Hi Brad, Looks like you're suffering from an old bug, you'll need to tuners.lustre the MDT target, capture the current params and then --erase-params, --param mdd.quota_type=ug and anything else (other than mdt.quota_type=ug) and --writeconf
And because of other behavioral issues around --writeconf, you'll need to --writeconf (only) all of the OSS targets And because of behavioural issues with initial mounting of lustre you'll want to mount in the specific order of: mgs / MDT, OSS(s) and then clients. Cheers and good luck. On Fri, Apr 2, 2021, 5:56 PM Brad Merchant <[email protected]> wrote: > We have an old IEEL 3.0 system (Lustre ver 2.7.15.3) that we enabled user > and group quotas on several months ago. Today we rebooted the MDS node for > the first time since then and the MDT refuses to mount with > > > [Fri Apr 2 18:36:33 2021] LDISKFS-fs (dm-1): mounted filesystem with > ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache > [Fri Apr 2 18:36:33 2021] LustreError: > 35031:0:(obd_config.c:1345:class_process_proc_param()) mdt: vipbgfs-MDT0000 > unknown param quota=ug > [Fri Apr 2 18:36:33 2021] LustreError: > 35031:0:(obd_config.c:1624:class_config_llog_handler()) MGC10.0.0.101@o2ib: > cfg command failed: rc = -38 > [Fri Apr 2 18:36:33 2021] Lustre: cmd=cf00f 0:vipbgfs-MDT0000 > 1:mdt.quota=ug > > [Fri Apr 2 18:36:33 2021] LustreError: 15c-8: MGC10.0.0.101@o2ib: The > configuration from log 'vipbgfs-MDT0000' failed (-38). This may be the > result of communication errors between this node and the MGS, a bad > configuration, or other errors. See the syslog for more information. > [Fri Apr 2 18:36:33 2021] LustreError: > 34940:0:(obd_mount_server.c:1305:server_start_targets()) failed to start > server vipbgfs-MDT0000: -38 > [Fri Apr 2 18:36:33 2021] LustreError: > 34940:0:(obd_mount_server.c:1792:server_fill_super()) Unable to start > targets: -38 > [Fri Apr 2 18:36:33 2021] Lustre: Failing over vipbgfs-MDT0000 > [Fri Apr 2 18:36:33 2021] Lustre: server umount vipbgfs-MDT0000 complete > [Fri Apr 2 18:36:33 2021] LustreError: > 34940:0:(obd_mount.c:1342:lustre_fill_super()) Unable to mount (-38) > > > Is there a way to disable quota param to get the MDT to mount? Or any > other way to get the MDT to mount? > > If it matters the node is currently running e2fsprogs ver 1.42.13.wc4-7 > (all targets are ldiskfs) > > > Thanks, > Brad Merchant > HPC Technologist > Cambridge Computer > _______________________________________________ > lustre-discuss mailing list > [email protected] > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org >
_______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
