[LU-9423] Wrong uid and gid for ost objects

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Affects Version/s: Lustre 2.7.0
• Severity: 3
• Assignee: Peter Jones
• Reporter: Mahmoud Hanafi

Description

We have discovered  objects that have the wrong UID or GID. For example on one filesystem there are over >600000 files effect.

 

Here is the details:

 ls -ln /nobackupp8/file_removed_for_security
-rw-r--r-- 1 10576 40770 0 Dec 8 21:40 /nobackupp8/file_removed_for_security


lfs path2fid /nobackupp8/file_removed_for_security
[0x36045b238:0x6f94:0x0]


lfs getstripe /nobackupp8/file_removed_for_security

/nobackupp8/file_removed_for_security
lmm_stripe_count: 1
lmm_stripe_size: 1048576
lmm_pattern: 1
lmm_layout_gen: 0
lmm_stripe_offset: 272
 obdidx objid objid group
 272 48704742 0x2e72ce6 0

# debugfs -c -R "stat /O/0/d$((48704742 % 32))/48704742" /dev/mapper/nbp8_13_OST272
debugfs 1.42.13.wc5 (15-Apr-2016)
/dev/mapper/nbp8_13_OST272: catastrophic mode - not reading inode or group bitmaps
Inode: 361442 Type: regular Mode: 0666 Flags: 0x80000
Generation: 2149307429 Version: 0x00000027:023c6769
User: 0 Group: 0 Size: 0
File ACL: 0 Directory ACL: 0
Links: 1 Blockcount: 0
Fragment: Address: 0 Number: 0 Size: 0
 ctime: 0x584a43d1:00000000 -- Thu Dec 8 21:40:33 2016
 atime: 0x00000000:00000000 -- Wed Dec 31 16:00:00 1969
 mtime: 0x584a43d1:00000000 -- Thu Dec 8 21:40:33 2016
crtime: 0x584a43c0:3db75e98 -- Thu Dec 8 21:40:16 2016
Size of extra inode fields: 28
Extended attributes stored in inode body: 
 lma = "08 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 e6 2c e7 02 00 00 00 00 " (24)
 lma: fid=[0x100000000:0x2e72ce6:0x0] compat=8 incompat=0
 fid = "38 b2 45 60 03 00 00 00 94 6f 00 00 00 00 00 00 " (16)
 fid: parent=[0x36045b238:0x6f94:0x0] stripe=0
EXTENTS:

 

What would cause this discrepancy and how do we fix them.