This worked ( I actually bought a larger disk). It also asked if
something changed with the partition, I said yes.
Vladimir V. Saveliev wrote:
Hello
If the partition you have problems with is not the last partition on the
disk, you can expand the partition with fdisk. Of course, to do that you
will have to delete partition which follows the partition to be
expanded.
(Please note that to have new partition table to make an effect you may
have to reboot after fdisk if there were mounted partitions of that hard
drive.)
Then you have to run
reiserfsck --rebuild-sb
It will ask you whether you ran resizer, and you have to answer No.
Then --rebuild-sb will change filesystem's block counting to spread over
whole device.
Then you have to run --rebuild-tree.
On Sat, 2006-03-25 at 12:47 +0200, Alftheo Potgieter wrote:
How do I resize the filesystem while it is corrupted?
Vitaly Fertman wrote:
Hello
On Tuesday 21 March 2006 01:44, alftheo potgieter wrote:
Hi
I'm using the latest reiserfsck (3.6.19),,
My filesystem got corrupted by an unexpected power loss. Initially, I
could mount the filesystem read-only with minor problems. As I had
nowhere to back it up, I ran reiserfsck --rebuild-tree, which could not
complete, as the filesystem was full.
it is possible to get such a corruption that fsck will need to
insert some extra metadata to successfully repair the fs. this
process may run out of disk space. I have an improved version
of reiserfsck, which detects these corruptions and avoid these
metadata insertion. however your fs already has these metadata
inserted and there is probably no space to proceed.
I will send you that improved reiserfsck, if it runs out of disk
space too, you need to enlarge you partition, enlarge fs, and run
reiserfsck again.
If you will need to enlarge the partition, before doing it,
please zero the space that will be added into the partition
to avoid mixing your reiserfs metadata with another reiserfs
metadata.
Now it is flagged as unmountable "to prevent further corruption". Is
there any way to restore the filesytem to the previous mountable but
corrupted state (which would be infinitely more useful)? I imagine
either finding the root node again or somehow growing the filesystem (as
I have since found enough space to grow it)
Any help would be useful.
alf
