This is interesting. The salvager appears to unlink the file in a child
process, then try to open it again later in the parent (am I reading
this correctly?):
# fgrep salvage.inodes /tmp/salvager.truss.log
159: open("/viceps/salvage.inodes.c2t0d2s6.159", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 8
159: stat("/viceps/salvage.inodes.c2t0d2s6.159", 0xFFBECF90) = 0
159: open("/viceps/salvage.inodes.c2t0d2s6.159", O_RDWR) = 7
162: unlink("/viceps/salvage.inodes.c2t0d2s6.159") = 0
159: open("/viceps/salvage.inodes.c2t0d2s6.159", O_RDONLY) Err#2 ENOENT
159: unlink("/viceps/salvage.inodes.c2t0d2s6.159") Err#2 ENOENT
I can provide more "truss" context if it would be helpful, but that sure
looks odd. It also seems that maybe it isn't a question of the length
of the pathname.
-norm
On Tue, 2003-02-25 at 13:46, Derrick J Brashear wrote:
> On 25 Feb 2003, Norman P. B. Joseph wrote:
>
> > 02/25/2003 13:35:23 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager /viceps
> > 536871053)
> > 02/25/2003 13:35:34 Scanning inodes on device /dev/rdsk/c2t0d2s6...
> > 02/25/2003 13:36:01 No applicable vice inodes on c2t0d2s6; not salvaged
> > Temporary file /viceps/salvage.inodes.c2t0d2s6.82 is missing...
>
> So what file does exist? strace or truss on the salvager is ok.
>
>
>
> _______________________________________________
> OpenAFS-info mailing list
> [EMAIL PROTECTED]
> https://lists.openafs.org/mailman/listinfo/openafs-info
--
Norman Joseph, Systems Engineer [EMAIL PROTECTED] IC|XC
Concurrent Technologies Corporation 814/269.2633 --+--
Global Systems Center NI|KA
*** Be kind, for everyone you meet is fighting a great battle ***
_______________________________________________
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info
