Re: Recovery of failed RAID 6 and LVM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 25 Sep 2011 23:58:00 +0200 "Marcin M. Jessa" <lists@xxxxxxxxx> wrote:

> On 9/25/11 11:40 PM, NeilBrown wrote:
> 
> [...]
> 
> > You wouldn't expect an LV to contain a partition table.  You would expect it
> > to contain a filesystem.
> 
> Yes, there is still data available on the LVs.
> I actually managed to grab some files from one of the LVs using 
> foremost. But foremost is limited and creates it's own directory 
> hierarchy with file names being changed.
> 
> > What does
> >     fsck -f -n /dev/fridge/storage
> >
> > show??
> 
> # fsck -f -n /dev/fridge/storage
> fsck from util-linux 2.19.1
> e2fsck 1.42-WIP (02-Jul-2011)
> fsck.ext2: Superblock invalid, trying backup blocks...
> fsck.ext2: Bad magic number in super-block while trying to open 
> /dev/mapper/fridge-storage
> 
> 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>
> 
> 

Do you remember what filesystem you had on 'storage'?  Was it ext3 or ext4 or
xfs or something else?

NeilBrown

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux