On Wednesday 09 March 2005 17:21, Derrick J Brashear wrote: > On Wed, 9 Mar 2005, Hans-Gunther Borrmann wrote: > > On the destination the VolserLog contains: > > Wed Mar 9 16:52:11 2005 VAttachVolume: Failed to open > > /vicepcp/V0537085440.vl (errno 2) > > Wed Mar 9 16:52:11 2005 1 Volser: CreateVolume: volume 537085440 > > (usr.md0) created > > unable to allocate inode: File exists > > Namei or inode?
Namei I'm unsure why the file would exist, but if it's namei, I > suppose you could use a syscall tracer and see what's getting EEXIST, I'd > be curious to hear what you have that's in the way. > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info Hello I have traced volserver on the destination of the failing move. Unfortunately I could not use truss (# truss -p 15496 truss: 0915-023 Cannot control process #15496.). So I had to trace the kernel. You find the trace report in /afs/uni-freiburg.de/usr/b/borrmann/public/volsertrace I traced FILE ACTIVITY (open,close,read,write). Hope you'll find a hint what is wrong with this partition. Gunther -- ________________________________________________________________ Hans-Gunther Borrmann <[EMAIL PROTECTED]> Rechenzentrum der Universitaet Freiburg Hermann-Herder-Str. 10, D79104 FREIBURG Tel.: +49 761/203-4652 Fax: +49 761/203-4643 _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
