Hi Eric,
thank`s a lot for your fast answer !
I have compiled the newest xfs-tools and I was able to recover the
Fileystem ide1(22,2) (=/usr) which has the same Problems at booting the
machine as the ide1(22,3).
After installing a minimal Debian on a new harddisk, I was able to do the
xfs_repair on the ide1(22,2), and I was able to mount this partition and
was glad, that all files of this partition
where ok.
I do the same at the ide1(22,3) and mounted it, but there was only the
"lost+found" directory with many "lost+found" files.
A simply "df" showed me, that the capacity shows 80 % (the same as before
the crash.)
Is there a chance, to rescue my files on this (=/home) Partition ?
Thank you for your help
Christian
Eric Sandeen <sandeen@xxxxxxx>
21.09.2002 19:31
An: christian_binder@xxxxxxxxxxx
Kopie: linux-xfs@xxxxxxxxxxx
Thema: Re: xfs-patch on kernel 2-4-19
Hi Christian -
On Sat, 21 Sep 2002 christian_binder@xxxxxxxxxxx wrote:
> A "dmesg" give me after booting the machine the following text:
...
> SGI XFS with no debug enabled
> XFS mounting filesystem ide1(22,2)
> Starting XFS recovery on filesystem: ide1(22,2) (dev: 22/2)
> Ending XFS recovery on filesystem: ide1(22,2) (dev: 22/2)
That one mounted fine...
> XFS mounting filesystem ide1(22,3)
> XFS: corrupted root inode
> XFS: device 0x1603- Root inode 128 is not a directory
And this one has problems.
> Unable to handle kernel NULL pointer dereference at virtual address
Can you run this through ksymoops?
> xfs_create looping, dir ino 0xc30739, ino 0xc307c1, ide1(22,2)
This is odd, this is on the filesystem that said it mounted OK...
> I was very surprised, that a "ls" in some directories of the /usr -
> Partition shows me files (e. g. the smbd.pid-Sambafile), and a "ls -lia"
> shows me the same files not. A "rm filename" says, that there is no such
> file or directory.
>
> If I want to do a "xfs_check" on the other Partitions, it wouldnt start;
> the process hangs up.
> A "xfs_repair" do the same.
Maybe you can do an strace of the process to see where it stops? Also,
make sure you have the latest version of the tool...
-Eric
|