On Fri, Dec 13, 2002 at 04:47:59PM -0800, Conrad Minshall wrote:
I must go work other issues... and hope someone else follows up so EFBIG is
dealt with sensibly.
I checked in the simple fix (map EFBIG to NT_STATUS_DISK_FULL) so it's not
an immediate problem.
Jeremy.
On Wed, 2002-12-11 at 03:24, Conrad Minshall wrote:
My client maps NT_STATUS_DISK_FULL to EFBIG, but really this should be done
by observing some Windows server. With W2K/NTFS I had no success - using
SMB_SET_FILE_END_OF_FILE_INFO doesn't generate a sparse file so I fill up
the disk before
At 8:14 PM -0800 12/9/02, [EMAIL PROTECTED] wrote:
On Mon, Dec 09, 2002 at 08:10:00PM -0800, Conrad Minshall wrote:
A local filesystem has to return EFBIG to Samba (per POSIX write system
call def'n) and in the Samba source I'm looking at EFBIG isn't used
anywhere relevant to a WRITE_ANDX, in
At 10:36 AM -0800 12/7/02, [EMAIL PROTECTED] wrote:
On Sat, Dec 07, 2002 at 01:42:18AM -0800, Conrad Minshall wrote:
The server's
local filesystem has a maximum filesize of 16 Terabytes. If my
client attempts a writex with an offset of exactly 16TB then I see
ERRnoaccess
The code
On Mon, Dec 09, 2002 at 08:10:00PM -0800, Conrad Minshall wrote:
A local filesystem has to return EFBIG to Samba (per POSIX write system
call def'n) and in the Samba source I'm looking at EFBIG isn't used
anywhere relevant to a WRITE_ANDX, in particular it isn't in the
unix_dos_nt_errmap
I'm testing my smb client against Samba on FreeBSD. The server's
local filesystem has a maximum filesize of 16 Terabytes. If my
client attempts a writex with an offset of exactly 16TB then I see
ERRnoaccess rather than ERRdiskfull. Looking at some 3.0 sources, it
appears reply_write_and_X()
On Sat, Dec 07, 2002 at 01:42:18AM -0800, Conrad Minshall wrote:
I'm testing my smb client against Samba on FreeBSD. The server's
local filesystem has a maximum filesize of 16 Terabytes. If my
client attempts a writex with an offset of exactly 16TB then I see
ERRnoaccess rather than
