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.
Works fine after an fai-sysinfo boot:
r...@lutil:~# e2fsck -p -f /dev/vg0/usr
/dev/vg0/usr: 41374/393216 files (0.6% non-contiguous),
227117/1572864 blocks
r...@lutil:~#
At this time resize2fs doesn't require a prior e2fsck, though.
So I hope that the addition of -p fixes this (3.4~beta1+experimental7).
It does :-) . Looks like it's the end of this everlasting thread.
Thanks for your great job with setup-storage.
--
Nicolas
