From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon McNair Subject: Re: Linux software RAID assistance Date: Wed, 16 Feb 2011 19:15:44 +0000 Message-ID: <4D5C2260.3020800@gmail.com> References: <4D540F6C.6050904@gmail.com> <20110215155315.55d35b8e@notabene.brown> <4D5A92F3.1090004@turmel.org> <4D5BD678.2050200@gmail.com> <4D5BE119.7000804@turmel.org> <4D5C0E17.3060306@gmail.com> <4D5C140F.9010301@turmel.org> <4D5C1508.3040308@gmail.com> <4D5C15D3.1070608@turmel.org> <4D5C167C.7000101@turmel.org> <4D5C1CF8.1020507@gmail.com> <4D5C1E0B.9060300@turmel.org> <4D5C2061.4060106@gmail.com> <4D5C2143.3000907@turmel.org> Reply-To: simonmcnair@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D5C2143.3000907@turmel.org> Sender: linux-raid-owner@vger.kernel.org To: Phil Turmel Cc: NeilBrown , linux-raid@vger.kernel.org List-Id: linux-raid.ids 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 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