Hello,
it would be nice that lfs prints out the ACTIVE (in our case) tcp connection.
i.e:
cluster1 ~ # lfs osts -i
OBDS:
0: scia-OST0000_UUID INACTIVE
1: scia-OST0001_UUID INACTIVE
2: scia-OST0002_UUID INACTIVE
3: scia-OST0003_UUID INACTIVE
<snip><snap>
35: scia-OST0023_UUID ACTIVE --> 192.168.16....@tcp
36: scia-OST0024_UUID ACTIVE --> 192.168.16....@tcp
37: scia-OST0025_UUID ACTIVE --> 192.168.16....@tcp
38: scia-OST0026_UUID ACTIVE --> 192.168.16....@tcp
39: scia-OST0027_UUID ACTIVE --> 192.168.16....@tcp
40: scia-OST0028_UUID ACTIVE --> 192.168.16....@tcp
41: scia-OST0029_UUID ACTIVE --> 192.168.16...@tcp
42: scia-OST002a_UUID ACTIVE --> 192.168.16...@tcp
43: scia-OST002b_UUID ACTIVE --> 192.168.16....@tcp
44: scia-OST002c_UUID ACTIVE --> 192.168.16....@tcp
45: scia-OST002d_UUID ACTIVE --> 192.168.16....@tcp
cluster1 ~ # lfs osts
OBDS:
0: scia-OST0000_UUID INACTIVE
1: scia-OST0001_UUID INACTIVE
2: scia-OST0002_UUID INACTIVE
3: scia-OST0003_UUID INACTIVE
<snip><snap>
35: scia-OST0023_UUID ACTIVE
36: scia-OST0024_UUID ACTIVE
37: scia-OST0025_UUID ACTIVE
38: scia-OST0026_UUID ACTIVE
39: scia-OST0027_UUID ACTIVE
40: scia-OST0028_UUID ACTIVE
41: scia-OST0029_UUID ACTIVE
42: scia-OST002a_UUID ACTIVE
43: scia-OST002b_UUID ACTIVE
44: scia-OST002c_UUID ACTIVE
45: scia-OST002d_UUID ACTIVE
I've patched lfs accordingly and if it is of general interest would put it in
bugzilla.
The content of /proc/fs/lustre/../../ost_conn_uuid is read.
So it should work with other connection types as well, but has not been tested.
Regards
Heiko
_______________________________________________
Lustre-discuss mailing list
[email protected]
http://lists.lustre.org/mailman/listinfo/lustre-discuss
