On 2010-09-01, at 01:55, Heiko Schröter wrote: > it would be nice that lfs prints out the ACTIVE (in our case) tcp connection. > 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 > > I've patched lfs accordingly and if it is of general interest would put it in > bugzilla.
This looks generally interesting. I recall that I had posted something similar in a thread "On which OSS are the OST?": lctl get_param osc.*.ost_conn_uuid but it makes sense to make this into "lfs osts" (as I'd also suggested in that thread). Submitting the patch to Bugzilla is the first step to getting this landed. Cheers, Andreas -- Andreas Dilger Lustre Technical Lead Oracle Corporation Canada Inc. _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
