From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] snapshots of busy ext2 file system corrupt
Date: Tue Feb 26 14:58:02 2002 [thread overview]
Message-ID: <2621690000.1014757084@tiny> (raw)
In-Reply-To: <m2bsecdouv.fsf@isnogud.escape.de>
On Tuesday, February 26, 2002 08:28:40 PM +0100 Urs Thuermann <urs@isnogud.escape.de> wrote:
> Chris Mason <mason@suse.com> writes:
>
>> For ext2, the best we could do would probably be a hack based on
>> locking the super. As far as I know, nobody is planning on this,
>
> :-(
>
>> especially given how easy it is to go from ext2->ext3.
>
> Some performance tests I made with ext2, ext3, and reiserfs convinced
> me to stay with ext2. ext3 was significantly slower than ext2 on some
> operations (and reiserfs even worse than that).
You trade speed for safety sometimes, but you can lower the performance
hit by mounting ext3 with -o data=writeback, and help both filesystems
by playing with bdflush values (increment the metadata timeout up from 5
seconds).
Other tuning depends on your app.
-chris
next prev parent reply other threads:[~2002-02-26 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 7:55 [linux-lvm] snapshots of busy ext2 file system corrupt Urs Thuermann
2002-02-26 10:59 ` Andreas Dilger
2002-02-26 11:40 ` Chris Mason
2002-02-26 13:30 ` Urs Thuermann
2002-02-26 14:58 ` Chris Mason [this message]
2002-02-26 15:27 ` Andreas Dilger
2002-02-26 16:32 ` Marc MERLIN
2002-02-26 17:21 ` Andreas Dilger
2002-02-26 13:25 ` Urs Thuermann
2002-02-27 3:01 ` Anselm Kruis
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 14:24 Stephenson, Dale
2002-02-27 14:43 ` Chris Mason
2002-03-04 2:46 ` Anselm Kruis
2002-03-04 2:51 ` Anselm Kruis
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=2621690000.1014757084@tiny \
--to=mason@suse.com \
--cc=linux-lvm@sistina.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.