From: Marc des Garets <marc@ttux.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] broken fs after removing disk from group
Date: Wed, 12 Nov 2014 23:16:13 +0100 [thread overview]
Message-ID: <5463DC2D.5020305@ttux.net> (raw)
Hi,
I messed up a bit and I am trying to find the best way to recover.
A few days ago, 1 of the physical disk of my lvm setup started to show
sign of failure (I/O errors) so I decided to move it to another disk
with pvmove. That didn't work out. After 5 days, pvmove had done only
0.1% so I stopped it.
After a reboot, the dying disk wouldn't show up at all, it had died
completely so I decided to remove it with vgreduce --removemissing
--force VolGroup00
Problem is that it refused to do so because of the pvmove saying the LV
was locked. I tried pvmove --abort which refused to do so because of the
missing disk that died.
So I was stuck and did: vgcfgbackup VolGroup00
Then I edited the file, removed the entry about pvmove, tried
vgcfgbackup VolGroup00 which refused to restore because of the missing
disk so I edited the file again, removed the missing disk from there and
did the vgcfgrestore which succeeded.
Now the problem is that I can't mount my volume because it says:
wrong fs type, bad option, bad superblock
Which makes sense as the size of the partition is supposed to be 2.4Tb
but now has only 2.2Tb. Now the question is how do I fix this? Should I
use a tool like testdisk or should I be able to somehow create a new
physical volume / volume group where I can add my logical volumes which
consist of 2 physical disks and somehow get the file system right (file
system is ext4)?
pvdisplay output:
--- Physical volume ---
PV Name /dev/sda4
VG Name VolGroup00
PV Size 417.15 GiB / not usable 4.49 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 106789
Free PE 0
Allocated PE 106789
PV UUID dRhDoK-p2Dl-ryCc-VLhC-RbUM-TDUG-2AXeWQ
--- Physical volume ---
PV Name /dev/sdb1
VG Name VolGroup00
PV Size 1.82 TiB / not usable 4.97 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 476923
Free PE 0
Allocated PE 476923
PV UUID MF46QJ-YNnm-yKVr-pa3W-WIk0-seSr-fofRav
Thank you for your help.
Marc
next reply other threads:[~2014-11-12 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 22:16 Marc des Garets [this message]
2014-11-12 23:11 ` [linux-lvm] broken fs after removing disk from group Fran Garcia
2014-11-13 7:21 ` Marc des Garets
2014-11-13 9:47 ` Marc des Garets
2014-11-13 19:27 ` Marc des Garets
2014-11-13 19:48 ` matthew patton
2014-11-13 20:04 ` Marc des Garets
2014-11-14 8:42 ` Marc des Garets
2014-11-14 17:12 ` Jack Waterworth
2014-11-14 19:16 ` Marc des Garets
2014-11-14 19:30 ` Marc des Garets
2014-11-14 20:54 ` Marc des Garets
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=5463DC2D.5020305@ttux.net \
--to=marc@ttux.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).