I'm running a server with Centos 3 that I have set up a smbfs share to a Buffalo LinkStation. The LS has 4 drives configured with RAID 5. Each disk has 1 TB capacity, so the resulting drive is approximately 2.7 TB.
When doing a df, the result shows 2 TB, and no used blocks. Is there some setting I can change so that Centos sees and uses all 2.7 TB or does Centos 3 not support this?
Steve Campbell
On 11/06/2009 09:04 AM, Steve Campbell wrote:
I'm running a server with Centos 3 that I have set up a smbfs share to a Buffalo LinkStation. The LS has 4 drives configured with RAID 5. Each disk has 1 TB capacity, so the resulting drive is approximately 2.7 TB.
When doing a df, the result shows 2 TB, and no used blocks. Is there some setting I can change so that Centos sees and uses all 2.7 TB or does Centos 3 not support this?
Steve Campbell
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Setting the blocksize did the trick for me.
block size = 4096
This goes in the "services" section, not global.
i.e.:
[xx-01] comment = xx-01 path = /data-store valid users = xx read only = No block size = 4096
Hope this helps.
Monty
Monty Shinn wrote:
On 11/06/2009 09:04 AM, Steve Campbell wrote:
I'm running a server with Centos 3 that I have set up a smbfs share to a Buffalo LinkStation. The LS has 4 drives configured with RAID 5. Each disk has 1 TB capacity, so the resulting drive is approximately 2.7 TB.
When doing a df, the result shows 2 TB, and no used blocks. Is there some setting I can change so that Centos sees and uses all 2.7 TB or does Centos 3 not support this?
Steve Campbell
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Setting the blocksize did the trick for me.
block size = 4096
This goes in the "services" section, not global.
i.e.:
[xx-01] comment = xx-01 path = /data-store valid users = xx read only = No block size = 4096
Hope this helps.
Monty
I had googled and found something about that setting, but....
Where exactly is this set? What file is that set in?
Thanks for the fast reply.
steve
On 11/06/2009 09:17 AM, Steve Campbell wrote:
Monty Shinn wrote:
On 11/06/2009 09:04 AM, Steve Campbell wrote:
I'm running a server with Centos 3 that I have set up a smbfs share to a Buffalo LinkStation. The LS has 4 drives configured with RAID 5. Each disk has 1 TB capacity, so the resulting drive is approximately 2.7 TB.
When doing a df, the result shows 2 TB, and no used blocks. Is there some setting I can change so that Centos sees and uses all 2.7 TB or does Centos 3 not support this?
Steve Campbell
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Setting the blocksize did the trick for me.
block size = 4096
This goes in the "services" section, not global.
i.e.:
[xx-01] comment = xx-01 path = /data-store valid users = xx read only = No block size = 4096
Hope this helps.
Monty
I had googled and found something about that setting, but....
Where exactly is this set? What file is that set in?
Thanks for the fast reply.
steve
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
It is set in the smb.conf file. It is located under /etc/samba/.
You will have to restart samba for the change to take place. Do that by issuing the following:
/etc/init.d/smb restart.
The setting is placed in the share definitions section, not in the global settings where server level definitions are placed.
See http://us1.samba.org/samba/docs/man/manpages-3/smb.conf.5.html for more details.
excerpt:
block size (S)
This parameter controls the behavior of smbd(8) http://us1.samba.org/samba/docs/man/manpages-3/smbd.8.html when reporting disk free sizes. By default, this reports a disk block size of 1024 bytes.
Changing this parameter may have some effect on the efficiency of client writes, this is not yet confirmed. This parameter was added to allow advanced administrators to change it (usually to a higher value) and test the effect it has on client write performance without re-compiling the code. As this is an experimental option it may be removed in a future release.
Changing this option does not change the disk free reporting size, just the block size unit reported to the client.
Default: //|block size|/ = |1024| /
Example: //|block size|/ = |4096|/
Hope this helps.
Monty
Monty Shinn wrote:
On 11/06/2009 09:17 AM, Steve Campbell wrote:
Monty Shinn wrote:
On 11/06/2009 09:04 AM, Steve Campbell wrote:
I'm running a server with Centos 3 that I have set up a smbfs share to a Buffalo LinkStation. The LS has 4 drives configured with RAID 5. Each disk has 1 TB capacity, so the resulting drive is approximately 2.7 TB.
When doing a df, the result shows 2 TB, and no used blocks. Is there some setting I can change so that Centos sees and uses all 2.7 TB or does Centos 3 not support this?
Steve Campbell
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Setting the blocksize did the trick for me.
block size = 4096
This goes in the "services" section, not global.
i.e.:
[xx-01] comment = xx-01 path = /data-store valid users = xx read only = No block size = 4096
Hope this helps.
Monty
I had googled and found something about that setting, but....
Where exactly is this set? What file is that set in?
Thanks for the fast reply.
steve
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
It is set in the smb.conf file. It is located under /etc/samba/.
You will have to restart samba for the change to take place. Do that by issuing the following:
/etc/init.d/smb restart.
The setting is placed in the share definitions section, not in the global settings where server level definitions are placed.
See http://us1.samba.org/samba/docs/man/manpages-3/smb.conf.5.html for more details.
excerpt:
block size (S) This parameter controls the behavior of smbd(8) <http://us1.samba.org/samba/docs/man/manpages-3/smbd.8.html> when reporting disk free sizes. By default, this reports a disk block size of 1024 bytes. Changing this parameter may have some effect on the efficiency of client writes, this is not yet confirmed. This parameter was added to allow advanced administrators to change it (usually to a higher value) and test the effect it has on client write performance without re-compiling the code. As this is an experimental option it may be removed in a future release. Changing this option does not change the disk free reporting size, just the block size unit reported to the client. Default: //|block size|/ = |1024| / Example: //|block size|/ = |4096|/Hope this helps.
Monty
OK, now I'm even more confused. I'm not running smb at all now. The only thing I do is mount the LinkStation using webmin as a smbfs system. It shows up in my mount as an smbfs system using smbmount. The Centos box is only acting as a client to the LinkStation, which is a Windows box running samba shares. Does the smb.conf file control smbmount and smb clients also.
The link you provided seems to imply that smb.conf controls how the machine works when it's a Samba server.
Sorry to be so thick.
steve
On 11/06/2009 10:24 AM, Steve Campbell wrote:
Monty Shinn wrote:
On 11/06/2009 09:17 AM, Steve Campbell wrote:
Monty Shinn wrote:
On 11/06/2009 09:04 AM, Steve Campbell wrote:
I'm running a server with Centos 3 that I have set up a smbfs share to a Buffalo LinkStation. The LS has 4 drives configured with RAID 5. Each disk has 1 TB capacity, so the resulting drive is approximately 2.7 TB.
When doing a df, the result shows 2 TB, and no used blocks. Is there some setting I can change so that Centos sees and uses all 2.7 TB or does Centos 3 not support this?
Steve Campbell
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Setting the blocksize did the trick for me.
block size = 4096
This goes in the "services" section, not global.
i.e.:
[xx-01] comment = xx-01 path = /data-store valid users = xx read only = No block size = 4096
Hope this helps.
Monty
I had googled and found something about that setting, but....
Where exactly is this set? What file is that set in?
Thanks for the fast reply.
steve
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
It is set in the smb.conf file. It is located under /etc/samba/.
You will have to restart samba for the change to take place. Do that by issuing the following:
/etc/init.d/smb restart.
The setting is placed in the share definitions section, not in the global settings where server level definitions are placed.
See http://us1.samba.org/samba/docs/man/manpages-3/smb.conf.5.html for more details.
excerpt:
block size (S) This parameter controls the behavior of smbd(8) <http://us1.samba.org/samba/docs/man/manpages-3/smbd.8.html> when reporting disk free sizes. By default, this reports a disk block size of 1024 bytes. Changing this parameter may have some effect on the efficiency of client writes, this is not yet confirmed. This parameter was added to allow advanced administrators to change it (usually to a higher value) and test the effect it has on client write performance without re-compiling the code. As this is an experimental option it may be removed in a future release. Changing this option does not change the disk free reporting size, just the block size unit reported to the client. Default: //|block size|/ = |1024| / Example: //|block size|/ = |4096|/Hope this helps.
Monty
OK, now I'm even more confused. I'm not running smb at all now. The only thing I do is mount the LinkStation using webmin as a smbfs system. It shows up in my mount as an smbfs system using smbmount. The Centos box is only acting as a client to the LinkStation, which is a Windows box running samba shares. Does the smb.conf file control smbmount and smb clients also.
The link you provided seems to imply that smb.conf controls how the machine works when it's a Samba server.
Sorry to be so thick.
steve
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
No, I may be the thick one here.
I thought you were using your Centos box as a server, not a client. I must have mis-read your original post.
Can't really help you much with the Buffalo box.
Sorry for sending you down a rabbit trail.
Monty
2009/11/6 Monty Shinn montys@videopost.com:
Setting the blocksize did the trick for me.
Not so sure you need to do that, I have a 40TB share over samba that presents itself properly with no additional configuration.
Ben
Thanks all.
Think I'll go ask over on the webmin list since that's where and how I created the mounted share. I don't see anything on the Buffalo that'll allow me to change anything.
steve
Benjamin Donnachie wrote:
2009/11/6 Monty Shinn montys@videopost.com:
Setting the blocksize did the trick for me.
Not so sure you need to do that, I have a 40TB share over samba that presents itself properly with no additional configuration.
Ben _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Benjamin Donnachie wrote:
2009/11/6 Monty Shinn montys@videopost.com:
Setting the blocksize did the trick for me.
Not so sure you need to do that, I have a 40TB share over samba that presents itself properly with no additional configuration.
Ben _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Some clients need it, mac osx 10.4.x for sure.
ms
Steve Campbell wrote:
When doing a df, the result shows 2 TB, and no used blocks. Is there some setting I can change so that Centos sees and uses all 2.7 TB or does Centos 3 not support this?
You often don't need to be concerned about the amount of space being reported by a network file system, it could be a limitation in the client driver itself. Usually what happens when the client thinks it is full is it just says so via df but still can send data because the file system really isn't full.
My NAS cluster actually has an option to "fake" what it reports to clients as how large the volume is for reasons similar to this.
What I would suggest is assuming the LS is empty, fill it up and see what happens.
nate
-
Benjamin Donnachie -
Monty Shinn -
nate -
Steve Campbell