Hi,

I'm converting one of my systems to run RAID level 1 (mirroring). One of the
final steps in the conversion is running resize2fs because the filesytem
has become a little smaller because the raid superblock is stored at the
end of the partition.

Anyway, when I run "resize2fs /dev/md0" it says "attempt to read block on
filesytem resulted in a short read while trying to resize /dev/md0". After
that, it says the filesytems has been successfully resized to the new size.
However, when I run e2fsck again (or reboot the sytem), it says that the
partition table or superblock is corrupt, meaning it hasn't resized the
filesytem.

My platform is AMD K6-2 400 MHz, the filesytem is an ext3 filesystem,
resize2fs is version 1.26 (from slackware, I believe slackware 9,
bootdisks). I have successfully converted a filesystem on another computer
to a RAID system using these slackware bootdisks.

Does anybody have any idea what is causing this and how to fix it?

TIA

Halfgaar
--
To send email, change nospam.com into yahoo.com.

Halfgaar wrote:

I don't know if anybody is going to answer this question, if you do, don't
. I've just recreated the filesytem. It was a bit more work, but at least
now it works.

Halfgaar
--
To send email, change nospam.com into yahoo.com.