From: Andy <genanr@emsphone.com>
To: "Lars Michael Jogbäck" <lm@swip.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with size after growing a device
Date: Mon, 9 Jul 2007 14:22:21 -0500 [thread overview]
Message-ID: <20070709192221.GA11684@thumper2> (raw)
In-Reply-To: <468A27B8.9000107@swip.net>
On Tue, Jul 03, 2007 at 12:40:56PM +0200, Lars Michael Jogbäck wrote:
> Hi,
>
> So, if I do:
> # cat /sys/block/sdk/size
> 4882708480
>
> and
> # blockdev --getsz /dev/sdk
> 3906166784
>
> Apparently /sys/block/sdk/size is updated with the new size, but
> whatever "blockdev --getsz" and "pvresize" is querying is not. If I
> reboot, everything works correctly.
>
I have mentioned this problem before with resizing non-partitioned devices,
then trying to resize the filesystem.
I consider the issue a bug, because different parts of the kernel have
a different size for the same device. It should be consistent, preferably
with the new size being reported both by the sys fs and by blockdev (then
hopefully xfs_growfs will work without a reboot).
Andy
prev parent reply other threads:[~2007-07-09 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 10:40 Problem with size after growing a device Lars Michael Jogbäck
2007-07-09 19:22 ` Andy [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=20070709192221.GA11684@thumper2 \
--to=genanr@emsphone.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@swip.net \
/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.