linux-kernel - Re: Problem with size after growing a device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 9 Jul 2007 14:22:21 -0500
From:	Andy <genanr@...phone.com>
To:	Lars Michael Jogbäck <lm@...p.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Problem with size after growing a device

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/