> Hi all,
>
> I've been having a problem that I thought might be related to Tridge's, but
> maybe not:
>
> When copying directories over NFS (v2) from OSF1 clients to a Linux server
> with XFS, files and directories will mysteriously "vanish" after the cp
> completes, however, enough of the file/dir remains (i.e., the name of the
> file in the inode table) that an ls of the dir will yield this:
>
>
> [root@sdssdp9 rawdata]# ls CANNOT_RM.51940/
> ls: CANNOT_RM.51940/guider: No such file or directory
Are you doing anything special to hit this? I move files around NFS all
the time, I have not seen this. Anything else you can tell us to try to
recreate it? Does this only happen on RAID?
> Aug 18 00:14:10 sdssdp9 kernel: xfs_create looping, dir ino 0xa25e000, ino
> 0x101000800, md(9,0)
> Aug 18 00:14:10 sdssdp9 kernel:
> Aug 18 00:14:10 sdssdp9 kernel: nfsd: non-standard errno: -990
The -990 is EFSCORRUPTED, generated directly after the "xfs_create
looping" message, which comes out of a trap commented like this:
/*
* xfs_create_broken is a trap routine to isolate the cause of a
infinite
* loop condition reported in IRIX 6.4 by PV 522864. If no
occurances
* of this error recur (that is, the trap code isn't hit), this
routine
* should be removed in future releases.
*/
so I guess we won't remove it just yet... ;-)
-Eric
|