<!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:20100413152559.GR26478@laptop165.dbai.tuwien.ac.at"
type="cite">
<blockquote type="cite">
<pre wrap="">e2fsck is still grumpy:
(CMD) e2fsck -f /dev/vg0/usr 1> /tmp/2jcv6xhbVE 2> /tmp/qT7zDl1RU4
Executing: e2fsck -f /dev/vg0/usr
Command e2fsck -f /dev/vg0/usr had exit code 8
(STDERR) e2fsck 1.41.11 (14-Mar-2010)
(STDERR) e2fsck: need terminal for interactive repairs
<a class="moz-txt-link-freetext" href="http://paste.debian.net/68701/">http://paste.debian.net/68701/</a>
</pre>
</blockquote>
<pre wrap=""><!---->
Could you run e2fsck interactively, doing
e2fsck -p -f /dev/vg0/usr
to see whether a safe repair can be done non-interactively? I wonder if your
filesystem is corrupted anyway and that e2fsck run before resize2fs wouldn't
even be necessary otherwise.
</pre>
</blockquote>
Works fine after an fai-sysinfo boot:<br>
<br>
<tt>root@lutil:~# e2fsck -p -f /dev/vg0/usr<br>
/dev/vg0/usr: 41374/393216 files (0.6% non-contiguous), 227117/1572864
blocks<br>
root@lutil:~# </tt><br>
<br>
At this time resize2fs doesn't require a prior e2fsck, though.<br>
<br>
-- <br>
Nicolas<br>
</body>
</html>