Details
-
Bug
-
Resolution: Fixed
-
Major
-
Lustre 2.4.1
-
None
-
RHEL6 2.6.32-358.18.1.el6.x86_64
Description
A no longer existing OST has been permanently disabled on the MGS using
lctl conf_param vegas-OST0059.osc.active=0
After this, clients hang on df (after lustre is remounted the next time). strace shows it hanging on a statfs call.
Tried with the lustre mount option lazystatfs (undocumented?) which is supposed to work around this issue, but it did not help with lustre 2.4.1, clients still hang on df. This is the standard df, lfs df seems to work OK.
This seems to work. The syntax is
lctl conf_param <fsname>.llite.lazystafs=1
So, is this expected behaviour and setting this option is required on any lustre filesystem with permanently deactivated OSTs? Or is it still a bug? The conf_param option does not seem to be documented.