Michael Wood,
Thanks to your proposition I was able to intercept the size information sent to windows by samba using the dfree command and have displayed the proper size.
The only thing I did was adding


dfree command = /usr/local/samba/bin/dfree

and in the dfree script I put :

df $1 | tail -1 | awk '{printf "%.0f %.0f",  $(NF-4),$(NF-2)}'

And suddently windows was able to calculate the proper size of my ceph partition.

Thank you again that helped me alot.
signature

*Alphé Salas*
Ingeniero T.I

Descripción: cid:[email protected]*Kepler Data Recovery*

*Asturias 97, Las Condes**
Santiago- Chile**
*((*56 2) 362 7529*

[email protected]
*www.kepler.cl <http://www.kepler.cl>*

On 10/24/2012 11:45 AM, Michael Wood wrote:
Hi

On 24 October 2012 16:41, alphe salas michels <[email protected]> wrote:
Thank you for your proposition!

I tryed to lie about the block size,  but unfortunatly windows blocksize buffer 
is coded into 2 bytes (short int). so the size upper to that like Ceph that has 
1MB of block size will not be handled the proper way.

My guess (it is just an assuption) is that samba can detect who connects to it and if it 
is a true windows workstation /server then the samba lures the count by multiplying the 
amount of blocks by 1MB / (blocksize from 1K to 64K). In order to allow people to play 
with the samba "block size = " parameter in the smb.conf.
Well, my suggestion is just a guess.  Did you try supplying your own
script for the "dfree command"?

I have not tried it myself.

Alphé Salas
Ingeniero T.I

Kepler Data Recovery

Asturias 97, Las Condes
Santiago- Chile
((56 2) 362 7529

[email protected]
www.kepler.cl

On 10/24/2012 11:26 AM, Michael Wood wrote:

Hi

On 24 October 2012 15:41, alphe salas michels <[email protected]> wrote:
Dear developement team,

I want to share a massive storage  casted with Ceph by samba with windows
workstations.

All works well. My problem so is that in windows the ceph storage size
statistics are wrong. Instead of seeing a 44TB hard drive I see a 176GB hard
drive.

Under linux that issue doesn't show. The size are properly reported.

I investigated around and it seems that the problem belongs in the unability
for windows
to treat blocksize over 65k and by default the block size is 4K.

Don't know how you can solve that issue but I really need to get that
working right.
I don't know if this will help, but it might be worth a try.  There's
a "dfree command" option that specifies a command to run to get the
free disk space:

http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#DFREECOMMAND

So if Windows doesn't like the block size, maybe you could lie about
the block size and then calculate the number of blocks based on the
fake block size.

There's also a "max disk size" option that may or may not make any difference:

http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#MAXDISKSIZE

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Reply via email to