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
