[LU-4504] User quota problem after Lustre upgrade (2.1.4 to 2.4.1)

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Affects Version/s: Lustre 2.4.1
• Severity: 3
• Assignee: Niu Yawei (Inactive)
• Reporter: Oz Rentas (Inactive)

Description

After the upgrade at KIT, the user quotas are not reported correctly. The quota for root seems to be OK. The user quota is 0 on all OSTs, which is wrong.

e.g for root:

[root@pfs2n13 ~]# lfs quota -u root -v /lustre/pfs2wor2/client/
Disk quotas for user root (uid 0):
Filesystem kbytes quota limit grace files quota limit
grace
/lustre/pfs2wor2/client/
4332006768 0 0 - 790 0
0 -
pfs2wor2-MDT0000_UUID
2349176 - 0 - 790 - 0
-
pfs2wor2-OST0000_UUID
134219820 - 0 - - -

• -
  pfs2wor2-OST0001_UUID
  12 - 0 - - - -
  -
  pfs2wor2-OST0002_UUID
  134219788 - 0 - - -
• -

for a user
[root@pfs2n3 ~]# lfs quota -v -u aj9102 /lustre/pfs2wor1/client/
Disk quotas for user aj9102 (uid 3522):
Filesystem kbytes quota limit grace files quota limit
grace
/lustre/pfs2wor1/client/
448 0 0 - 3985 0 0
-
pfs2wor1-MDT0000_UUID
448 - 0 - 3985 - 0
-
pfs2wor1-OST0000_UUID
0 - 0 - - - -
-
pfs2wor1-OST0001_UUID
0 - 0 - - - -
-
pfs2wor1-OST0002_UUID
0 - 0 - - - -
-

Issue Links

• is blocked by: LU-5018 e2fsprogs build failed
• is related to: LU-4345 failed to update accounting ZAP for user
• is related to: LU-5129 CLONE - failed to update accounting ZAP for user

Comments

[Minh Diep]

Thank you Sir!

[Oz Rentas (Inactive)]

Yes, a long time ago. Please close. Thanks!

[Minh Diep]

[e-mail], orentas, have you resolved this issue? do you need anything else from this ticket?

[Niu Yawei (Inactive)]

We dont think manually fixing the OST object is not a good idea. Since the filesystem have more than 100 million files.
Cu is expecting a better way to fix this issue,

I can't think of any other good ways to fix the bad IDs. I think running a script instead of repeating the commands manually would be better?

[Rajeshwaran Ganesan]

Hello Niu,

We dont think manually fixing the OST object is not a good idea. Since the filesystem have more than 100 million files.
Cu is expecting a better way to fix this issue,

Thanks,
Rajesh

[Niu Yawei (Inactive)]

I updated the way of how to fix bad ID for OST object (see my previous comment). Thanks.

[John Fuchs-Chesney (Inactive)]

Hello Oz,
We've recently heard from another site that Niu's fixes have resolved the quota problems they were seeing.
Has DDN installed a new version at this site, with those patches?
If so, do you have any new news on this?
Thanks,
~ jfc.

[Niu Yawei (Inactive)]

For the huge UID/GIDs caused by the lustre defect described in
LU-4345: Is there a way to repair the bad IDs on the OST objects?

Fix bad IDs on existing OST objects:

• Find the objects with bad IDs first (mount the OST device with ldiskfs to check IDs of each file or use debugfs without umount)
• Get the correct ID from MDT (see Lustre manual 13.14 to identify which file the object belongs to) the set the correct IDs to these OST objects.
• Set correct IDs for the objects on OST directly.

[Oz Rentas (Inactive)]

From the customer:

It's good news that you found possible reasons for the problem.
We will install the patches during our next maintenance which is expected to take place during the next 2 months. However, DDN will have to provide a Lustre version which includes those patches.

For the huge UID/GIDs caused by the lustre defect described in
LU-4345: Is there a way to repair the bad IDs on the OST objects?

[Niu Yawei (Inactive)]

http://review.whamcloud.com/10227