Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Lustre 2.4.3
-
3
-
13490
Description
The following LBUG appeared at customer site, during the mount process on all OSS in lustre 2.4.3 version.
LustreError: 12838:0:(fld_handler.c:172:fld_server_lookup()) ASSERTION(fld->lsf_control_exp ) failed: LustreError: 12838:0:(fld_handler.c:172:fld_server_lookup()) LBUG Pid: 12838, comm: mount.lustre Call Trace: libcfs_debug_dumpstack+0x55/0x80 [libcfs] lbug_with_loc+0x47/0xb0 [libcfs] fld_server_lookup+0x2f7/0x3d0 [fld] osd_fld_lookup+0x71/0x1d0 [osd_ldiskfs] osd_remote_fid+0x9a/0x280 [osd_ldiskfs] osd_index_ea_lookup+0521/0x850 [osd_ldiskfs] dt_lookup_dir+0x6f/0x130 [obdclass] llog_osd_open+0x485/0xc00 [obdclass] llog_open+0xba/0x2c0 [obdclass] mgc_process_log [mgc] mgc_process_config [mgc] lustre_process_log [obdclass] server_start_targets [obdclass] server_fill_super [obdclass] lustre_fill_super[obdclass] get_sb_nodev lustre_get_sb vfs_kern_mount do_kern_mount do_mount sys_mount system_call_fastpath
This issue seems the same as LU-3126 for which a patch has been landed in lustre 2.5. Unfortunately no patch has been provided for lustre 2.4 release.