I've got a volume that is unable to be moved or dumped, yet salvager thinks it's fine.
It appears that the cause of this problem is that a windows client attempted to create an over-2GB file, which failed. The current state of the volume is that it has a bogus directory entry for a 2GB-truncated file, which gives an I/O Error when attempting to access. It's almost like their is a very slight disconnect between what the file/vol server thinks is a LARGEFILE, and what the O/S does. Strangely enough, rsync is able to read the file, but cp is not. Probably a question of whather cp is largefile enabled on this old OS build. I'm not sure there's really anything to do here, but I'd be aware that there may be a off-by-one error or something in size limitations for large/non-large files somewhere. -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-6679 UMR Information Technology Fax: (573) 341-4216 _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
