search for: list_nids

...iband fabric, and because ko2iblnd loads without any complaints. In /etc/modprobe.d/lustre (this is a Debian system, hence this subdir of modprobe-configs), I have > options ip2nets="o2ib0 192.168.0.[1-5]" I load lnet and do ''lctl network up'', but then ''lctl list_nids'' will invariably give me only > 192.168.0.1 at tcp no matter how I twist the modprobe-config (ip2nets="o2ib", network="o2ib", network="o2ib(ib0), etc.) This is true as long as I have ib0 configured with the IP 192.168.0.1 Once I unconfigure it, I get, quite exp...

...ain it''ll use IB for LFS on this client? Thanks, Chris > > Cheers, > Craig > > > > > Chris Worley wrote: > > More issues. Now, on the clients. > > > > The MDT/MGS/OST''s are all up and mounted, showing: > > > > # lctl list_nids > > 36.122.255.201 at o2ib > > 36.121.255.201 at tcp > > > > Now, when I go to mount on the IB-based clients, I get: > > > > # mount -t lustre 36.122.255.201 at o2ib:/ddnlfs /lfs > > mount.lustre: mount 36.122.255.201 at o2ib:/ddnlfs at /lfs failed:...

I am running on CentOS 5 distribution without adding any updates from CentOS. I am using the lustre 1.6.4.1 kernel and software. I have two NICs that run though different switches. I have the lustre options in my modprobe.conf to look like this: options lnet networks=tcp0(eth1,eth0) My MGS seems to be only listening on the first interface however. When I try and ping the 1st interface (eth1)

I installed 1 MDS , 2 OSS/OST and 2 Lustre Client. My MDS shows: [code] [root at MDS ~]# lctl list_nids 10.94.214.185 at tcp [root at MDS ~]# [/code] On Lustre Client1: [code] [root at lustreclient1 lustre]# lfs df -h UUID bytes Used Available Use% Mounted on lustre-MDT0000_UUID 4.5G 274.3M 3.9G 6% /mnt/lustre[MDT:0] lustre-OST0000_UUI...

I installed 1 MDS , 2 OSS/OST and 2 Lustre Client. My MDS shows: [code] [root at MDS ~]# lctl list_nids 10.94.214.185 at tcp [root at MDS ~]# [/code] On Lustre Client1: [code] [root at lustreclient1 lustre]# lfs df -h UUID bytes Used Available Use% Mounted on lustre-MDT0000_UUID 4.5G 274.3M 3.9G 6% /mnt/lustre[MDT:0] lustre-OST0000_UUID 5...

...If I go to system2 then my Lustre file system stops because it cannot get to the alias IP number. I did configure the lustre OSTs to use --mgsnode=a.b.c.d (a.b.c.d representing my Pacemaker IP alias). A tunefs.lustre confirms the alias IP number. The alias IP number does not appear in LNET (lctl list_nids), and "lctl ping a.b.c.d" fails. Should this IP alias go into the LNET data base? If yes, how? What steps should I take to generate a successful "lctl ping a.b.c.d"? Thanks for reading! Cheers, megan

Hello, I''ve several problems with quota on our testcluster: When I set the quota for a person to a given value (e.g. the values which are provided in the operations manual), I''m able to write exact the amount which is set with setquota. But when I delete the files(file) I''m not able to use this space again. Here is what I''ve done in detail: lfs checkquota