Apparently your kernel or file system has a serious bug. As your
private email to me demonstrated, if "empty" is an empty directory and
"d" is a directory, then the system call rename("d", "empty") does not
decrement the link count of ".", and this corrupts the file system.
What sort of file system are the files on?
normal SCSI hard disk, standard file system, i.e. efs (no XFS).
I assume IRIX 5.3 has a 'rename' system call, and that 'rename' is not
emulated by lower-level calls? You should be able to check this by
using "par -isSS mv -fT empty d".
OK:
lorenz 22% par -isSS /var/tmp/coreutils-5.97/src/mv -fT a b
0mS par( 753): was sent signal SIGUSR1
2mS par( 753): END-pause() errno = 4 (Interrupted system
call)
2mS par( 753): received signal SIGUSR1
2mS par( 753): sigreturn(0x7fffaa98) OK
2mS mv( 753): execve(/var/tmp/coreutils-5.97/src/mv,
0x7fffaf3c, 0x7fffaf50) OK
I am wondering whether SGI still maintains a publicly readable bug
tracking system. I'd be hoping to find a reference whether that issue
also applied to efs and where it was fixed.
I also found http://www-uxsup.csx.cam.ac.uk/pub/public_patches/SGI/6.1/patch1674.relnotes
According to this description the bug is not limited to xfs.
Patch 1409 is still available, but probably it will apply only on the
XFS version of IRIX 5.3.
Changing the subject slightly:
<https://support.sgi.com/content_request/8277/index.html> says
SGI last released IRIX 5.3 in May 1996 and stopped supporting it in
January 2002. That same reference says that SGI has expired all IRIX
releases other than the current one, 6.5. So there is no point in
your reporting this bug to SGI unless the bug also occurs in IRIX 6.5.
I didn't expect so :-)
Are there old patch sets from SGI for IRIX 5.3 that you could apply to
your system? Perhaps they might fix the problem.
I've applied already every applicable patch I could get hold of. You
can still get quite some of them at ftp://ftp.sgi.com/support/Patches/5.3.
I also got the Y2K patches from ftp://ftp.mayn.de/pub/really_old_stuff/irix/oldstuff/
Is it still important that new GNU utilities run on this old system,
or are you just trying to help out by using IRIX 5.3 as a porting
target to debug the coreutils installation procedure? If the latter,
then I suspect it's not worth the trouble: we typically are worried
about porting only to systems that actively employ recent coreutils
apps in practical use.
the IRIX machine is not mission critical to me :-)
It's a toy, not a production machine. I use it for testing code on
akward systems :-)
Sometimes problems showing up on such systems can be relevant for
more modern ones as well.