[OpenAFS-devel] clients able to create corrupt file on non-largefile server

[Neulinger, Nathan]

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.=20

Maybe there is a >=3D 2GB somewhere instead of a > 2GB?

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-6679
UMR Information Technology             Fax: (573) 341-4216
=20

> -----Original Message-----
> From: Jeffrey Altman [mailto:jaltman@columbia.edu]=20
> Sent: Thursday, August 25, 2005 11:04 AM
> To: Neulinger, Nathan
> Cc: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] clients able to create corrupt=20
> file on non-largefile server
>=20
> 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.
>=20
> Is there any other details you can provide?
>=20
>=20
> Neulinger, Nathan wrote:
> > I take that back... rsync is just stupid and thinks it's reading the
> > file but isn't... Very weird.
> >=20
> > -- Nathan
> >=20
> > ------------------------------------------------------------
> > Nathan Neulinger                       EMail:  nneul@umr.edu
> > University of Missouri - Rolla         Phone: (573) 341-6679
> > UMR Information Technology             Fax: (573) 341-4216
> > =20
> >=20
> >=20
> >>-----Original Message-----
> >>From: openafs-devel-admin@openafs.org=20
> >>[mailto:openafs-devel-admin@openafs.org] On Behalf Of=20
> >>Neulinger, Nathan
> >>Sent: Thursday, August 25, 2005 10:51 AM
> >>To: openafs-devel@openafs.org
> >>Subject: [OpenAFS-devel] clients able to create corrupt file=20
> >>on non-largefile server
> >>
> >>I've got a volume that is unable to be moved or dumped, yet salvager
> >>thinks it's fine.=20
> >>
> >>It appears that the cause of this problem is that a windows client
> >>attempted to create an over-2GB file, which failed.=20
> >>
> >>The current state of the volume is that it has a bogus=20
> directory entry
> >>for a 2GB-truncated file, which gives an I/O Error when=20
> attempting to
> >>access. It's almost like their is a very slight disconnect=20
> >>between what
> >>the file/vol server thinks is a LARGEFILE, and what the O/S does.=20
> >>
> >>Strangely enough, rsync is able to read the file, but cp is not.
> >>Probably a question of whather cp is largefile enabled on=20
> this old OS
> >>build.
> >>
> >>I'm not sure there's really anything to do here, but I'd be=20
> 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:  nneul@umr.edu
> >>University of Missouri - Rolla         Phone: (573) 341-6679
> >>UMR Information Technology             Fax: (573) 341-4216
> >>_______________________________________________
> >>OpenAFS-devel mailing list
> >>OpenAFS-devel@openafs.org
> >>https://lists.openafs.org/mailman/listinfo/openafs-devel
> >>
> >>
> >=20
> > _______________________________________________
> > OpenAFS-devel mailing list
> > OpenAFS-devel@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20