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
proxmox:/home/simon# fsck.ext4 -n /dev/mapper/lvm-raid-RAID
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
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 ?
Simon
On 16/02/2011 19:10, Phil Turmel wrote:
On 02/16/2011 02:07 PM, Simon McNair wrote:
pvscan is:
proxmox:/home/simon# pvscan --verbose
Wiping cache of LVM-capable devices
Wiping internal VG cache
Walking through all physical volumes
PV /dev/sda2 VG pve lvm2 [465.26 GB / 4.00 GB free]
PV /dev/md0 VG lvm-raid lvm2 [8.19 TB / 0 free]
Total: 2 [655.05 GB] / in use: 2 [655.05 GB] / in no VG: 0 [0 ]
lvm-raid is there ....
Very good.
proxmox:/home/simon# fsck.ext4 -n /dev/md0
Uh, no.
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext4: Superblock invalid, trying backup blocks...
Superblock has an invalid ext3 journal (inode 8).
Clear? no
fsck.ext4: Illegal inode number while checking ext3 journal for /dev/md0
I thought I needed to run fsck against the lvm group ? I used to do... fsck.ext4 /dev/lvm-raid/RAID so do I need to mount it or something ?
vgscan --verbose
lvscan --verbose
Then either:
fsck -N /dev/mapper/lvm-raid-RAID
or:
fsck -N /dev/lvm-raid/RAID
depends on what udev is doing.
Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
