Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the
following link:
https://bugzilla.lustre.org/show_bug.cgi?id=11229
What |Removed |Added
----------------------------------------------------------------------------
Attachment #9212 is|0 |1
obsolete| |
Created an attachment (id=9221)
Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the
following link:
--> (https://bugzilla.lustre.org/attachment.cgi?id=9221&action=view)
permanent osc (de)activation, true config param changing
Cancel old parameter settings in config logs, instead of just overwriting old
settings. This allows the permanent deactivation and subsequent (permanent)
reactivation of an osc without the toggling of the active state during
subsequent client startups (when the entire config log is parsed). It also
adds
the .../osc/active writable proc file to change/view the active setting.
Permanent removal of an OST is now accomplished with e.g.:
lctl conf_param lustre-OST0001.osc.active=0
which both sets the appropriate OSC's inactive on all clients (and MDT), and
changes the config logs so that newly-starting clients will start with the osc
in the inactive state. If the OST is fixed at some point in the future,
re-enable with active=1.
_______________________________________________
Lustre-devel mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-devel
