https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-1367 Lustre <p>I am on the phone with our storage vendor. We have some corruption on the disk, and the file system when readonly. We suspect that there might be a FW issue in the RAID controller.</p> <p>When we run fsck, we see a couple of messages like this:</p> <p> Free inodes count wrong for group #45590 (1, counted=0).</p> <p>The storage vendor would like to know the LBA associated with this this data. Can you tell me how to find that?</p> <p>Thanks.</p> LU-1367

Help finding bad LBA

Task Minor Resolved Incomplete Peter Jones Roger Spellman Thu, 3 May 2012 15:55:42 +0000 Sat, 15 Mar 2014 01:01:42 +0000 Sat, 15 Mar 2014 01:01:42 +0000 0 2 <p>The "inode count wrong" is itself not associated with a particular block address. Instead, this is a side-effect of some previous error that was corrected (e.g. a corrupted or unreferenced inode being deleted), and now the summary count for the group that held that inode is incorrect.</p> <p>It is possible to find the filesystem block number for a particular inode using the "debugfs -c -R 'imap &lt;inode number&gt;' /dev/XXX" command. Once the filesystem block number is found, this needs to be converted to a sector number (usually block_number * 8, assuming 512-byte sectors) and added to the offset of the start of the partition (0, in the recommended case of using the whole device for a Lustre target).</p> <p>Andreas, Thanks for this info.<br/> From this message, I don't see the inode number, just the group number.<br/> If I knew the size of the group, I should would be able to calculate the LBA of that particular group, then I could use the offset of the inode count and free inodes to get their LBAs.<br/> Do you know the size of the group?</p> <p>Roger &#8211; can we mark this issue as resolved?<br/> Thanks,<br/> ~ jfc.</p> <p>Looks like we will not pursue this issue further.</p> Development Rank 1|hzw1rj: Rank (Obsolete) 10367