Details
-
Technical task
-
Resolution: Fixed
-
Critical
-
Lustre 2.4.2
-
13609
Description
An existing filesystem on a 2.4.2 MDT that was previously upgraded from Lustre 2.1, 1.8, 1.6, has about 1.8M inodes in use:
lfs df -i UUID Inodes IUsed IFree IUse% Mounted on myth-MDT0000_UUID 2621440 1837764 783676 70% /myth[MDT:0] myth-OST0000_UUID 921856 315326 606530 34% /myth[OST:0] myth-OST0001_UUID 475168 168933 306235 36% /myth[OST:1] myth-OST0002_UUID 715264 585400 129864 82% /myth[OST:2] myth-OST0003_UUID 688128 600027 88101 87% /myth[OST:3] myth-OST0004_UUID 921856 118677 803179 13% /myth[OST:4] filesystem summary: 2621440 1837764 783676 70% /myth
Running "lctl lfsck_start -t namespace -M myth-MDT0000" it shows the following statistics on completion:
lctl get_param mdd.*.lfsck_namespace mdd.myth-MDT0000.lfsck_namespace= name: lfsck_namespace magic: 0xa0629d03 version: 2 status: completed flags: scanned-once,inconsistent param: (null) time_since_last_completed: 3 seconds time_since_latest_start: 126 seconds time_since_last_checkpoint: 3 seconds latest_start_position: 13, N/A, N/A last_checkpoint_position: 2621440, N/A, N/A first_failure_position: N/A, N/A, N/A checked_phase1: 3688305 checked_phase2: 222 updated_phase1: 1762893 updated_phase2: 147 failed_phase1: 0 failed_phase2: 0 dirs: 92332 M-linked: 833 nlinks_repaired: 0 lost_found: 0 success_count: 3 run_time_phase1: 122 seconds run_time_phase2: 0 seconds average_speed_phase1: 30232 items/sec average_speed_phase2: 222 objs/sec real-time_speed_phase1: N/A real-time_speed_phase2: N/A current_position: N/A
The number of inodes reported "checked_phase1" is about 2x the number of actual inodes in the filesystem, which looks like a bug if LFSCK is checking each inode twice.
Also, the "updated_phase1" value is always showing almost all of the inodes are "updated", even if LFSCK is run multiple times. This seems like a possibly separate bug if this is caused by IGIF inodes, or other problems with older filesystems.