From: Omry Yadan <omry@firefang.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lv became unmountable - "bad blocks" appeared.
Date: Sun, 27 Nov 2005 22:17:37 +0200 [thread overview]
Message-ID: <438A1461.2000809@firefang.net> (raw)
some background:
I have a volume group that spans on two drives.
one drive has a partition table, and one partion is LVM, and it contain
one lv.
the other has two lv's which overs it all (no partition table).
each lv sits on a single drive.
I started with a single huge lv, but decided to change things to this way
to minimize the damage in an event of a drive failure).
I started to get io errors from the lv on the first disk (the one which
is on the drive with the partition table).
just as I decided to backup the stuff, the lv became unmountable.
I suspected bad blocks in the drive, so I ran badblocks in non
destructable mode on the drive.
it didn't find anything.
I tried to run badblocks on the partition itself (badblocks /dev/hde3),
just to be sure.
still nothing.
this convinced me that the problem is not physical.
I decided to have badblocks access the blocks via lvm, meaning badblocks
/dev/data_vg/data
this found about 40K bad blocks.
I am now in the stage before I attemp to fix the file system (reiserfs)
using the bad blocks list. to recover whatever can be recovered.
do you guys have any better idea, because this will surely cost me some
data - and I am not convinced that
there is nothing else at lvm level that can make things more optimistic.
another thing:
this is a very serious problem, which looks like its originating from LVM.
I would be glad to share whatever info (lvm metadata etc) you guys will
need to identify it, in hope this problem will be eliminated, for the
sake of future victims.
Thanks,
Omry.
reply other threads:[~2005-11-27 20:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=438A1461.2000809@firefang.net \
--to=omry@firefang.net \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).