From: Spam <spam@tnonline.net>
To: reiserfs-list@namesys.com
Subject: Re: Need Warm Fuzzies, ReiserFS (3)
Date: Mon, 20 Dec 2004 17:32:38 +0100 [thread overview]
Message-ID: <1046303449.20041220173238@tnonline.net> (raw)
In-Reply-To: <200412201725.03216.christian.mayrhuber@gmx.net>
> On Monday 20 December 2004 16:38, Tom Vier wrote:
>> On Mon, Dec 20, 2004 at 01:31:25PM +0100, Christian Mayrhuber wrote:
>> > The barrier mount option should provide protection against a corrupted
>> > journal during power failure for drives with write caching enabled.
>> > (Mostly IDE)
>>
>> There's a mount option for write barriers? It should be enabled by default.
>> Otherwise, that's asking for tons of users with corruption.
> http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.9
> Before disk barriers you had to disable harddisk write caching to prevent
> journal corruption. This is what nearly no one did and blamed the
> filesystems instead.
> Disk barriers are only in since 2.6.9, so maybe these get turned on per
> default after some more testing. That did happen to the data=ordered journal
> mode.
What happen with the performance when these barriers are active?
Is it only during power failure the data in the write cache is lost?
Also, does anyone know if the data in the disk write cache is
written out if the system crashes/freezes. Power failure is not a
very common occurrence, but crashes are much more so.
Is it possible to detect if filesystem was unmounted due to power
failure or due to a kernel crash?
~S
--
next prev parent reply other threads:[~2004-12-20 16:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 5:41 Need Warm Fuzzies, ReiserFS (3) Jim Miller
2004-12-20 12:31 ` Christian Mayrhuber
2004-12-20 15:38 ` Tom Vier
2004-12-20 16:25 ` Christian Mayrhuber
2004-12-20 16:32 ` Spam [this message]
2004-12-20 20:24 ` Christian Mayrhuber
2004-12-20 20:31 ` Spam
2004-12-20 20:55 ` Christian Mayrhuber
2004-12-20 21:26 ` Tom Vier
2004-12-20 21:34 ` Spam
2004-12-21 15:49 ` Tom Vier
2004-12-20 19:23 ` Tom Vier
2004-12-20 20:04 ` Christian Mayrhuber
2004-12-20 17:27 ` Hans Reiser
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=1046303449.20041220173238@tnonline.net \
--to=spam@tnonline.net \
--cc=reiserfs-list@namesys.com \
/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.