Hi all,
is it possible to make an OST "listen" or rather communicate via a particular
interface?
In a test sytem, we had OSSes A, B, C.
- C is switched off
- B has two network interfaces, one of them now with the IP previously on C
- `lctl list_nids` on B shows both NIDs
- The MDS can lctl-ping both NIDs on B
- The OSTs of C have been recreated on B ("mkfs.lustre --replace ...")
- Mounting the OSTs works, also the MDS takes notice ("Found index ..., updating
log")
- Setting those OSTs active on the MDS ("lctl set_param -P
osc."#{OST}"-osc-MDT0000.active=1") works ("Modifying parameter...)
However, in `lctl dl`, these OSTs remain "IN" forever. The clients never
connect, and the log of the OSS shows continous reconnections of the MDT.
Presumably, the clients (mounting ones and the client
testfs-MDT0000-mdtlov_UUID) do not really know where to find the missing OSTs.
Any way to convince them to look on that OSS B?
Regards,
Thomas
_______________________________________________
lustre-discuss mailing list
[email protected]
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
