[Lustre-discuss] obdidx mapping

Jack David jd6589 at gmail.com
Tue Feb 7 22:12:46 PST 2012


On Wed, Feb 8, 2012 at 9:57 AM, Carlos Thomaz <cthomaz at ddn.com> wrote:
> Hi Jack,
>
> I guess this is what you are looking for:
>
>
> 4.3.15 Determining Which Machine is Serving an OSTIn the course of
> administering a Lustre file system, you may need to determine which
> machine is serving a specific OST. It is not as simple as identifying the
> machine¹s IP address, as IP is only one of several networking protocols
> that Lustre uses and, as such, LNET does not use IP addresses as node
> identifiers, but NIDs instead.
> To identify the NID that is serving a specific OST, run one of the
> following commands on a client (you do not need to be a root user):
> client$ lctl get_param osc.${fsname}-${OSTname}*.ost_conn_uuid
> For example:
> client$ lctl get_param osc.*-OST0000*.ost_conn_uuid
> osc.myth-OST0000-osc-f1579000.ost_conn_uuid=192.168.20.1 at tcp
> - OR -
> client$ lctl get_param osc.*.ost_conn_uuid
> osc.myth-OST0000-osc-f1579000.ost_conn_uuid=192.168.20.1 at tcp
> osc.myth-OST0001-osc-f1579000.ost_conn_uuid=192.168.20.1 at tcp
> osc.myth-OST0002-osc-f1579000.ost_conn_uuid=192.168.20.1 at tcp
> osc.myth-OST0003-osc-f1579000.ost_conn_uuid=192.168.20.1 at tcp
> osc.myth-OST0004-osc-f1579000.ost_conn_uuid=192.168.20.1 at tcp
>

Thanks Carlos,
That did the trick. It is reading the info from.
/proc/fs/lustre/osc/*/ost_conn_uuid

Thanks,
J

> Regards,
> Carlos
>
>
>
>
>
> --
> Carlos Thomaz | HPC Systems Architect
> Mobile: +1 (303) 519-0578
> cthomaz at ddn.com | Skype ID: carlosthomaz
> DataDirect Networks, Inc.
> 9960 Federal Dr., Ste 100 Colorado Springs, CO 80921
> ddn.com <http://www.ddn.com/> | Twitter: @ddn_limitless
> <http://twitter.com/ddn_limitless> | 1.800.TERABYTE
>
>
>
>
>
> On 2/7/12 6:37 AM, "Jack David" <jd6589 at gmail.com> wrote:
>
>>lmm_stripe_pattern: 1
>>
>



-- 
J



More information about the lustre-discuss mailing list