Re: [lustre-discuss] lfs migrate of hard links
You may be able to just copy the lfs_migrate script from a 2.12.x client, I don't think it has any dependencies on kernel or lfs features in the 2.12 release. I would of course recommend that you test it is working properly on some test hard-linked files before running it on the whole filesystem. On May 27, 2019, at 19:02, Scott Wood wrote: > > Hi folks, > > I am in the process of draining a dozen OSTs in a 2.10.3 environment (all > servers and clients) for replacement and it turns out they have many files > with multiple hard links to them. We can't leave these files behind, as we > need to replace the OSTs, but we can't let them " be split into multiple > separate files" by lfs_migrate as that would break things. > > From my reading of the changelogs and the new lfs_migrate script, it seems > that these are now handled more elegantly. If I were to upgrade the lustre > client to 2.12.1 on a dozen clients, would the new client side lfs_migrate in > 2.12.1 work with 2.10.3 servers, or will I need a system wide outage to > upgrade all clients and servers? > > Cheers! > Scott Cheers, Andreas -- Andreas Dilger Principal Lustre Architect Whamcloud ___ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
[lustre-discuss] lfs migrate of hard links
Hi folks, I am in the process of draining a dozen OSTs in a 2.10.3 environment (all servers and clients) for replacement and it turns out they have many files with multiple hard links to them. We can't leave these files behind, as we need to replace the OSTs, but we can't let them " be split into multiple separate files" by lfs_migrate as that would break things. >From my reading of the changelogs and the new lfs_migrate script, it seems >that these are now handled more elegantly. If I were to upgrade the lustre >client to 2.12.1 on a dozen clients, would the new client side lfs_migrate in >2.12.1 work with 2.10.3 servers, or will I need a system wide outage to >upgrade all clients and servers? Cheers! Scott ___ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
[lustre-discuss] Lustre under autofs
In our Rocks cluster, we added entries to /etc/auto.share to conveniently mount our Lustre file systems on all nodes: lfs01 -fstype=lustre 192.168.230.238@o2ib:/lustrefs lfs02 -fstype=lustre 192.168.230.239@o2ib:/lustrefs On login nodes, the lfs01 or lfs02 mount points would occasionally give "No such file or directory," and attempting to statically mount them while at that state would give "File exists." Rebooting the client node makes the problem go away temporarily. Are we perhaps missing some option in the auto.share entries above to prevent that behavior from reoccurring? Thanks in advance for any pointers. Youssef Eldakar Bibliotheca Alexandrina ___ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
