I am running a REHL 4.3 server with samba RPMs: 3.0.10-1.4e.9 When an os X client connects to our samba server it can copy files from the server an overwrite other files that already exist. However when it comes time to create a file, it fails, where this process works correctly from a windows system. In addition, I can go to where the volume is mounted on the os X (10.3.7) machine and copy files there. This isn't a problem for me, but it is for my users, has anyone else experienced this? thanks, Dan
I have done some digging and found out more. The problem seems to be that OS X is reporting the 5TB drive as 1TB and since there is over 1TB on the drive, it shows as full. Does anyone know of a work around for this? thanks, Dan On Thu, 2006-08-17 at 13:44 -0500, Daniel Davidson wrote:> I am running a REHL 4.3 server with samba RPMs: > > 3.0.10-1.4e.9 > > When an os X client connects to our samba server it can copy files from > the server an overwrite other files that already exist. However when it > comes time to create a file, it fails, where this process works > correctly from a windows system. In addition, I can go to where the > volume is mounted on the os X (10.3.7) machine and copy files there. > > This isn't a problem for me, but it is for my users, has anyone else > experienced this? > > thanks, > > Dan >
Am 17.08.2006 23:42 Uhr schrieb "Daniel Davidson" <danield@igb.uiuc.edu>:> I have done some digging and found out more. The problem seems to be > that OS X is reporting the 5TB drive as 1TB and since there is over 1TB > on the drive, it shows as full. Does anyone know of a work around for > this?Upgrade to 10.4.x - IIRC, 10.3.x does use 32bit offsets for filesystem type, which implies a 4TB maximum size. We have 10.4.x users accessing a 4.4TB store here, which reports storage size fine. Be advised though, that Apple is shipping an ancient self-hacked release of Samba (3.0.10), and all sorts of breakage may be due to this. Regards, Harald -- harald wagener technical lead it fcb wilkens an der alster 42 20099 hamburg hwagener@hamburg.fcb.com t. +49(0)40-2881-1252 http://www.fcb.com/de
I was finally able to fix my problem yesterday. It seemed that OSX was assuming that my block size 1024 where it was actually 4096. I put in a: block size = 4096 on the share and that fixed it. It now shows as a 4.92TB size on 10.3.9 Dan On Fri, 2006-08-18 at 09:37 +0200, Wagener, Harald wrote:> Am 17.08.2006 23:42 Uhr schrieb "Daniel Davidson" <danield@igb.uiuc.edu>: > > > I have done some digging and found out more. The problem seems to be > > that OS X is reporting the 5TB drive as 1TB and since there is over 1TB > > on the drive, it shows as full. Does anyone know of a work around for > > this? > > Upgrade to 10.4.x - IIRC, 10.3.x does use 32bit offsets for filesystem type, > which implies a 4TB maximum size. > > We have 10.4.x users accessing a 4.4TB store here, which reports storage > size fine. > > Be advised though, that Apple is shipping an ancient self-hacked release of > Samba (3.0.10), and all sorts of breakage may be due to this. > > Regards, > Harald >