Details
-
Technical task
-
Resolution: Fixed
-
Critical
-
Lustre 2.4.0
-
None
-
6666
Description
It would be very useful to have an OBD_COMPAT_NOIGIF flag stored in the last_rcvd file after the first OI Scrub has completed and stored the IGIF FID-in-LMA and in the OI, and after this it should refuse access to IGIF FIDs that are not in the OI.
The OBD_COMPAT_NOIGIF flag should also be set for newly formatted filesystems, since they should never have IGIF inodes from the beginning.
This prevents users from trying to access e.g. the OSD root inode "[2:0:0]" even without knowing the generation number, since OSD_OII_NOGEN == 0, and this allows accessing a file just by guessing.
Attachments
Issue Links
- is related to
-
LU-2780 Use real inode for .lustre/fid
-
- Resolved
-
Having this depend on initial OI scrub to check each time whether IGIF FIDs are allowed isn't as robust as I would have liked - the SF_UPGRADE step would only be relevant the first time after an upgrade and not after a later backup/restore. This opens the possibility of IGIF lookups even after the first OI scrub is finished. However, it is at least preventing this access of the time, and much better than we have today.