public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Adriaanse <alex.adriaanse@gmail.com>
To: "Marc A. Lehmann" <pcg@goof.com>,
	Andreas Steinmetz <ast@domdv.de>,
	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 14:46:44 -0600	[thread overview]
Message-ID: <93ca306705022212461f9e0d81@mail.gmail.com> (raw)
In-Reply-To: <20050222194900.GB10968@schmorp.de>

On Tue, 22 Feb 2005 20:49:00 +0100, Marc A. Lehmann <pcg@goof.com> wrote:
> > >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.
> 
> Well, I do use reiserfs->aes-loop->lvm/dm->md5/raid5, and it never failed
> for me, except once, and the error is likely to be outside reiserfs, and
> possibly outside lvm.

Marc, what about you, were you using dm-snapshot when you experienced
temporary corruption?

Alex

  reply	other threads:[~2005-02-22 20:46 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
2005-02-22 19:49       ` Lehmann 
2005-02-22 20:46         ` Alex Adriaanse [this message]
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=93ca306705022212461f9e0d81@mail.gmail.com \
    --to=alex.adriaanse@gmail.com \
    --cc=ast@domdv.de \
    --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