<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote
cite="mid:20100408153938.GK15504@laptop165.dbai.tuwien.ac.at"
type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">Huch? Why is that expected behavior? Shouldn't everything be resized? Could you
paste the logs?
</pre>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="http://paste.debian.net/68014/">http://paste.debian.net/68014/</a>
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.
</pre>
</blockquote>
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap="">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 <a class="moz-txt-link-freetext" href="http://paste.debian.net/68019/">http://paste.debian.net/68019/</a>.
</pre>
</blockquote>
<pre wrap=""><!---->
Could you briefly hack a "-f" to the resize2fs calls in Commands.pm? The man
page doesn't quite tell whether this will override this e2fsck requirement; if
not, we'll really need to do so, which might be pretty time consuming.
</pre>
</blockquote>
It does override the e2fsck requirement, resize2fs seems ok, but the
result is.... well, unexpected <span class="moz-smiley-s1"><span> :-) </span></span>:<br>
<br>
<tt>Filesystem 1K-blocks Used Available Use% Mounted on<br>
/dev/mapper/vg0-usr 6159800 -1278720 7123948 - /target/usr</tt><br>
<br>
After the end of the installation, the partition is still 6G wide.<br>
<br>
-- <br>
Nicolas<br>
</body>
</html>