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-2358 Lustre <p>An MGS has a NULL obd_fsops.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>cat /proc/fs/lustre/mgs/MGS/fstype LustreError: 4219:0:(lprocfs_status.c:604:lprocfs_rd_fstype()) ASSERTION( obd-&gt;obd_fsops != ((void *)0) ) failed: LustreError: 4219:0:(lprocfs_status.c:604:lprocfs_rd_fstype()) LBUG </pre> </div></div> CentOS 6.3 LU-2358

LBUG reading /proc/fs/lustre/mgs/MGS/fstype

Story Minor Resolved Fixed Emoly Liu John Hammond patch procfs Mon, 19 Nov 2012 18:01:07 +0000 Mon, 17 Dec 2012 10:01:05 +0000 Mon, 17 Dec 2012 10:01:05 +0000 Lustre 2.4.0 Lustre 2.4.0 0 5 <p>Please see <a href="http://review.whamcloud.com/#change,4635" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,4635</a>.</p> <p>I will review this patch.</p> <p>I am afraid this will not work if MGS is set up separately from MDT and/or if it is based on osd-zfs. Can we just remove fstype and mntdev entries from MGS/ completely?</p> <p>Sorry, I had wrong impression just after reading comments in patch. I see now that it will link properly. But I wonder still do we really need these entries?</p> <p>Andreas, do you have any idea about these entries?</p> <p>Mike, if they symlink to the proper OSD device, then it should be ok? One reason for these files is that the mnt dev is used by e2fsck to detect that the device is mounted by Lustre. It is also useful for the admin on occasions to see this. </p> <p>I worry that we will have many links in lustre procfs tree making that difficult to understand where each entry belongs to. I am just not sure how e2fsck uses that, but if all data is placed already in OSD procfs directory, maybe we need to check it there? For example, proposed patch makes two things - link proper OSD proc entry to the particular MGS and then link fstype and mntdev right from there to the MGS too. I wonder just if we have already proper OSD link, can't we check those fields there?</p> <p>Should we add a sanity.sh test to check all the readable lustre proc entries to avoid such error?</p> <p>An issue for the sanity check has been created; see <a href="https://jira.whamcloud.com/browse/LU-2376" title="Need a sanity check to ensure readable proc files are readable" class="issue-link" data-issue-key="LU-2376"><del>LU-2376</del></a>.</p> <p>Landed for 2.4</p> Development Rank 1|hzvcif: Rank (Obsolete) 5613