[274] in testers
undelete rtpc 6.4 afs
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Mon Nov 20 19:29:57 1989
Date: Mon, 20 Nov 89 19:29:29 -0500
From: Jonathan I. Kamens <jik@PIT-MANAGER.MIT.EDU>
To: geer@ATHENA.MIT.EDU
Cc: testers@ATHENA.MIT.EDU
In-Reply-To: geer@ATHENA.MIT.EDU's message of Mon, 20 Nov 89 09:51:02 -0500 <8911201451.AA09279@e40-342f-2.MIT.EDU>
From: geer@ATHENA.MIT.EDU
Date: Mon, 20 Nov 89 09:51:02 -0500
undelete catastrophically failed:
e40-342f-2% undelete Makefile
undelete: An undeleted already exists.
Do you wish to continue with the undelete and overwrite that version? y
undelete: Invalid argument
e40-342f-2% more Makefile
Makefile: No such file or directory
e40-342f-2% undelete Makefile
undelete: Makefile: No such file or directory
in addition, the first undelete operation
took over 2 minutes elasped time.
--dan
From: geer@ATHENA.MIT.EDU
Date: Mon, 20 Nov 89 09:58:06 -0500
IN ADDITION, THAT UNDELETE OPERATION DID A
HARD RM ON ALL OTHER FILES IN THAT SAME
DIRECTORY, RESULTING IN A LOSS OF SEVERAL
DAYS WORK. THAT'S RIGHT, >35 RM'S & RMDIR'S
AS THE RESULT OF THAT UNDELETE OPERATION!!
THIS IS A SHOW STOPPER ON UNDELETE AND
======================================
ON THE RELEASE THAT CONTAINS IT.
================================
--DAN
I cannot duplicate this behavior. The following information would be
helpful:
1. Were you working in AFS, NFS, or local disk?
2. Do you have undelete aliased to anything (i.e. are you passing it
any arguments that I didn't see from your example)?
3. Was there an undeleted version of Makefile in the directory? If
so, what kind of file was it (regular file, sym-link, directory)?
4. Can you duplicate this? If so, can you tell me how to duplicate
it?
If you find that you cannot duplicate this occurrence, my first guess
about the cause would be that I am failing to check a malloc
somewhere, resulting in a pointer to a bad string, resulting in an
attempt to unlink "", resulting in the removal of the entire contents
of the directory, as you have described.
Of course, it is difficult to find a bug that only manifests itself
when the program is running low on memory, but I will put some effort
into seeing if that is the cause.
jik
