Unfortunately no... The only detail I have is that the client is attempting to create a >2GB zip file, and it's obviously not working. I think what's happening though is that it is able to create one exactly 2GB or something like that.
2147483648 Aug 11 19:22 backup articles_m08-11-2005_17#57#52.zip The only reason I noticed this file is that there are only a small number of files on the volume, and the vol won't move or dump - and this has happened once to this user/volume in the past, likely the same cause. Maybe there is a >= 2GB somewhere instead of a > 2GB? -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-6679 UMR Information Technology Fax: (573) 341-4216 > -----Original Message----- > From: Jeffrey Altman [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 25, 2005 11:04 AM > To: Neulinger, Nathan > Cc: [email protected] > Subject: Re: [OpenAFS-devel] clients able to create corrupt > file on non-largefile server > > Um. Windows clients do not support files larger than 2GB. > The protocol the Windows CIFS client uses to speak to the AFS Client > Service does not permit the representation of files > 2GB. > > Is there any other details you can provide? > > > Neulinger, Nathan wrote: > > I take that back... rsync is just stupid and thinks it's reading the > > file but isn't... Very weird. > > > > -- Nathan > > > > ------------------------------------------------------------ > > Nathan Neulinger EMail: [EMAIL PROTECTED] > > University of Missouri - Rolla Phone: (573) 341-6679 > > UMR Information Technology Fax: (573) 341-4216 > > > > > > > >>-----Original Message----- > >>From: [EMAIL PROTECTED] > >>[mailto:[EMAIL PROTECTED] On Behalf Of > >>Neulinger, Nathan > >>Sent: Thursday, August 25, 2005 10:51 AM > >>To: [email protected] > >>Subject: [OpenAFS-devel] clients able to create corrupt file > >>on non-largefile server > >> > >>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 > >> > >> > > > > _______________________________________________ > > OpenAFS-devel mailing list > > [email protected] > > https://lists.openafs.org/mailman/listinfo/openafs-devel > _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
