From: Johannes Graumann <johannes_graumann@web.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] [SOLVED]: lvm2 and partition shringkin: superblock/filesystem size mismatch
Date: Wed, 01 Dec 2010 11:10:47 +0100 [thread overview]
Message-ID: <id56v8$fc4$1@dough.gmane.org> (raw)
In-Reply-To: id4tfc$81m$1@dough.gmane.org
mke2fs -b 4096 -t ext3 -S /dev/mapper/mygroup-home
on the unmounted file system solved my issue.
Joh
Johannes Graumann wrote:
> Hi,
>
> I'm running debian testing and "/home" is an ext3 fs. I run the following
> order of commands to shrink the fs and the corresponding partition:
>
> e2fsck -f /dev/mapper/mygroup-home
> resize2fs /dev/mapper/mygroup-home 55329357
> lvreduce -L 208.5g /dev/mapper/mygroup-home
>
> The latter was supposed to be .5g bigger than necessary (paranoia
> regarding the data integrity kicking in).
>
> "e2fck /dev/mapper/mygroup-home" now stops with superblock/filesystem size
> mismatch, but I can't grow the fs into the new partition size, as
> "resize2fs" wants "e2fsck" (stopping with the mismatch) first.
>
> The fs is mountable and everything seems allright otherwise.
>
> Any pointers on how to update the superblock's size statement?
>
> Thanks, Joh
>
> _______________________________________________
> 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/
next prev parent reply other threads:[~2010-12-01 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 7:28 [linux-lvm] lvm2 and partition shringkin: superblock/filesystem size mismatch Johannes Graumann
2010-12-01 10:04 ` Lars Ellenberg
2010-12-01 10:10 ` Johannes Graumann [this message]
2010-12-01 13:45 ` [linux-lvm] [SOLVED]: " Johannes Graumann
2010-12-01 14:12 ` Lars Ellenberg
2010-12-01 14:23 ` Johannes Graumann
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='id56v8$fc4$1@dough.gmane.org' \
--to=johannes_graumann@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).