public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: pcg@goof.com
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:39:21 +0100	[thread overview]
Message-ID: <421B8A69.8000903@domdv.de> (raw)
In-Reply-To: <20050222190149.GB9590@schmorp.de>

pcg( Marc)@goof(A.).(Lehmann )com wrote:
> 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.
> 

To clarify: there were no disk I/O errors, only I/O errors were reported 
  by find during operation so it is definitely filesystem corruption 
that is  going on here.
Though find performs heavy read activity there could well be heavy write 
activity be involved due to atime updates so this fits your description.

> A reboot fixes this for both ext3 and reiserfs (i.e. the error is gone).
> 

Well, it didn't fix it for me. The fs was trashed for good. The major 
question for me is now usability of md/dm for any purpose with 2.6.x. 
For me this is a showstopper for any kind of 2.6 production use.
-- 
Andreas Steinmetz                       SPAMmers use robotrap@domdv.de

  reply	other threads:[~2005-02-22 19:43 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 
2005-02-22 19:39     ` Andreas Steinmetz [this message]
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=421B8A69.8000903@domdv.de \
    --to=ast@domdv.de \
    --cc=alex.adriaanse@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcg@goof.com \
    --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