Is there a way to backup the configuration information on the target
disk before changing the MGS NID (ie. adding second multi-homed network) ?
These config logs are created when the filesystem is created (ie.
mkfs.lustre) and not regenerated each time lustre is mounted ?
To add the second netw
On Jan 09, 2009 18:31 -0500, Chris Hunter wrote:
> Andreas Dilger wrote:
>> On Jan 07, 2009 18:16 -0500, Chris Hunter wrote:
>>> We currently use lustre over an infiniband network. We would like to
>>> allow ethernet clients (ie. no infiniband) to use the same lustre FS.
>>>
>>> The MDT and OST
Andreas Dilger wrote:
> On Jan 07, 2009 18:16 -0500, Chris Hunter wrote:
>> We currently use lustre over an infiniband network. We would like to
>> allow ethernet clients (ie. no infiniband) to use the same lustre FS.
>>
>> The MDT and OSTs were all created using only the MGS infiniband
>> int
On Jan 07, 2009 18:16 -0500, Chris Hunter wrote:
> We currently use lustre over an infiniband network. We would like to
> allow ethernet clients (ie. no infiniband) to use the same lustre FS.
>
> The MDT and OSTs were all created using only the MGS infiniband
> interface (ie. mkfs.lustre --mgs
We currently use lustre over an infiniband network. We would like to
allow ethernet clients (ie. no infiniband) to use the same lustre FS.
The MDT and OSTs were all created using only the MGS infiniband
interface (ie. mkfs.lustre --mgsnode=10.2.1...@ib0).
We have modified the OSTs and MDS to
