From: NeilBrown <neilb@suse.de>
To: lists@yazzy.org
Cc: linux-raid@vger.kernel.org
Subject: Re: Recovery of failed RAID 6 and LVM
Date: Mon, 26 Sep 2011 08:18:53 +1000 [thread overview]
Message-ID: <20110926081853.2819622b@notabene.brown> (raw)
In-Reply-To: <4E7FA3E8.5010603@yazzy.org>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
On Sun, 25 Sep 2011 23:58:00 +0200 "Marcin M. Jessa" <lists@yazzy.org> 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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-09-25 22:18 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 7:55 Recovery of failed RAID 6 and LVM Marcin M. Jessa
2011-09-25 8:39 ` Stan Hoeppner
2011-09-25 10:07 ` Marcin M. Jessa
2011-09-25 13:15 ` Phil Turmel
2011-09-25 14:16 ` Marcin M. Jessa
2011-09-25 16:43 ` Phil Turmel
2011-09-25 14:41 ` Marcin M. Jessa
2011-09-25 16:19 ` Phil Turmel
2011-09-25 21:40 ` NeilBrown
2011-09-25 21:58 ` Marcin M. Jessa
2011-09-25 22:18 ` NeilBrown [this message]
2011-09-25 22:21 ` Marcin M. Jessa
[not found] ` <4E804062.3020700@yazzy.org>
2011-09-26 9:31 ` NeilBrown
2011-09-26 10:53 ` Marcin M. Jessa
2011-09-26 11:10 ` NeilBrown
2011-09-27 19:12 ` Marcin M. Jessa
2011-09-27 23:13 ` NeilBrown
2011-09-28 2:50 ` Stan Hoeppner
2011-09-28 7:10 ` Marcin M. Jessa
2011-09-28 7:51 ` David Brown
2011-09-28 16:12 ` Stan Hoeppner
2011-09-28 16:30 ` Marcin M. Jessa
2011-09-28 18:56 ` Thomas Fjellstrom
2011-09-28 19:26 ` Marcin M. Jessa
2011-09-28 19:42 ` Thomas Fjellstrom
2011-09-28 23:49 ` NeilBrown
2011-09-29 9:03 ` David Brown
2011-09-29 15:21 ` Stan Hoeppner
2011-09-29 17:14 ` David Brown
2011-09-29 18:28 ` Dan Williams
2011-09-29 23:07 ` NeilBrown
2011-09-30 0:18 ` Williams, Dan J
2011-10-05 2:15 ` NeilBrown
2011-09-28 10:38 ` Michal Soltys
2011-09-28 13:20 ` Brad Campbell
2011-09-28 19:02 ` Thomas Fjellstrom
2011-09-28 16:31 ` Stan Hoeppner
2011-09-28 16:37 ` Marcin M. Jessa
2011-09-28 19:03 ` Thomas Fjellstrom
2011-09-28 19:29 ` Marcin M. Jessa
2011-09-28 19:43 ` Thomas Fjellstrom
2011-09-30 20:01 ` Marcin M. Jessa
2011-09-30 21:47 ` Thomas Fjellstrom
2011-09-30 22:30 ` Marcin M. Jessa
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=20110926081853.2819622b@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lists@yazzy.org \
/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.