From: Andreas Dilger <adilger@turbolabs.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] e2fsck probs with LVM and 2.4.9-ac9+
Date: Sun, 23 Sep 2001 22:17:29 -0600 [thread overview]
Message-ID: <20010923221729.U14526@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0109221900090.23118-100000@zeke.goatskin.org>
On Sep 22, 2001 19:11 -0400, Shane Shrybman wrote:
> When I attempted to upgrade to 2.4.9-ac9 and ac14 from 2.4.9-ac6 I ran
> into a problem.
>
> With either of these kernels (I didn't try any others between ac6 and
> ac14) the kernel boots fine and lvm-mod gets loaded ok but when the first
> filesystem that is on an lv gets mounted e2fsck complains and drops me to
> admin prompt. The error message is something like this:
>
> The filesystem size (according to the superblock) is 524288 blocks
> the physical size of the device is 57344
> ...
>
> When I reboot back into 2.4.9-ac6 everything is fine after e2fsck.
>
> I have e2fsprogs version 1.19, do I need a more recent version?
That depends on how big you expect the devices to be. I would suspect
an LVM error, but it is hard to say which one causes the problem. If
you boot your old kernel, do lvscan, and compare to output of lvscan
on new kernel. Likewise output of /proc/partitions and "df" to see
how big each LV should be.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-09-24 4:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-22 23:11 [linux-lvm] e2fsck probs with LVM and 2.4.9-ac9+ Shane Shrybman
2001-09-24 4:17 ` Andreas Dilger [this message]
2001-09-24 11:17 ` Heinz J . Mauelshagen
2001-09-24 22:23 ` Shane Shrybman
2001-09-25 6:38 ` Werner John
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=20010923221729.U14526@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=linux-lvm@sistina.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.