From: Andreas Steinmetz <ast@domdv.de>
To: Alex Adriaanse <alex.adriaanse@gmail.com>
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: Odd data corruption problem with LVM/ReiserFS
Date: Mon, 21 Feb 2005 12:37:53 +0100 [thread overview]
Message-ID: <4219C811.5070906@domdv.de> (raw)
In-Reply-To: <93ca3067050220212518d94666@mail.gmail.com>
Alex Adriaanse wrote:
> As far as I can tell all the directories are still intact, but there
> was a good number of files that had been corrupted. Those files
> looked like they had some chunks removed, and some had a bunch of NUL
> characters (in blocks of 4096 characters). Some files even had chunks
> of other files inside of them!
I can second that. I had the same experience this weekend on a
md/dm/reiserfs setup. The funny thing is that e.g. find reports I/O
errors but if you then run tar on the tree you eventually get the
correct data from tar. Then run find again and you'll again get I/O errors.
> I did a reiserfsck (3.6.19) on /var, which did not report any problems.
You need to run 'reiserfsck --rebuild-tree' and see what happens :-(
> 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 can furthermore state that reiserfs without dm/md does work correctly
as I use reiserfs on a ieee1394 backup disk (that saved me from terrible
trouble).
Currently I can only warn to not use reiserfs with dm/md on 2.6.
--
Andreas Steinmetz SPAMmers use robotrap@domdv.de
next prev parent reply other threads:[~2005-02-21 11:37 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 [this message]
2005-02-21 16:44 ` Alex Adriaanse
2005-02-21 18:07 ` Andreas Steinmetz
2005-02-22 19:01 ` Lehmann
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=4219C811.5070906@domdv.de \
--to=ast@domdv.de \
--cc=alex.adriaanse@gmail.com \
--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