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? 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
Sorry. I forgot the VolserLog:
Fri Mar 11 14:38:57 2005 VAttachVolume: Failed to open /vicepcp/V0537085534.vl (errno 2)
Fri Mar 11 14:38:57 2005 1 Volser: CreateVolume: volume 537085534 (usr.sperling) created
unable to allocate inode: File exists
Fri Mar 11 14:38:57 2005 1 Volser: ReadVnodes: Restore aborted
Fri Mar 11 14:38:57 2005 1 Volser: Delete: volume 537085534 deleted
Gunther
If you look into /vicepcp/AFSIDat/S=/SNo+U/special
is there anything? If so remove the subtree
/vicepcp/AFSIDat/S=/SNo+U
and - if existent - /vicepcp/V0537085534.vl
and try again. The message "unable to allocate inode: File exists" looks like there is some volume special file from an earlier try around.
Hartmut
-- ----------------------------------------------------------------- Hartmut Reuter e-mail [EMAIL PROTECTED] phone +49-89-3299-1328 RZG (Rechenzentrum Garching) fax +49-89-3299-1301 Computing Center of the Max-Planck-Gesellschaft (MPG) and the Institut fuer Plasmaphysik (IPP) ----------------------------------------------------------------- _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
