From: Phil Turmel <philip@turmel.org>
To: simonmcnair@gmail.com
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Linux software RAID assistance
Date: Wed, 16 Feb 2011 14:36:30 -0500 [thread overview]
Message-ID: <4D5C273E.7020609@turmel.org> (raw)
In-Reply-To: <4D5C2260.3020800@gmail.com>
On 02/16/2011 02:15 PM, Simon McNair wrote:
> proxmox:/home/simon# vgscan --verbose
> Wiping cache of LVM-capable devices
> Wiping internal VG cache
> Reading all physical volumes. This may take a while...
> Finding all volume groups
> Finding volume group "pve"
> Found volume group "pve" using metadata type lvm2
> Finding volume group "lvm-raid"
> Found volume group "lvm-raid" using metadata type lvm2
> proxmox:/home/simon#
> proxmox:/home/simon# lvscan --verbose
> Finding all logical volumes
> ACTIVE '/dev/pve/swap' [11.00 GB] inherit
> ACTIVE '/dev/pve/root' [96.00 GB] inherit
> ACTIVE '/dev/pve/data' [354.26 GB] inherit
> inactive '/dev/lvm-raid/RAID' [8.19 TB] inherit
>
> proxmox:/home/simon# vgchange -ay
> 3 logical volume(s) in volume group "pve" now active
> 1 logical volume(s) in volume group "lvm-raid" now active
Heh. Figures.
> proxmox:/home/simon# fsck.ext4 -n /dev/mapper/lvm-raid-RAID
Actually, I wanted you to try with a capital N. Lower case 'n' is similar, but not quite the same.
> e2fsck 1.41.3 (12-Oct-2008)
> fsck.ext4: No such file or directory while trying to open /dev/mapper/lvm-raid-RAID
>
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
> e2fsck -b 8193 <device>
>
> proxmox:/home/simon# fsck.ext4 -n /dev/mapper/
> control lvm--raid-RAID pve-data pve-root pve-swap
Strange. I guess it does that to distinguish dashes in the VG name from dashes between VG and LV names.
> proxmox:/home/simon# fsck.ext4 -n /dev/mapper/lvm--raid-RAID
> e2fsck 1.41.3 (12-Oct-2008)
> /dev/mapper/lvm--raid-RAID has unsupported feature(s): FEATURE_I31
> e2fsck: Get a newer version of e2fsck!
>
> my version of e2fsck always worked before ?
v1.41.14 was release 7 weeks ago. But, I suspect there's corruption in the superblock. Do you still have your disk images tucked away somewhere safe?
If so, try:
1) The '-b' option to e2fsck. We need to experiment with '-n -b offset' to find the alternate superblock. Trying 'offset' = to 8193, 16384, and 32768, per the man-page.
2) A newer e2fsprogs.
Finally,
3) mount -r /dev/lvm-raid/RAID /mnt/whatever
Phil
next prev parent reply other threads:[~2011-02-16 19:36 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 16:16 Linux software RAID assistance Simon McNair
2011-02-10 18:24 ` Phil Turmel
2011-02-15 4:53 ` NeilBrown
2011-02-15 8:48 ` Simon McNair
2011-02-15 14:51 ` Phil Turmel
2011-02-15 19:04 ` Simon McNair
2011-02-15 19:37 ` Phil Turmel
2011-02-15 19:45 ` Roman Mamedov
2011-02-15 21:09 ` Simon McNair
2011-02-17 15:10 ` Simon Mcnair
2011-02-17 15:42 ` Roman Mamedov
2011-02-18 9:13 ` Simon McNair
2011-02-18 9:38 ` Robin Hill
2011-02-18 10:38 ` Simon Mcnair
2011-02-19 11:46 ` Jan Ceuleers
2011-02-19 12:40 ` Simon McNair
2011-02-19 17:37 ` Jan Ceuleers
2011-02-16 13:51 ` Simon McNair
2011-02-16 14:37 ` Phil Turmel
2011-02-16 17:49 ` Simon McNair
2011-02-16 18:14 ` Phil Turmel
2011-02-16 18:18 ` Simon McNair
2011-02-16 18:22 ` Phil Turmel
2011-02-16 18:25 ` Phil Turmel
2011-02-16 18:52 ` Simon McNair
2011-02-16 18:57 ` Phil Turmel
2011-02-16 19:07 ` Simon McNair
2011-02-16 19:10 ` Phil Turmel
2011-02-16 19:15 ` Simon McNair
2011-02-16 19:36 ` Phil Turmel [this message]
2011-02-16 21:28 ` Simon McNair
2011-02-16 21:30 ` Phil Turmel
2011-02-16 22:44 ` Simon Mcnair
2011-02-16 23:39 ` Phil Turmel
2011-02-17 13:26 ` Simon Mcnair
2011-02-17 13:48 ` Phil Turmel
2011-02-17 13:56 ` Simon Mcnair
2011-02-17 14:34 ` Simon Mcnair
2011-02-17 16:54 ` Phil Turmel
2011-02-19 8:43 ` Simon Mcnair
2011-02-19 15:30 ` Phil Turmel
[not found] ` <AANLkTinOXJWRw_et2U43R_T9XPBzQLnN56Kf2bOAz=_c@mail.gmail.com>
2011-02-19 16:19 ` Phil Turmel
2011-02-20 9:56 ` Simon Mcnair
2011-02-20 19:50 ` Phil Turmel
2011-02-20 23:17 ` Simon Mcnair
2011-02-20 23:39 ` Phil Turmel
2011-02-22 17:12 ` Simon Mcnair
2011-02-22 17:14 ` Simon Mcnair
2011-02-22 18:23 ` Phil Turmel
2011-02-22 18:36 ` Simon McNair
2011-02-22 19:06 ` Phil Turmel
2011-02-18 9:31 ` Simon Mcnair
2011-02-18 13:16 ` Phil Turmel
2011-02-18 13:21 ` Roberto Spadim
2011-02-18 13:26 ` Phil Turmel
2011-02-18 13:29 ` Simon Mcnair
2011-02-18 13:34 ` Phil Turmel
2011-02-18 14:12 ` Simon McNair
2011-02-18 16:10 ` Phil Turmel
2011-02-18 16:38 ` Roberto Spadim
[not found] ` <AANLkTi=RmR5nVnmFLuqK5anHc3WDPxjuYjitT6+5wAqS@mail.gmail.com>
2011-02-20 18:48 ` Phil Turmel
2011-02-20 19:25 ` Simon Mcnair
2011-02-19 8:49 ` Simon Mcnair
2011-02-16 13:56 ` Simon McNair
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=4D5C273E.7020609@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=simonmcnair@gmail.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.