Russel Ingram wrote:
> I have seen umount related things in the archives but nothing that seems
> to match what I am experiencing here. I just installed the kernel and xfs
> utils that come on the ProPack 1.4 CD. I created an xfs filesytem on
> /dev/hda4 (now after having copied
> everything out of it to a temp dir. The filesystem created fine and
> mounted fine. I was even able to copy the old fs back to it with no
> problems. I unmounted the new fs to mount it back into its normal mount
> point in the dir tree (/home), but when I went to mount it back in it gave
> be a bad superblock or too many filesystems mounted error. xfs_check
> didn't report anything, but after running xfs_repair on it it mounted
> ok. I umounted it again to see if the error was going to occur again and
> it did. It seems the filesystem becomes corrupt every time umount is run
> on it. Is this a known problem? Is there an easy way around it?
Hmm as long a the FS was cleanly un-mounted this should be occurring.
Run the theca command after un-mounting the file system.
xfs_logprint -t /dev/ide/host0/bus0/target0/lun0/part4
send us the output.
> Russ Ingram
> Gargoyle Computer Consulting