All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moshe Yudkowsky <moshe@pobox.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID needs more to survive a power hit, different /boot layout for example (was Re: draft howto on making raids for surviving a disk crash)
Date: Mon, 04 Feb 2008 04:58:23 -0600	[thread overview]
Message-ID: <47A6EFCF.9080906@pobox.com> (raw)
In-Reply-To: <47A6DA81.3030008@msgid.tls.msk.ru>

Michael Tokarev wrote:
> Moshe Yudkowsky wrote:
> []
>> But that's *exactly* what I have -- well, 5GB -- and which failed. I've
>> modified /etc/fstab system to use data=journal (even on root, which I
>> thought wasn't supposed to work without a grub option!) and I can
>> power-cycle the system and bring it up reliably afterwards.
> 
> Note also that data=journal effectively doubles the write time.
> It's a bit faster for small writes (because all writes are first
> done into the journal, i.e. into the same place, so no seeking
> is needed), but for larger writes, the journal will become full
> and data found in it needs to be written to proper place, to free
> space for new data.  Here, if you'll continue writing, you will
> have more than 2x speed degradation, because of a) double writes,
> and b) more seeking.

The alternative seems to be that portions of the / file system won't 
mount because the file system is corrupted on a crash while writing.

If I'm reading the man pages, Wikis, READMEs and mailing lists correctly 
--  not necessarily the case -- the ext3 file system uses the equivalent 
of data=journal as a default.

The question then becomes what data scheme to use with reiserfs on the 
remainder of the file system, the /usr, /var, /home, and others. If they 
can recover on a reboot sing fsck and the default configuration of 
resierfs, then I have no problem using them. But my understanding is 
that data can be destroyed or lost or destroyed if there's a crash on a 
write; then there's little point in running a RAID system that can 
collect corrupt data.

Another way to phrase this: unless you're running data-center grade 
hardware and have absolute confidence in your UPS, you should use 
data=journal for reiserfs and perhaps avoid XFS entirely.


-- 
Moshe Yudkowsky * moshe@pobox.com * www.pobox.com/~moshe
"Right in the middle of a large field where there had never been a 
trench was a
shell hole... 8 feet deep by 15 across. On the edge of it was a dead... 
rat not over
twice the size of a mouse. No wonder the war costs so much." Col. George 
Patton

  reply	other threads:[~2008-02-04 10:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 19:15 RAID needs more to survive a power hit, different /boot layout for example (was Re: draft howto on making raids for surviving a disk crash) Moshe Yudkowsky
2008-02-03 20:01 ` Robin Hill
2008-02-03 20:46   ` Moshe Yudkowsky
2008-02-03 22:01     ` Robin Hill
2008-02-04 11:06       ` Moshe Yudkowsky
2008-02-04 11:40         ` Robin Hill
2008-02-03 20:28 ` Michael Tokarev
2008-02-03 20:54   ` Moshe Yudkowsky
2008-02-03 21:04     ` Michael Tokarev
2008-02-04  9:27     ` Michael Tokarev
2008-02-04 10:58       ` Moshe Yudkowsky [this message]
2008-02-04 13:52         ` Michael Tokarev
2008-02-04 14:09           ` Justin Piszcz
2008-02-04 14:25             ` Eric Sandeen
2008-02-04 14:42               ` Eric Sandeen
2008-02-04 15:31               ` Moshe Yudkowsky
2008-02-04 16:45                 ` Eric Sandeen
2008-02-04 17:22                   ` Michael Tokarev
2008-02-05 12:31                     ` Linda Walsh
2008-02-04 16:38               ` Michael Tokarev
2008-02-04 19:02                 ` Richard Scobie
2008-02-04 22:27                 ` Justin Piszcz
2008-02-06  1:12                 ` Linda Walsh
2008-02-06  2:12                   ` Michael Tokarev
2008-02-06  9:14                 ` Luca Berra

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=47A6EFCF.9080906@pobox.com \
    --to=moshe@pobox.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.