From: <pcg@goof.com ( Marc) (A.) (Lehmann )>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Alex Adriaanse <alex.adriaanse@gmail.com>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: Odd data corruption problem with LVM/ReiserFS
Date: Tue, 22 Feb 2005 20:01:49 +0100 [thread overview]
Message-ID: <20050222190149.GB9590@schmorp.de> (raw)
In-Reply-To: <4219C811.5070906@domdv.de>
On Mon, Feb 21, 2005 at 12:37:53PM +0100, Andreas Steinmetz <ast@domdv.de> wrote:
> >Anyway, what do you guys think could be the problem? Could it be that
> >the LVM / Device Mapper snapshot feature is solely responsible for
> >this corruption? (I'm sure there's a reason it's marked
> >Experimental).
>
> I don't think so - I changed from reiserfs to ext3 without changing the
> underlying dm/raid5 and this seems to work properly.
I use both reiserfs and ext3 on lvm/dm on raid.
Both filesystems have issues when restoring from backup (i.e. very heavy
write activity).
I did report this to the linux kernel, and got as reply that there are
indeed races *somewhere*, but as of yet there is no fix.
The symptoms are _not_ I/O errors (but until I see logs I wouldn't believe
you that there are real I/O errors), but usually too-high block numbers.
A reboot fixes this for both ext3 and reiserfs (i.e. the error is gone).
You might want to explore this problem and decide for yourself if it's caused
by I/O errors (in which case you have a disk problem) or "just" filesystem
corruption.
--
The choice of a
-----==- _GNU_
----==-- _ generation Marc Lehmann
---==---(_)__ __ ____ __ pcg@goof.com
--==---/ / _ \/ // /\ \/ / http://schmorp.de/
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE
next prev parent reply other threads:[~2005-02-22 19:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 5:25 Odd data corruption problem with LVM/ReiserFS Alex Adriaanse
2005-02-21 10:48 ` Vladimir Saveliev
2005-02-21 11:37 ` Andreas Steinmetz
2005-02-21 16:44 ` Alex Adriaanse
2005-02-21 18:07 ` Andreas Steinmetz
2005-02-22 19:01 ` Lehmann [this message]
2005-02-22 19:39 ` Andreas Steinmetz
2005-02-22 19:49 ` Lehmann
2005-02-22 20:46 ` Alex Adriaanse
2005-02-22 20:54 ` Lehmann
2005-02-21 15:18 ` Alasdair G Kergon
2005-02-21 21:28 ` Alex Adriaanse
2005-02-22 3:19 ` Alex Adriaanse
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=20050222190149.GB9590@schmorp.de \
--to=pcg@goof.com \
--cc=alex.adriaanse@gmail.com \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox