[lustre-discuss] Problems with quota after adding a new OST
Massimo Sgaravatto
massimo.sgaravatto at pd.infn.it
Mon Apr 11 23:36:33 PDT 2016
Indeed when I created that filesystem I simply ran on the MDS:
lctl conf_param cmshome.quota.ost=u
lctl conf_param cmshome.quota.mdt=u
and this was enough.
As I tried to explain in my mail, the problem started when I added
another OST to this filesystem.
And now I have an OST with quota, and another one where quota is disabled !
I have the feeling that the problem is somehow due to the inactive OST
ost1 between the two online OSTs:
client# lfs quota -v -u fanzago /homeui
Disk quotas for user fanzago (uid 716):
Filesystem kbytes quota limit grace files quota limit
grace
/homeui 16777812* 1000000 1100000 - 187 0
0 -
cmshome-MDT0000_UUID
156 - 0 - 187 - 0
-
cmshome-OST0000_UUID
550544 - 812688 - - - -
-
quotactl ost1 failed.
cmshome-OST0002_UUID
16227112 - 0 - - -
- -
Total allocated inode limit: 0, total allocated block limit: 812688
Some errors happened when getting quota info. Some devices may be not
working or deactivated. The data in "[]" is inaccurate.
On 12/04/2016 08:28, PGabriele wrote:
> Hi Massimo,
> Since lustre 2.5 (I guess) formatting the OST using the specific
> parameter it's no more necessary. You should simply enable it using the
> lctl command.
>
> On Tuesday, 12 April 2016, Massimo Sgaravatto
> <massimo.sgaravatto at pd.infn.it <mailto:massimo.sgaravatto at pd.infn.it>>
> wrote:
>
> Any hints ?
>
> Should I try to change (using lctl conf_param) the attribute:
>
> osd-ldiskfs.cmshome-OST0002.quota_slave.enabled
>
>
> on the new OST from 'none' to 'u' to fix the problem ?
>
> Thanks, Massimo
>
>
> On 08/04/2016 18:40, Massimo Sgaravatto wrote:
>
> Hi
>
> We are running Lustre 2.7.0. We have problems with quota on a
> filesystem.
>
> This filesystem was initially composed of a single OST, and at
> that time
> quota was enable on the MDT simply doing:
>
> lctl conf_param cmshome.quota.ost=u
> lctl conf_param cmshome.quota.mdt=u
>
> Nothing was needed on the OST (besided specifying "--param
> ost.quota_type=ug" when formatting).
>
> Problems started when we added a new OST (OST0002: there is also a
> deactived OST0001). This was formatted using "--param
> ost.quota_type=ug"
> but quota is disabled on this OST. [*]
>
> Do I need to somehow explicitly enable quota on this OST ? How
> and why ?
>
>
> Thanks a lot, Massimo
>
>
> [*]
>
> # lfs quota -v -u sgaravat /homeui
> Disk quotas for user sgaravat (uid 741):
> Filesystem kbytes quota limit grace files
> quota limit
> grace
> /homeui 357356 400000 410000 - 2
> 0 0
> -
> cmshome-MDT0000_UUID
> 0 - 0 - 2
> - 0
> -
> cmshome-OST0000_UUID
> 355784 - 372168 - -
> - -
> -
> quotactl ost1 failed.
> cmshome-OST0002_UUID
> 1572 - 0 - -
> - -
> -
> Total allocated inode limit: 0, total allocated block limit: 372168
> Some errors happened when getting quota info. Some devices may
> be not
> working or deactivated. The data in "[]" is inaccurate.
>
>
>
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
>
>
>
> --
> www: http://paciucci.blogspot.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1901 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20160412/61ba6fd7/attachment.bin>
More information about the lustre-discuss
mailing list