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>
Cc: darx@sent.com
Subject: Re: [linux-lvm] resize of LV causing superblock corruption ( Bad magic number ). how to prevent/fix?
Date: Mon, 22 Jul 2013 10:58:27 +0100	[thread overview]
Message-ID: <51ED0243.3050003@redhat.com> (raw)
In-Reply-To: <1374438895.27222.9223372036855387565.0F08A743@webmail.messagingengine.com>

This is an fdisk rather than LVM2 problem.

Compare:

On 07/21/2013 09:34 PM, darx@sent.com wrote:
> 	fdisk -l /dev/VGTEST/test_root | grep Linux
> 		/dev/VGTEST/test_root1            2048     8388607    
                                                  ^^^^
> 		4193280   83  Linux

vs.:


> 	fdisk -l /dev/VGTEST/test_root | grep Linux
> 		/dev/VGTEST/test_root1              32    25165823   
                                                    ^^
> 		12582896   83  Linux

I.e. your fdisk program moved the start of the partition. That'll pretty
much break any file system that has fixed superblock locations.

Either use an fdisk that matches the defaults used when the partition
was first created or ensure you are using sector display units (looks
like you are - 2048 == 1MiB which is the default used by modern fdisks
from util-linux) and carefully match the start location when
deleting/re-adding.

Btw this is fixable as long as you can still find the correct starting
sector.

Regards,
Bryn.

  reply	other threads:[~2013-07-22  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-21 20:34 [linux-lvm] resize of LV causing superblock corruption ( Bad magic number ). how to prevent/fix? darx
2013-07-22  9:58 ` Bryn M. Reeves [this message]
2013-07-22 16:29   ` darx

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=51ED0243.3050003@redhat.com \
    --to=bmr@redhat.com \
    --cc=darx@sent.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.