From: Anselm Kruis <A.Kruis@science-computing.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] snapshots of busy ext2 file system corrupt
Date: Wed Feb 27 03:01:01 2002 [thread overview]
Message-ID: <Pine.LNX.4.02.10202270943080.8818-100000@murnau.science-computing.de> (raw)
In-Reply-To: <m28z9guz53.fsf@isnogud.escape.de>
On 26 Feb 2002, Urs Thuermann wrote:
> I tried creating a snapshot of a ext2 file system on a LV. I expected
> a fsck on the snapshot device to give no errors, i.e. a consistent
> file system. This is ok, as long as there is no (or little) load on
> the file system when creating the snapshot.
>
> However, on a busy file system, the created snapshot has lots of
> errors found by fsck.
>
> Is it this what the VFS lock patch is for? If so, why hasn't it been
> integrated into the standard kernel? Has it flaws in it? Maybe
> performance wise?
It deadlocks for XFS on smp under heavy writeload. I use a writeable
snapshot patch and replay the log afterwards.
I think, the VFS patch has some principal problems. Creating a snapshot
with the VFS-lock patch applied is more or less equivalent to unmounting
the file system, creating the snapshot of the device and remounting the
file system. That means that all ongoing write operations must be
suspended until the filesystem is in a "clean" state. This can take
some time. Up to 15 minutes from my observations and that is way too long.
I think the right way is: use a jornaling file system, take a snapshot,
make the snapshot writeable, replay the log, make the snapshot readonly
and dump it to tape or whatever you want. No races, no deadlocks, no
problems.
Anselm
---
Anselm Kruis Tel. +49 (0)89-356386-74
science + computing ag FAX +49 (0)89-356386-37
Ingolstädter Str. 22 mailto: A.Kruis@science-computing.de
D-80807 München WWW: http://www.science-computing.de/
**********************************************************************
*** Wir freuen uns auf Ihren Besuch ***
*** ***
*** CeBIT 2002 ***
*** 13.-20.03.2002, Messegelände Hannover, Halle 11, F 64 ***
*** ***
*** Automotive Circle International ***
*** 18.-19.04.2002, Bad Nauheim ***
*** ***
*** VDI-Tagung: Berechnung und Simulation im Fahrzeugbau ***
*** 01.-02.10.2002, Congress-Centrum Würzburg ***
*** ***
**********************************************************************
next prev parent reply other threads:[~2002-02-27 3:01 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
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 [this message]
-- 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=Pine.LNX.4.02.10202270943080.8818-100000@murnau.science-computing.de \
--to=a.kruis@science-computing.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).