All of lore.kernel.org
 help / color / mirror / Atom feed
From: <pcg( Marc)@goof(A.).(Lehmann )com>
To: Alex Adriaanse <alex.adriaanse@gmail.com>
Cc: Andreas Steinmetz <ast@domdv.de>,
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: Odd data corruption problem with LVM/ReiserFS
Date: Tue, 22 Feb 2005 21:54:19 +0100	[thread overview]
Message-ID: <20050222205419.GA12797@schmorp.de> (raw)
In-Reply-To: <93ca306705022212461f9e0d81@mail.gmail.com>

On Tue, Feb 22, 2005 at 02:46:44PM -0600, Alex Adriaanse <alex.adriaanse@gmail.com> wrote:
> On Tue, 22 Feb 2005 20:49:00 +0100, Marc A. Lehmann <pcg@goof.com> wrote:
> > 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?

No snapshots either.

-- 
                The choice of a
      -----==-     _GNU_
      ----==-- _       generation     Marc Lehmann
      ---==---(_)__  __ ____  __      pcg@goof.com
      --==---/ / _ \/ // /\ \/ /      http://schmorp.de/
      -=====/_/_//_/\_,_/ /_/\_\      XX11-RIPE

WARNING: multiple messages have this Message-ID (diff)
From: <pcg@goof.com ( Marc) (A.) (Lehmann )>
To: Alex Adriaanse <alex.adriaanse@gmail.com>
Cc: Andreas Steinmetz <ast@domdv.de>,
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: Odd data corruption problem with LVM/ReiserFS
Date: Tue, 22 Feb 2005 21:54:19 +0100	[thread overview]
Message-ID: <20050222205419.GA12797@schmorp.de> (raw)
In-Reply-To: <93ca306705022212461f9e0d81@mail.gmail.com>

On Tue, Feb 22, 2005 at 02:46:44PM -0600, Alex Adriaanse <alex.adriaanse@gmail.com> wrote:
> On Tue, 22 Feb 2005 20:49:00 +0100, Marc A. Lehmann <pcg@goof.com> wrote:
> > 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?

No snapshots either.

-- 
                The choice of a
      -----==-     _GNU_
      ----==-- _       generation     Marc Lehmann
      ---==---(_)__  __ ____  __      pcg@goof.com
      --==---/ / _ \/ // /\ \/ /      http://schmorp.de/
      -=====/_/_//_/\_,_/ /_/\_\      XX11-RIPE

  reply	other threads:[~2005-02-22 20:54 UTC|newest]

Thread overview: 17+ 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:01     ` Lehmann 
2005-02-22 19:39     ` Andreas Steinmetz
2005-02-22 19:49       ` Lehmann 
2005-02-22 19:49         ` Lehmann 
2005-02-22 20:46         ` Alex Adriaanse
2005-02-22 20:54           ` Lehmann  [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
2005-02-21 15: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=20050222205419.GA12797@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.