Unfortunately......
I couldnt check the /var/log/messages since its turned off. I had to turn it
off due to the
other problem I've been having. (see article with subject aic7xxx parity error
detected in data-in phase)
I was also curious if these two issues were related.....
I've already started an xfs_repair with the assume_xfs option...started it
yesterday at about
4pm....its still running....heh.
But then it is about 360gbs
*crosses fingers*
brian
-----Original Message-----
From: Seth Mos [mailto:knuffie@xxxxxxxxx]
Sent: Wednesday, October 23, 2002 5:30 PM
To: Brian Gulizia
Cc: linux-xfs@xxxxxxxxxxx
Subject: RE: Share suddenly empty
On Wed, 23 Oct 2002, Brian Gulizia wrote:
> I hadnt done anything to it. All I did was reboot, I got the "not a valid
> block
> device" when i tried to mout it, rebooted again and was able to mount it but
> it has
> nothing on it when I do an ls. You'll have to excuse my newbieness, but when
> you
> say let the filesystem do recovery, what do you mean? I didnt see anything
> about the
> kernel doing any recovering.
The recovery part is something the filesystem does after a "unclean
unmount" eg. poweroff. When you mount the filesystem it would be done
automatically. If recovery was required there will be a message during the
mount of the filesystem.
And if I am right there should at least be a message in you
/var/log/messages (or equivalent) stating that there was a filesystem
error. If not from the just attempted mount there should at least be one
from when the files first "dissappeard".
Did you already repair the filesystem per chance?
Check with mount if it is unmounted.
xfs_repair -n /dev/sdb? or xfs_check /dev/sdb? and check for errors or
other problems it finds. Mail that back to the list (zipped please).
If there is nothing serious in there you could attempt a repair of the
filesystem if you are couragesous ;-)
I'm going to bed here, maybe someone from america can pick this up *hint*
See you in 8 hours.
Cheers
Seth
|