samba - Mar 2005 - Mac/Samba capacity detection problem

Hi,
 
We are having a problem between
 Linux 2.6.9-prep #12 SMP Mon Dec 6 12:08:34 CST 2004 x86_64 x86_64 
x86_64 GNU/Linux
(Samba version 3.0.9-1.fc3)
 
and
 
MAC OS X 10.3.5
Samba version 3.0.0rc2
 
Basically the issue is that the Mac reports the Linux share as being 
full, and won't allow files to be copied. 
 
We are able to work around it using this method:
Create a folder on the Linux share with the same name as the folder to 
be copied from MAC.
Then when you try copy and paste, it will let you select "Replace".
 
 
Here's what I'm getting with the DF command:
 
Linux server with plenty of free space:
 
[root@TeranII ~]# df -H
Filesystem             Size   Used  Avail Use% Mounted on

/dev/mapper/vg00-lv00
                             5.0T   2.3T   2.8T  45%    /home
 
 
Macs with mounted  Linux drive shows erroneous drive space:
 
[cinemac:/sbin] root# df -H
Filesystem                                           Size   Used  Avail 
Capacity  Mounted on
//USERNAME@AMOS/SOURCE          602G   2.2T  -1.6T   365%    /Volumes/Source
 
 
sincityedit:/Volumes/source root# df -H
Filesystem                                         Size   Used  Avail 
Capacity  Mounted on
//USERNAME@AMOS/SOURCE        602G   2.2T  -1.6T   365%    /Volumes/source
 
 
Windows mapped drive to Linux shows  correct free space:
 
 Directory of Y:\
 
03/22/2005  09:51a      <DIR>          .
12/30/2004  10:00a      <DIR>          ..
03/22/2005  10:16a      <DIR>          _Admin

               0 File(s)              0 bytes
               3 Dir(s)  2,765,958,938,624 bytes free
 
 
I'm not sure what I can do to isolate the problem.  Can you give me some 
advice?
 
Thanks,
Carlos

Your problem is the following...
 
OS X 10.3.x can't cope with seeing Samba shares that are larger than 2 TB.  
If the Mac sees anything larger, in the "info" listing on the share,
it will
tell you the true size (i.e., 2.8 TB), but then it will tell you there is 0  
space left. 
 
Don't get me started on what a piece of (fill in the blank) Macs are for  
networking. And Netatalk is no picnic either. You'll have the same problem
with
large shares and AFP.
 
Anyway, the solution is to either: 
 
a)  partition your hard drive so that any given share can't have more  than
2
TB of space 
or 
b)  use quotas, and set the quota for the user or group that owns the  share 
to be smaller than 2 TB. 
 
I use option b. Works like a charm. Took me about 4 months to realize this  
was the problem. Hope I can save you some headaches and heartaches.
Andy Liebman
 
In a message dated 3/23/2005 5:17:58 P.M. Eastern Standard Time,  
cknowlton@update.fsix.com writes:

Hi,

We are having a problem between
Linux 2.6.9-prep #12 SMP  Mon Dec 6 12:08:34 CST 2004 x86_64 x86_64 
x86_64 GNU/Linux
(Samba  version 3.0.9-1.fc3)

and

MAC OS X 10.3.5
Samba version  3.0.0rc2

Basically the issue is that the Mac reports the Linux share as  being 
full, and won't allow files to be copied. 

We are able to  work around it using this method:
Create a folder on the Linux share with  the same name as the folder to 
be copied from MAC.
Then when you try  copy and paste, it will let you select "Replace".


Here's what I'm  getting with the DF command:

Linux server with plenty of free  space:

[root@TeranII ~]# df -H
Filesystem         Size   Used  Avail Use% Mounted  on

/dev/mapper/vg00-lv00
5.0T    2.3T   2.8T  45%    /home


Macs with  mounted  Linux drive shows erroneous drive space:

[cinemac:/sbin]  root# df -H
Filesystem                Size   Used  Avail  
Capacity  Mounted on
//USERNAME@AMOS/SOURCE       602G   2.2T  -1.6T   365%     /Volumes/Source


sincityedit:/Volumes/source root# df  -H
Filesystem                    Size   Used  Avail 
Capacity  Mounted  on
//USERNAME@AMOS/SOURCE        602G    2.2T  -1.6T   365%     /Volumes/source


Windows mapped drive to Linux shows  correct  free space:

Directory of Y:\

03/22/2005  09:51a   <DIR>           .
12/30/2004  10:00a      <DIR>     ..
03/22/2005  10:16a       <DIR>          _Admin

0 File(s)         0 bytes
3 Dir(s)  2,765,958,938,624 bytes free


I'm not  sure what I can do to isolate the problem.  Can you give me some  
advice?

Thanks,
Carlos

Glad I could help :)
 
In a message dated 3/24/2005 2:50:23 P.M. Eastern Standard Time,  
cknowlton@update.fsix.com writes:

I tried  the quota option, that did the trick!

thank  you!
Carlos