Re: [lustre-discuss] Adding a servicenode (failnode) to existing OSTs

2018-04-06 Thread Steve Barnet
Hi all, Thanks for the info. Very helpful! Best, ---Steve On 4/4/18 12:07 PM, Mohr Jr, Richard Frank (Rick Mohr) wrote: On Apr 3, 2018, at 1:14 PM, Steve Barnet wrote: There appear to be a couple ways that this could be done: a) Add the service nodes: tunefs.lustre --servicenode=ni

Re: [lustre-discuss] Adding a servicenode (failnode) to existing OSTs

2018-04-04 Thread Mohr Jr, Richard Frank (Rick Mohr)
> On Apr 3, 2018, at 1:14 PM, Steve Barnet wrote: > > There appear to be a > couple ways that this could be done: > > a) Add the service nodes: > tunefs.lustre --servicenode=nid,nid /dev/ > > b) Add a failover node: > tunefs.lustre --param="failover.node= /dev/ The first one is the prefer

Re: [lustre-discuss] Adding a servicenode (failnode) to existing OSTs

2018-04-04 Thread Artem Blagodarenko
Hello, But If writeconf is not possible there is patch that currently is being inspected that adds replace_nids failover nodes support (https://jira.hpdd.intel.com/browse/LU-10384). You are welcome for inspection and testing. Thanks, Artem Blagodarenko. > On 3 Apr 2018, at 20:46, Vicker, Darby

Re: [lustre-discuss] Adding a servicenode (failnode) to existing OSTs

2018-04-03 Thread Vicker, Darby (JSC-EG311)
We have a similar setup and recently had to do something similar - in our case, to add a 2nd IB NID. The admin node says that servicenode is preferred over failnode, so that's what we use. It works great - we love the capability to fail over for maintenance or troubleshooting. Our tunfs.lustr