All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Can no longer mount logical volume after a kernal panic. HELP!
Date: Thu, 15 Jan 2009 10:59:18 +0000	[thread overview]
Message-ID: <496F1706.3080403@redhat.com> (raw)
In-Reply-To: <BLU117-W51CBAE0430A271DF3DC52FFAD70@phx.gbl>

Bob Smith wrote:
> 
> I have been using LVM for quite a while to create a 3.64 stripe out of 4 x 1TB drives.  I use this as storage for my MythTV.  Tonight my system had a kernel panic, and when I rebooted I was no longer able to mount my LV, when I do I get:
> 
> ----------------------------------------------------------------------------------------------------------------------------------------------
> mount: wrong fs type, bad option, bad superblock on /dev/mapper/stripe-raid,
>        missing codepage or helper program, or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so

Did anything appear in dmesg? What does "file -s 
/dev/mapper/stripe-raid" say?

> When I do an fdisk -l /dev/stripe/raid (I know these are really dumb names for the lv and vg):

Why are you expecting there to be a partition table on the LV? That's 
something that you'd only normally do if you're using the LV as "whole 
disk" storage for an entire machine (e.g. exporting it via iSCSI or 
using it as storage for some kind of virtual machine).

Normally with LVM, file systems go directly onto the LV.

> Which makes me really worried that something has happened to the partition table when I was forced to reboot after the kernel panic.  Doing fdisk /dev/stripe/raid shows:

See above - I wouldn't normally expect there to be a partition table 
*inside* the LV.

Regards,
Bryn.

      parent reply	other threads:[~2009-01-15 10:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15  3:55 [linux-lvm] Can no longer mount logical volume after a kernal panic. HELP! Bob Smith
2009-01-15  5:11 ` Bob Smith
2009-01-15 10:59 ` Bryn M. Reeves [this message]

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=496F1706.3080403@redhat.com \
    --to=bmr@redhat.com \
    --cc=linux-lvm@redhat.com \
    /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.