[edit] WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Talk:Handling Full OSTs

From Obsolete Lustre Wiki
Jump to: navigation, search

Please use this page to provide feedback about lustre.org content (errors to fix, new content needed, or existing content that needs updating). Log in and click the + tab above to add your comment.
If you have a technical question or encounter a problem with Lustre, please post to the lustre-discuss mailing list (see Lustre Mailing Lists) or file a bug (see Reporting Bugs).

lctl deactivate does not make the OST read-only

The page says the OST is "rendered read-only using the lctl command" (deactivate). This is misleading -- files existing on the OST can still be opened and written to. Deactivation of the OST on the MDS only prevents new files from going there. Specifically, when using lfs_migrate to handle full OSTs, more care than noted here has to be taken in order to quiesce writes to the OST.

Personal tools