Whamcloud Community JIRA

Whamcloud Community JIRA https://jira.whamcloud.com This file is an XML representation of an issue en-us

9.4.14

940014

05-12-2023

[LU-5462] trigger OI https://jira.whamcloud.com/browse/LU-5462 Lustre <p>After restart of MDT we got this error. What does mean?<br/> LustreError: 0-0: nbp7-MDT0000: trigger OI scrub by RPC for <span class="error">[0x200088c7c:0x14:0x0]</span>, rc = 0 <span class="error">[1]</span></p> LU-5462

trigger OI

Question/Request Minor Resolved Not a Bug nasf Mahmoud Hanafi Fri, 8 Aug 2014 01:49:48 +0000 Wed, 29 Oct 2014 16:30:14 +0000 Wed, 29 Oct 2014 16:30:14 +0000 Lustre 2.4.3 0 4 <p>Fan Yong</p> <p>Could you please advise with this one?</p> <p>Thanks</p> <p>Peter</p> <p>Hi Mahmoud,</p> <p>What is the output for "cat /proc/fs/lustre/osd-ldiskfs/nbp7-MDT0000/oi_scrub" ?</p> <p>nbp7-mds1 ~ # cat /proc/fs/lustre/osd-ldiskfs/nbp7-MDT0000/oi_scrub <br/> name: OI_scrub<br/> magic: 0x4c5fd252<br/> oi_files: 1<br/> status: completed<br/> flags:<br/> param:<br/> time_since_last_completed: 48833 seconds<br/> time_since_latest_start: 51587 seconds<br/> time_since_last_checkpoint: 48833 seconds<br/> latest_start_position: 12<br/> last_checkpoint_position: 536870913<br/> first_failure_position: N/A<br/> checked: 66205633<br/> updated: 2<br/> failed: 0<br/> prior_updated: 0<br/> noscrub: 94<br/> igif: 519<br/> success_count: 3<br/> run_time: 2753 seconds<br/> average_speed: 24048 objects/sec<br/> real-time_speed: N/A<br/> current_position: N/A</p> <p>The OI scrub is used for rebuilding crashed "FID=>ino/gen" mapping. These message means that during your system running, it found bad "FID=>ino/gen" mapping, then triggered OI scrub to repair the inconsistency automatically. It may be because of data crash, it also may be because of system upgrade, but of course, we cannot say there are no any non-known bugs in the code as to trigger OI scrub by wrong.</p> <p>From the output "cat /proc/fs/lustre/osd-ldiskfs/nbp7-MDT0000/oi_scrub", your system has ever run OI scrub for 3 times, and two items (mappings) have been repaired in the latest run. Since the OI scrub has completely already, we can generally say that your system comes back to consistency again. So you can keep it there without anything else, the system should can work well. But if you want to know more about the system status, you can disable OI scrub auto trigger mechanism by "echo 0 > /proc/fs/lustre/osd-ldiskfs/nbp7-MDT0000/auto_scrub", then when found bad OI mapping next time, the system will not repair the inconsistency automatically, instead, it may cause related application failure, and then we can try to dump more logs.</p> <p>Hi Mahmoud,<br/> Do we still have anything to resolve under this ticket? Or can we close it? Thanks!</p> <p>can be closed</p> <p>ok thanks Mahmoud</p> Development Rank 1|hzwt7j: Rank (Obsolete) 15219