search for: lnet

...manual 1.6 v18 says that that in production lustre debug level should be set to fairly low. Manual also says that I can verify that level by running following commands: # sysctl portals.debug This gives ne following error error: ''portals.debug'' is an unknown key cat /proc/sys/lnet/debug gives output: ioctl neterror warning error emerg ha config console cat /proc/sys/lnet/subsystem_debug undefined mdc mds osc ost class log llite rpc lnet lnd pinger filter echo ldlm lov lmv sec gss mgc mgs fid fld manual says that in order to set reasonable production debug level one nee...

...e 1.8.3 + ofed 1.4.2 right, because it allows me to see and use the infiniband 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...

...  SOURCE lustre-mdt1/mdt1  lustre:svname  fs0:MDT0001    local So far, so good. My /etc/ldev.conf: mds1 mds2 MGS zfs:lustre-mgs/mgs mds1 mds2 fs0-MDT0000 zfs:lustre-mdt0/mdt0 mds2 mds1 fs0-MDT0001 zfs:lustre-mdt1/mdt1 my /etc/modprobe.d/lustre.conf # options lnet networks=tcp0(em1) options lnet ip2nets="tcp0 10.0.0.[22,23]; tcp0 10.0.0.*;" ----------------------------------------------------------------------------- Now, when starting the services, I get strange errors: # service lustre start local Mounting lustre-mgs/mgs on /...

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) , it works when I go for the second (eth0) it does not. # lctl ping 192.168.135.81 at tcp<mailto:192.168.135.81 at tcp> 12345-0 at lo<mailto:12345-0 at...

Hello, Not sure if this is the right forum: I''m encountering difficulties with o2ib which prevents an LNET shutdown from proceeding: Unloading OpenIB kernel modules:NET: Unregistered protocal family 27 Failed to unload rdma_cm Failed to unload rdma_cm Failed to unload ib_cm Failed to unload ib_sa LustreError: 131-3: Received notification of device removal Please shutdown LNET to allow this to pr...

...properly. 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

...nt allow_access_nugid(const char *const nid, const uid_t uid, const gid_t gid) which tells whether access for a certain nid, uid and gid is granted. I did some "integration experiments" after studying the Lustre 2.3 code and tracing the function calls with lctl debug_daemon and sysctl -w lnet.debug=+trace sysctl -w lnet.debug=+info sysctl -w lnet.debug=+inode sysctl -w lnet.debug=+super sysctl -w lnet.debug=+ext2 .... and integrated the function allow_access_nugid(...) in lustre/mdt/mdt_lib.c inside static int old_init_ucred(struct mdt_thread_info *info, stru...

Hello, I use Julian Anastasov ''routes'' (to be more specific: static_routes, alt_routes and nf_reroute) patches on a 2.4.32 kernel. On the same host I run IPSec. I have discovered after a few hours of networking problems that, when IPSec is enabled on that patched kernel, inspecting packets with tcpdump while arping-ing a host from a network physically connected to this

...re-discuss <lustre-discuss at lists.lustre.org> Sent: Fri Mar 07 12:03:17 2008 Subject: Re: [Lustre-discuss] Multihomed question: want Lustre over IB andEthernet On Fri, Mar 7, 2008 at 9:39 AM, Craig Prescott <prescott at hpc.ufl.edu> wrote: > > I think your client modprobe.conf lnet option > should be this: > > > options lnet networks=o2ib(ib0) > > (not ''o2ib0''). It still seems to want the TCP connection: Lustre: Added LNI 36.122.255.1 at o2ib [8/64] Lustre: Lustre Client File System; info at clusterfs.com LustreError: 11043:0:(events.c...

Hello All, I have installed and configured Lustre 1.8.4 on SuSe 11.0 and everything works fine if i run modprobe lustre and when the lustre module is getting loaded. But when the server reboots it is not getting loaded. Kindly help. Lnet is configured in /etc/modprobe.conf.local as below. options lnet networks=tcp0(eth0) accept=all For loading lustre module i tried including lustre module in the variable MODULES_LOADED_ON_BOOT using yast2 sysconfig . But still it is not getting loaded. Error from dmesg is as below. LustreError:...

Hi, I would like to know what TCP/UDP ports should i keep open in my firewall policies on my MGS server such that I can have my MGS server fire-walled. Also if in a event of loss of MGT would it be possible to recreate the MGT without loosing data or bringing the filesystem down (i.e. by using cached information from MDT''s and OST''s) Thanks Anand

...ke the resource from each other, they haven''t seen the other side, if I saw well. I stopped heartbeat, resources, start it again, and back to online, worked fine. This morning I saw this in logs: Feb 22 03:25:07 node4 kernel: Lustre: 7:0:(linux-debug.c:98:libcfs_run_upcall()) Invoked LNET upcall /usr/lib/lustre/lnet_upcall ROUTER_NOTIFY,192.168.0.139@ tcp,down,1203647043 Feb 22 03:25:16 node4 kernel: Lustre: 7:0:(linux-debug.c:98:libcfs_run_upcall()) Invoked LNET upcall /usr/lib/lustre/lnet_upcall ROUTER_NOTIFY,192.168.0.15 at t cp,down,1203647045 Feb 22 03:25:17 node4 kernel: Lu...

...> [ 168.648006] IP: [<ffffffff8002c3d2>] task_rq_lock+0x42/0xa0 > [ 168.648018] PGD 7fac4067 PUD 7ef4c067 PMD 0 > [ 168.648023] Oops: 0000 [#1] SMP > [ 168.648026] last sysfs file: /sys/module/ip_tables/initstate > [ 168.648028] CPU 0 > [ 168.648030] Modules linked in: lnet(N+) lvfs(N) libcfs(N) iptable_nat nf_nat xt_tcpudp xt_pkttype ipt_LOG xt_limit autofs4 binfmt_misc microcode xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6_tables x_tables fuse loop dm_mod joydev rtc_core...

Guys, For those of you not party to the original email exchange, this is about how we can aggregate bandwidth across both rails of a dual-rail IB cluster using current lustre/LNET (i.e. before we have implemented transparant LNET support for failover and bandwidth aggregation across multiple networks). The following 2 points are fundamental - everything below is a direct consequence... 1. LNET is perfectly happy with multiple rails, but it doesn''t load balance...

Hello I''ve noticed that Lustre network error, especially LND errors, are considered as maskable errors. That means that on a production node, where debug mask is 0, those specific errors won''t be displayed if they happened. Does that mean that they are harmless? Do upper-layers resend their RPC/packet if LNDs report an error? When, in my case, o2iblnd says something like

Hello I''ve noticed that Lustre network error, especially LND errors, are considered as maskable errors. That means that on a production node, where debug mask is 0, those specific errors won''t be displayed if they happened. Does that mean that they are harmless? Do upper-layers resend their RPC/packet if LNDs report an error? When, in my case, o2iblnd says something like

...kernel 4. install the remaining rpms 5. download ofed from mellanox "MLNX_OFED_LINUX-1.5.3-3.1.0-rhel6.3-x86_64.iso" * build mellanox ofed bits using the lustre kernel and kernel-devel info * install mellanox ofed 6. reboot 7. upon reboot, if I do NOT have o2ib3 in my lnet networks parameters, I can modprobe lnet and lustre. 8. if I DO have o2ib3 present in the lnet parameters, running modprobe lustre gets me: ib/modules/2.6.32-279.14.1.el6_lustre.x86_64/updates/kernel/fs/lustre/fld.ko): Input/output error WARNING: Error inserting fid (/lib/modules/2.6.32-279.14.1...

...do ésta es numérica. Simplemente eliminando esa segunda fila, las columnas acaban teniendo la clase que deben.. #-------------------------------- Lectura del fichero de entrada sin corregir ----- > head(datIn) TIMESTAMP RECORD batt_volt WinVel WinDir Taire Haire BP_hPA cgr3_T_C cgr3_T_K Lnet long_up_corr CMP3 1 TS RN volts mV mV c % hPA deg_C NA NA W/m^2 W/m^2 2 2016-03-22 0.00 14.13 0.00 240.90 8.67 14.76 687.43 9.83 282.98 -141.02 222.56 767.82 3 2016-03-22 1.00 14.12 3.98 224.30 8.57 16.38 642.69...

.../src/openib/include /usr/local/ofed/src/openib/drivers/infiniband > > I untarred lustre 1.5.95, compiled it (./configure > --with-o2ib=/usr/local/ofed/src/openib) . did a make install, depmod -a > and still get the following: > > my modprobe.conf is the following > > options lnet ip2nets="o2ib0 161.74.83.[0-255]" > > lctl network up > LNET configure error 100: Network is down > > ko2iblnd: disagrees about version of symbol ib_create_cq > ko2iblnd: Unknown symbol ib_create_cq > ko2iblnd: disagrees about version of symbol ib_dereg_mr > ko2ibl...

...-compatible /proc/sys/portals symlink due to a conflict with Cray portals /proc debug on XT3. Before upgrading to 1.4.9, please ensure that you change any configuration scripts or /etc/sysctl.conf files that access /proc/sys/portals/* or sysctl portals.* to use the corresponding entry in /proc/sys/lnet or sysctl lnet.*. This change can be made in advance of the upgrade on any system running Lustre 1.4.6 or newer, since /proc/sys/lnet was added in that version. Thank you for your attention to this change. -- The Lustre Team --