NFS export settings
Ste
125 Posts
November 20, 2020, 1:56 pmQuote from Ste on November 20, 2020, 1:56 pmHello,
I created an NFS export, but I didn't find where to specify it's size. Shall I assume that it can grow to use all available space in the cluster ? Or there is a default size limit ? Can I define a size limit ?
A second question would have been where to input client addresses, but I just read this will be a new feature in ver. 2.7 🙂
Thanks and bye. Ste
Hello,
I created an NFS export, but I didn't find where to specify it's size. Shall I assume that it can grow to use all available space in the cluster ? Or there is a default size limit ? Can I define a size limit ?
A second question would have been where to input client addresses, but I just read this will be a new feature in ver. 2.7 🙂
Thanks and bye. Ste
Last edited on November 20, 2020, 2:00 pm by Ste · #1
admin
2,930 Posts
November 20, 2020, 3:44 pmQuote from admin on November 20, 2020, 3:44 pmThe export is only limited by the data pool size of the cephfs layout in which the export resides. So you may try to created a pool limited in size and assign it to a cephfs layout and select the layout when creating the share. Maybe in the future we may add more restrictions.
Yes 2.7 we are supporting client address filters for export access.
The export is only limited by the data pool size of the cephfs layout in which the export resides. So you may try to created a pool limited in size and assign it to a cephfs layout and select the layout when creating the share. Maybe in the future we may add more restrictions.
Yes 2.7 we are supporting client address filters for export access.
DividedByPi
32 Posts
November 20, 2020, 7:09 pmQuote from DividedByPi on November 20, 2020, 7:09 pmHey Ste,
You may find some success by using CephFS quotas. I have had success having clients honoring quotas set, and it does show up the correct size for the client based on the quotas you set.
To set the quota, SSH into one of your petasan nodes that is handling NFS. To set quotas based on total bytes use this syntax:
setfattr -n ceph.quota.max_bytes -v <byte_amt> /some/path
where /some/path equals your NFS share mount point.
If this worked, when mounting your share on the client when you run a df, the quota should be observed.
You can also check on your quotas with the following syntax:
getfattr -n ceph.quota.max_bytes /some/path
good luck!
Hey Ste,
You may find some success by using CephFS quotas. I have had success having clients honoring quotas set, and it does show up the correct size for the client based on the quotas you set.
To set the quota, SSH into one of your petasan nodes that is handling NFS. To set quotas based on total bytes use this syntax:
setfattr -n ceph.quota.max_bytes -v <byte_amt> /some/path
where /some/path equals your NFS share mount point.
If this worked, when mounting your share on the client when you run a df, the quota should be observed.
You can also check on your quotas with the following syntax:
getfattr -n ceph.quota.max_bytes /some/path
good luck!
Last edited on November 20, 2020, 7:17 pm by DividedByPi · #3
Ste
125 Posts
November 23, 2020, 11:50 amQuote from Ste on November 23, 2020, 11:50 amGreat, it worked !
Thanks. 🙂
Great, it worked !
Thanks. 🙂
DividedByPi
32 Posts
November 24, 2020, 2:00 pmQuote from DividedByPi on November 24, 2020, 2:00 pmGlad to hear it!
Glad to hear it!
NFS export settings
Ste
125 Posts
Quote from Ste on November 20, 2020, 1:56 pmHello,
I created an NFS export, but I didn't find where to specify it's size. Shall I assume that it can grow to use all available space in the cluster ? Or there is a default size limit ? Can I define a size limit ?
A second question would have been where to input client addresses, but I just read this will be a new feature in ver. 2.7 🙂
Thanks and bye. Ste
Hello,
I created an NFS export, but I didn't find where to specify it's size. Shall I assume that it can grow to use all available space in the cluster ? Or there is a default size limit ? Can I define a size limit ?
A second question would have been where to input client addresses, but I just read this will be a new feature in ver. 2.7 🙂
Thanks and bye. Ste
admin
2,930 Posts
Quote from admin on November 20, 2020, 3:44 pmThe export is only limited by the data pool size of the cephfs layout in which the export resides. So you may try to created a pool limited in size and assign it to a cephfs layout and select the layout when creating the share. Maybe in the future we may add more restrictions.
Yes 2.7 we are supporting client address filters for export access.
The export is only limited by the data pool size of the cephfs layout in which the export resides. So you may try to created a pool limited in size and assign it to a cephfs layout and select the layout when creating the share. Maybe in the future we may add more restrictions.
Yes 2.7 we are supporting client address filters for export access.
DividedByPi
32 Posts
Quote from DividedByPi on November 20, 2020, 7:09 pmHey Ste,
You may find some success by using CephFS quotas. I have had success having clients honoring quotas set, and it does show up the correct size for the client based on the quotas you set.
To set the quota, SSH into one of your petasan nodes that is handling NFS. To set quotas based on total bytes use this syntax:
setfattr -n ceph.quota.max_bytes -v <byte_amt> /some/path
where /some/path equals your NFS share mount point.
If this worked, when mounting your share on the client when you run a df, the quota should be observed.
You can also check on your quotas with the following syntax:
getfattr -n ceph.quota.max_bytes /some/path
good luck!
Hey Ste,
You may find some success by using CephFS quotas. I have had success having clients honoring quotas set, and it does show up the correct size for the client based on the quotas you set.
To set the quota, SSH into one of your petasan nodes that is handling NFS. To set quotas based on total bytes use this syntax:
setfattr -n ceph.quota.max_bytes -v <byte_amt> /some/path
where /some/path equals your NFS share mount point.
If this worked, when mounting your share on the client when you run a df, the quota should be observed.
You can also check on your quotas with the following syntax:
getfattr -n ceph.quota.max_bytes /some/path
good luck!
Ste
125 Posts
Quote from Ste on November 23, 2020, 11:50 amGreat, it worked !
Thanks. 🙂
Great, it worked !
Thanks. 🙂
DividedByPi
32 Posts
Quote from DividedByPi on November 24, 2020, 2:00 pmGlad to hear it!
Glad to hear it!