All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Chiappini <Jean.Chiappini@virtua.ch>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] EXT3-fs: unable to read superblock
Date: Tue, 12 Dec 2006 11:16:16 +0100	[thread overview]
Message-ID: <457E8170.4000007@virtua.ch> (raw)
In-Reply-To: <20061211180859.GN31405@valinor.arda.theunixman.com>

Thank you for your answer, but when I do this command, this error appear :
tune2fs: Argument invalide while trying to open 
/dev/mapper/VolGroup00-mysqldata
Couldn't find valid filesystem superblock.

The only solution I see now is to format this partition...

Evan Cofsky wrote:
> On 12/11 17:33, Jean Chiappini wrote:
>   
>> Hello all,
>>
>> I have a server production with centos 4 with kernel 2.6.9-42 and 
>> lvm2-2.02.06 installed. All was working find, but today the server 
>> crashed. When I would reboot my server, I saw in the log that the lvm 
>> partiton wouldn't mount. This is the error -> kernel: EXT3-fs: unable to 
>> read superblock.
>>     
>
> I had this problem recently with a few systems.  Try booting to
> single-user mode, and then do the following command:
>
> tune2fs -j DEVICE-FILE-WITH-PROBLEM
>
> This will create a new journal on the filesystem.  I haven't tracked
> down why the journal disappears yet, but it seems to, and then the
> system (of course) won't mount it as ext3.
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

  reply	other threads:[~2006-12-12 10:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11 16:33 [linux-lvm] EXT3-fs: unable to read superblock Jean Chiappini
2006-12-11 18:09 ` Evan Cofsky
2006-12-12 10:16   ` Jean Chiappini [this message]
2006-12-14  3:14     ` Evan Cofsky

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=457E8170.4000007@virtua.ch \
    --to=jean.chiappini@virtua.ch \
    --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.