Quote:
|
What possessed you to run --rebuild-tree when the problem was not a filesystem error but simply a lack of free space?[/b]
|
I had encountered this before; however, it was because the partition was dirty due to system crashes as well as hibernations (where the system hangs when trying to wake up).
df had shown the partition had about 1.6GB space; however, trying to write a 1MB gave the
insufficient disk space messages. After
fsck --rebuild-tree, I gained back the 1.6GB space and was able to use it. So, when this happened recently, I just did the
fsck --rebuild-tree again (not realizing the HD was really full).
Quote:
At the moment the only way out that I can see is to take an image of the partition (which you apparently already did), reformat the partition, and then recover your files from the image using loopback mount, something like this:
mount -o loop,ro -t reiser /data/part.img /mnt/oldhome[/b]
|
I tried this option before; however, the mount process complains with the following error messages:
Code:
[root@Mi:/opt/tmp 21%] # mount -o loop=/dev/loop0,ro -t reiserfs /opt/tmp/sdb8.img /mnt
mount: cannot mount /dev/loop0 read-only
The other option I have thought of is to put in a new HD. Create a partition of the same size. Use
dd to image the partition on to this newly create partition. Then, resize the partition before running the fsck again to see if that will do the trick.