In this case, the problem is somewhat unrelated: The partitions don't seem to
fit on disk in this way. That is, there isn't sufficient space for 512 * 1024 *
1024 bytes before sda2.
Was that layout created using setup-storage? Probably yes. What I do suspect is
some rounding issue, and, well this is the culprit: The partition has been
created such as to end at a cylinder boundary, which is considered for the final
disk layout, but not for intermediate checks.
My mistake, sorry.
I built the filesystem with setup-storage, using version FAI version
3.3.4 and for sda1 a size of '512', with no unit.
And then ran 3.3.5-experimental2 to resize /usr, with the same size
of '512' for sda1, which seems to give a different result.
I have done it again using a size of 512MiB, and it works as
expected: the volume is resized, but the filesystem is not.
Huch? Why is that expected behavior? Shouldn't everything be resized? Could you
paste the logs?
http://paste.debian.net/68014/
I really misunderstood your previous mail, where you said "resize2fs
will *not* be used on normal partitions".
I see you're using resize2fs in this case, but it fails.
Err, I should have looked at the resize2fs man page more closely. I somehow had
assumed that 512 byte sectors was the default. Added the necessary "s" as unit
in 3.3.5+experimental3. Could you please retry and report back whether it's
fixed?
You will need one more try, as resize2fs is still complaining:
(CMD) resize2fs /dev/vg0/usr 16777216s 1> /tmp/Hdv5kRmDAd 2> /tmp/FCrWPAlXCo
Executing: resize2fs /dev/vg0/usr 16777216s
Command resize2fs /dev/vg0/usr 16777216s had exit code 1
(STDERR) resize2fs 1.41.11 (14-Mar-2010)
(STDERR) Please run 'e2fsck -f /dev/vg0/usr' first.
The full log is at http://paste.debian.net/68019/.
--
Nicolas
