At 07:49 26-6-2001 -0400, J Landman wrote:
Folks:
Let me know if this is not the appropriate forum for this. I have what
I will call an annoying problem. It seems that cp/mv have stopped working
between xfs and the other file systems. Here are the basics:
uname -a : Linux genome.dtw.macsch.com 2.4.5-xfs #2 Thu Jun 21 03:06:30
EDT 2001 i686
unknown
(plain 2.4.5 using the xfs patches from last week for 2.4.5)
file system /work is a RAID 0 /dev/md0 device, striped across two disks on
one controller. Other file systems are reiserfs (or some ext2).
<snip>
This is a mandrake 8.0 system. I used the original Russell Mandrake
patched kernel until I started to notice this. I can move files around
using tar. Tar uses the same libraries as cp, with the additional librt,
and libpthread. This is all being done using the tcsh. This uses the
fileutils-4.0. I downloaded and handcompiled 4.1 of fileutils, and I get
the same behavior.
Did you compile the kernel with gcc or kgcc/egcs?
What else should I do? I just want to make this go away. File system was
built using the 1.0 mkfs. I have run xfs_check and xfs_repair -n on it.
I can back it up and rebuild the FS if needed. Let me know what you
think.
xfs_repair -n will not modify your filesystem. You need to run it normally
to actually repair the fs. I hardly think that rebuilding your fs is
needed. Nothing changed in the on-disk format.
There have been more reports of on-disk reporting with a kernel compiled
with 2.96 based compilers. So avoid using 2.96 to compile your kernel when
your data is valuable.
I made this point about compilers a lot clearer in the FAQ.
Cheers.
--
Seth
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.
|