Lustre discuss - Aug 2010 - mkfs.lustre and failover question

I''ve read through the ''More Complicated
Configurations'' section in the
manual and it says as part of setting up failover with
two(active/passive) MDS/MGS and two OSSs(active/active) to use the
following:

mkfs.lustre --fsname=lustre --ost --failnode=192.168.5.101 at tcp0
--mgsnode=192.168.5.104 at tcp0,192.168.5.105 at tcp0
/dev/lustre-ost1-dg1/lv1

Yet it fails when I try to mount:

kjournald starting.  Commit interval 5 seconds
LDISKFS FS on dm-9, internal journal
LDISKFS-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
LDISKFS FS on dm-9, internal journal
LDISKFS-fs: mounted filesystem with ordered data mode.
LDISKFS-fs: file extents enabled
LDISKFS-fs: mballoc enabled
Lustre: 5984:0:(client.c:1463:ptlrpc_expire_one_request()) @@@ Request
x1343800163193112 sent from MGC192.168.5.104 at tcp to NID
192.168.5.105 at tcp 5s ago has timed out (5s prior to deadline).
  req at ffff810118a53400 x1343800163193112/t0
o250->MGS at MGC192.168.5.104@tcp_0:26/25 lens 368/584 e 0 to 1 dl
1282144240 ref 1 fl Rpc:N/0/0 rc 0/0
LustreError: 4854:0:(obd_mount.c:1095:server_start_targets()) Required
registration failed for lustre-OSTffff: -4
LustreError: 4854:0:(obd_mount.c:1653:server_fill_super()) Unable to
start targets: -4
LustreError: 4854:0:(obd_mount.c:1436:server_put_super()) no obd lustre-OSTffff
LustreError: 4854:0:(obd_mount.c:147:server_deregister_mount())
lustre-OSTffff not registered
LDISKFS-fs: mballoc: 0 blocks 0 reqs (0 success)
LDISKFS-fs: mballoc: 0 extents scanned, 0 goal hits, 0 2^N hits, 0
breaks, 0 lost
LDISKFS-fs: mballoc: 0 generated and it took 0
LDISKFS-fs: mballoc: 0 preallocated, 0 discarded

Reading that makes me think its looking for 192.168.5.105 to be an
active MGS/MDS as well as 192.168.5.104(which is the primary).

David

-- 
Personally, I liked the university. They gave us money and facilities,
we didn''t have to produce anything! You''ve never been out of
college!
You don''t know what it''s like out there! I''ve worked
in the private
sector. They expect results. -Ray Ghostbusters

On Wed, Aug 18, 2010 at 10:16:36AM -0500, David Noriega
wrote:
> I''ve read through the ''More Complicated
Configurations'' section in the
> manual and it says as part of setting up failover with
> two(active/passive) MDS/MGS and two OSSs(active/active) to use the
> following:
> 
> mkfs.lustre --fsname=lustre --ost --failnode=192.168.5.101 at tcp0
> --mgsnode=192.168.5.104 at tcp0,192.168.5.105 at tcp0
> /dev/lustre-ost1-dg1/lv1
A Lustre-MGS can have more than one network address (NID). Different NIDs of
the same server are separated by commas. Here, you want to configure NIDs for
different servers. Those either have to be separated with a colon.
Alternatively, you can just use option --mgsnode twice with different
arguments. In your case, try

mkfs.lustre --fsname=lustre --ost --failnode=192.168.5.101 at tcp0
--mgsnode=192.168.5.104 at tcp0 --mgsnode=192.168.5.105 at tcp0
/dev/lustre-ost1-dg1/lv1

Regards,

Daniel.