Hi Eli, I believe that is still the case with lfs_migrate. If otherwise, we'll probably hear soon.
You should be able to disable those OSTs while keeping the file system active - via a command on the MDS(s) as well as the clients. My notes have the command as shown below, but please confirm via the appropriate Lustre manual: lctl set_param osc.<fsname>-<OST00xy>-*.active=0 Brett -- Protect Yourself Against Cybercrime PDS Software Solutions LLC https://www.TrustPDS.com <https://www.trustpds.com/> On Mon, Mar 20, 2017 at 10:43 AM, E.S. Rosenberg <[email protected] > wrote: > In the man page it says the following: > > Because lfs_migrate is not yet closely integrated with the MDS, it > cannot determine whether a file is currently open and/or in-use by other > applications or nodes. That makes it UNSAFE for use on files that might be > modified by other applications, since the migrated file is only a copy of > the current file, and this will result in the old file becoming an > open-unlinked file and any modifications to that file will be lost. > > Is this still the case? > Is there a better way to disable OSTs while keeping the filesystem live? > > Background: > We need to take a OSS enclosure that hosts multiple OSTs offline for > hardware maintenance, I'd like to do this without bringing Lustre as a > whole down. I made sure there is enough space on the other OSTs to house > the contents of the machine going offline and am now about to move things. > > Thanks, > Eli > > _______________________________________________ > 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
