At 22:33 19-12-2000 -0600, Lord, Steve wrote:
If my memory serves me correctly, xfs_repair etc were all in
in the root filesystem on Irix.
They are installed in /usr/bin under linux
from linux-2.4-xfs/cmd/xfs/configure
# Defaults:
ac_help=
ac_default_prefix=/usr/local
# Any additions from configure.in:
ac_default_prefix=/usr
./configure --help
Directory and file names:
--prefix=PREFIX install architecture-independent files in PREFIX
[/usr]
So does this need to be changed? Two ac_default_prefix is overdone anyways ;-)
If XFS fails to run log recovery at mount time then it is in a
pretty sorry state. There is a mount option not to run recovery,
which will give you a readonly filesystem for the really desperate,
it is quite possible that it will shut itself down if corrupted
metadata is detected during access in this case (and the shutdown
code in linux was not working too well).
I noticed that yes, but in this case there was an old xfs_log on disk fro a
test-5 kernel and if you then hit the reset button the newer test-11 can
not mount the older style xfs_log.
So this was not a case of a sorry state ;-)
I did have the luck that /usr was mounted so I could use xfs_repair to fix
the xfs_log on disk (it seems to know about both types of xfs_log)
This is because my home machine has xfs* commands in /usr/bin
At work they live in /bin these days
If the mount system call is not returning an error code for a
failed XFS mount that sounds like a bug.
Yep, no errors to be seen anywhere.
I just didn't had /home/seth anymore !! (/home was not mounted during boot)
Also, ask Martin Peterson at LinuxCare about an xfs aware
version of the LinuxCare rescue disk, that would be a useful
thing to have.
The root fs is ext2 so I always have access to the xfs* commands in general.
A redhat bootdisk with XFS kernel onboard is then probably enough to fix
the system using the ext2 root fs.
Steve
<snip>
Bye
--
Seth
Has anybody seen my lightbulb?
I _really_ need some light here.
|