public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 19:07:17 +0100	[thread overview]
Message-ID: <421A2355.1030605@domdv.de> (raw)
In-Reply-To: <93ca30670502210844578dce95@mail.gmail.com>

Alex Adriaanse wrote:
> The weird thing is I did not see any I/O errors in my logs, and
> running find on /var worked without a problem.  By the way, did you
> take any DM snapshots when you experienced that corruption?

No, no snapshots. Just working find on a large dataset (source tree, 
about 16GB). The fun part is that I got the I/O errors for varying 
diretories and 'ls'-sing thes directories after find failed, too. 
However a follow-up tar to the ieee1394 disk to salvage the data 
actually could access all data correctly. One day before I did 
experience the same symptom but did reboot. This caused actual damage 
all over the place and I had to restore from the last checkpoint I made.

-- 
Andreas Steinmetz                       SPAMmers use robotrap@domdv.de

  reply	other threads:[~2005-02-21 18:02 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 [this message]
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=421A2355.1030605@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