Details
-
Story
-
Resolution: Fixed
-
Minor
-
Lustre 2.4.0
-
CentOS 6.3
-
5613
Description
An MGS has a NULL obd_fsops.
cat /proc/fs/lustre/mgs/MGS/fstype LustreError: 4219:0:(lprocfs_status.c:604:lprocfs_rd_fstype()) ASSERTION( obd->obd_fsops != ((void *)0) ) failed: LustreError: 4219:0:(lprocfs_status.c:604:lprocfs_rd_fstype()) LBUG
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?