From: linux@horizon.com
To: linux-kernel@vger.kernel.org
Subject: Re: [lkcd-general] Re: What's left over.
Date: 3 Nov 2002 17:08:23 -0000 [thread overview]
Message-ID: <20021103170823.10591.qmail@science.horizon.com> (raw)
Just to complicate things, consider this setup:
# cat /proc/swaps
Filename Type Size Used Priority
/dev/md5 partition 999864 16904 0
/dev/md6 partition 999864 16924 0
/dev/md7 partition 999864 16920 0
Those are all RAID-1 mirrors, a measure whose ass-saving value I have
enjoyed.
While a crash dump to just half of one of those mirrors is fine, finding it
might be a little bit tricky. And the fact that the kernel reassembles
the mirrors automatically on boot might make retrieving the data a little
bit tricky, too.
(After a crash, the mirrors will be inconsistent, so one will get copied
over the other, but I'm not too clear on which direction it'll happen in.)
I can't NOT reassemble at least some mirrors on boot because / is mirrored!
Now, to that, add the case that each of those is significantly smaller than
main memory. (2/3 size would still allow swap = 2*ram.)
The problem is that hardware is getting more and more sopisticated and
requiring ever more elaborate device drivers. Eventually you have to
have a cutoff and say that something is too complex to talk to after a
crash, even though it's theoretically available. Where is that line?
USB? iSCSI? This situation?
A reasonable fallback is to just drop in a cheap crappy dedicated
IDE drive for catching crash dumps, but I'd like the crash dumper to
know how to wake it up from sleep mode; I'd hate to leave it spinning
all the time...
next reply other threads:[~2002-11-03 17:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 17:08 linux [this message]
2002-11-03 19:14 ` jw schultz
-- strict thread matches above, loose matches on Subject: below --
2002-11-05 20:37 Dr. Greg Wettstein
[not found] <Pine.LNX.4.44.0211040727330.771-100000@home.transmeta.com.suse.lists.linux.kernel>
[not found] ` <1036429035.1718.99.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel>
2002-11-04 16:53 ` Andi Kleen
2002-11-04 12:34 Richard J Moore
2002-11-04 11:59 Richard J Moore
2002-11-04 12:27 ` Lars Marowsky-Bree
2002-11-04 16:16 ` John Alvord
2002-11-04 16:22 ` Linus Torvalds
2002-11-04 16:57 ` Alan Cox
2002-11-05 9:05 ` Suparna Bhattacharya
[not found] <551170412@toto.iv>
2002-11-04 3:03 ` Peter Chubb
2002-11-04 13:08 ` Alan Cox
2002-11-03 13:48 Bill Davidsen
2002-11-04 2:44 ` [lkcd-general] " Jennie Haywood
2002-11-04 14:45 ` Henning P. Schmiedehausen
2002-11-04 15:29 ` Alan Cox
2002-11-04 15:27 ` Henning P. Schmiedehausen
2002-11-04 15:38 ` Patrick Finnegan
2002-11-04 16:51 ` Henning P. Schmiedehausen
2002-11-05 4:57 ` Werner Almesberger
2002-11-02 15:29 Alan Cox
2002-11-03 1:24 ` [lkcd-general] " Matt D. Robinson
2002-11-03 1:49 ` Alan Cox
2002-11-03 14:33 ` Bill Davidsen
2002-11-03 15:34 ` Bernd Eckenfels
2002-11-03 16:32 ` Alan Cox
2002-11-05 18:07 ` Bill Davidsen
2002-11-03 3:10 ` Christoph Hellwig
2002-10-31 22:47 Perez-Gonzalez, Inaky
2002-11-01 13:06 ` [lkcd-general] " Jan Iven
2002-10-31 22:20 Shawn
2002-10-31 23:14 ` [lkcd-general] " Bernhard Kaindl
2002-10-31 21:58 Richard J Moore
2002-10-31 15:46 Linus Torvalds
2002-10-31 17:55 ` [lkcd-general] " Dave Craft
2002-10-31 18:45 ` Patrick Mochel
2002-10-31 19:16 ` Stephen Hemminger
2002-10-31 19:57 ` george anzinger
2002-10-31 20:48 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021103170823.10591.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®