samba - Jul 1998 - 9GB Drives Show Up as 4GB

In NT Explorer, my 9GB usr shares show up as 4GB.
Any suggestions?
Doug Smith

On Sat, 18 Jul 1998 02:47:48 +1000, you wrote:
>In NT Explorer, my 9GB usr shares show up as 4GB.
>Any suggestions?
>Doug Smith
This question should probably go in the FAQ as it is being asked more
and more now that very large disks are cheaper.

The system call which returns the free space for a drive, seems to
have a cap on it. On my 6GB share, the disk size was initially shown
as 2GB (I'm on Win95), with 2GB remaining free space. When finally I
put more than 4GB on the drive, the true disk space remaining was
shown.

Currently: 
	Win95b says:
1,800,372,224 bytes (1.67GB) used
  347,078,656 bytes (331MB) free
2,147,450,880 bytes (1.99GB) capacity

	Unix says:
server:~# df /dev/hda2
Filesystem         1024-blocks  Used Available Capacity Mounted on
/dev/hda2            5994607 5342510   341641     94%   /mnt/storage

Suggestions? Ignore it. When you run out of space, it'll start reading
right.


I've attached this as it's a more technical explanation, but it
doesn't seem to apply to me. (I do have Win95 OSR 2)

------- Start attachment ----------
From: M?czka, Miros?aw <mmm@bze.com.pl>
Date: Thu, 9 Jul 1998 16:49:53 +1000
>From Microsoft Win32 Programmer's Reference 
GetDiskFreeSpace
GetDiskFreeSpaceEx

Windows 95: 

The GetDiskFreeSpace function returns incorrect values for volumes
that
are larger than 2 gigabytes. The function caps the values stored into
*lpNumberOfFreeClusters and *lpTotalNumberOfClusters so as to never
report volume sizes that are greater than 2 gigabytes.
Even on volumes that are smaller than 2 gigabytes, the values stored
into *lpSectorsPerCluster, *
lpNumberOfFreeClusters, and *lpTotalNumberOfClusters values may be
incorrect. That is because the operating system manipulates the values
so that computations with them yield the correct volume size. 

Windows 95 OSR 2:

The GetDiskFreeSpaceEx function is available on Windows 95 systems
beginning with OEM Service Release 2 (OSR 2). The GetDiskFreeSpaceEx
function returns correct values for all volumes, including those that
are greater than 2 gigabytes.  

mmm

---------- End attachment ----------------

Regards

Anthony

"If all these pretty young things were laid end-to-end,
I wouldn't be the least bit surprised." - Dorothy Parker

"Smith, Doug K NWW" <Doug.K.Smith@nww01.usace.army.mil> wrote:
>In NT Explorer, my 9GB usr shares show up as 4GB.
How many bits you need for 4 *1024 *1024 *1024 (minus 1)? NT uses a
32-bit unsinged integer to get (non-NT) share sizes. Win95 even uses a
signed int.

As I heard NT boxes among each other are able to annouce share sizes
above 4GB, I expect Samba 1.9.19 (as `the NT4-Release') to show all the
9 GB to NT boxes. The Win95 explorer will still remain in showing 2GB
share size.

BTW, we share directories on a 3GByte partition to (among others) Win95
boxes. Except for the wrong share size, we didn't encounter any
problems. Question to the SMB gurus: Have we just been lucky? Should I
reduce the partition size?

Ludolf

On Fri, 17 Jul 1998, Smith, Doug K NWW wrote:
> In NT Explorer, my 9GB usr shares show up as 4GB.
> Any suggestions?
This is an M$ feature. They (M$) claim to have 64-bit variables in the NT
file sub-system, which may well be true, BUT many of the other M$ products
use 32 bits, some signed and some unsigned, to report queries made of the
file sub-system.

There has been some other correspondence on this list on the same subject.
Recently. Try reading it.


---
Peter Blake
ppb@hft.co.uk
ppb@baloo.tcp.co.uk