When you're over the soft limit, you *should* see an '*' in the listing, as 
well as time left in the grace period. We've had mixed success with that 
actually working however.
Cameron

On 1/9/19 5:21 AM, Moreno Diego (ID SIS) wrote:
Hi ANS,

About the soft limits and not receiving any warning or notification when the 
soft quota is reached, this would be the expected behavior. The soft quota is 
used together with the grace period to give some “extra” time to the user to 
remove inodes/blocks, as per the Lustre Operations Manual:

Soft limit -- The grace timer is started once the soft limit is exceeded. At 
this point, the user/group/project can still allocate block/inode. When the 
grace time expires and if the user is still above the soft limit, the soft 
limit becomes a hard limit and the user/group/project can't allocate any new 
block/inode any more. The user/group/project should then delete files to be 
under the soft limit. The soft limit MUST be smaller than the hard limit. If 
the soft limit is not needed, it should be set to zero (0).

I’m not aware of any warnings triggered by Lustre when the soft quota is 
reached, though that would be interesting to have. I know some people using 
external tools to monitor Lustre quotas and trigger warnings or similar for 
users exceeding their soft quota.

Regards,

Diego


From: lustre-discuss 
<lustre-discuss-boun...@lists.lustre.org><mailto:lustre-discuss-boun...@lists.lustre.org>
 on behalf of ANS <ans3...@gmail.com><mailto:ans3...@gmail.com>
Date: Wednesday, 9 January 2019 at 10:00
To: "lustre-discuss@lists.lustre.org"<mailto:lustre-discuss@lists.lustre.org> 
<lustre-discuss@lists.lustre.org><mailto:lustre-discuss@lists.lustre.org>
Subject: Re: [lustre-discuss] LFS Quota

Dear All,

Can anyone look into it.

Thanks,
ANS

On Mon, Jan 7, 2019 at 6:38 PM ANS 
<ans3...@gmail.com<mailto:ans3...@gmail.com>> wrote:
Dear All,

I am trying to set quota on lustre but unfortunately i have issued the below 
commands:-

tunefs.lustre --param ost.quota_type=ug /dev/mapper/mds1
checking for existing Lustre data: found
Reading CONFIGS/mountdata

   Read previous values:
Target:     data-MDT0000
Index:      0
Lustre FS:  data
Mount type: ldiskfs
Flags:      0x1001
              (MDT no_primnode )
Persistent mount opts: user_xattr,errors=remount-ro
Parameters:  
mgsnode=192.168.2.9@o2ib:192.168.2.10@o2ib<mailto:mgsnode=192.168.2.9@o2ib:192.168.2.10@o2ib>
  
failover.node=192.168.2.9@o2ib:192.168.2.10@o2ib<mailto:failover.node=192.168.2.9@o2ib:192.168.2.10@o2ib>

   Permanent disk data:
Target:     data-MDT0000
Index:      0
Lustre FS:  data
Mount type: ldiskfs
Flags:      0x1041
              (MDT update no_primnode )
Persistent mount opts: user_xattr,errors=remount-ro
Parameters:  
mgsnode=192.168.2.9@o2ib:192.168.2.10@o2ib<mailto:mgsnode=192.168.2.9@o2ib:192.168.2.10@o2ib>
  
failover.node=192.168.2.9@o2ib:192.168.2.10@o2ib<mailto:failover.node=192.168.2.9@o2ib:192.168.2.10@o2ib>
 ost.quota_type=ug

After this i have issued lctl conf_param home.quota.mdt=ugp and now i am able 
to see quota enabled in mdt but will there be any affect to the above version 
as i have issue that command to 2 mdts where i am having 4 mdts in total. Do i 
need to issue any further commands to revert those.

After enabling quota and file space crossed soft limit but i am unable to get 
warning till it reached near hard limit.

Can anyone help me out.

Thanks,
ANS


--
Thanks,
ANS.



_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org>
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Reply via email to