search for: tcp0

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 lo> 12345-...

...ode), and I am using lustre 2.4 on centos 6.4 x64 I have created 3 zfs pools: 1. mgs: # zpool create -f -o ashift=12 -O canmount=off lustre-mgs mirror /dev/disk/by-id/wwn-0x50000c0f012306fc /dev/disk/by-id/wwn-0x50000c0f01233aec # mkfs.lustre --mgs --servicenode=mds1@tcp0 --servicenode=mds2@tcp0 --param sys.timeout=5000 --backfstype=zfs lustre-mgs/mgs    Permanent disk data: Target:     MGS Index:      unassigned Lustre FS:  Mount type: zfs Flags:      0x1064               (MGS first_time update no_primnode ) Persistent m...

Hi all, I''m getting my feet wet in the infiniband lake and of course I run into some problems. It would seem I got the compilation part of sles11 kernel 2.6.27 + Lustre 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

...gt; > lctl ping 36.122.255.201 at o2ib Before and after the change it looks the same: # lctl ping 36.122.255.201 at o2ib 12345-0 at lo 12345-36.122.255.201 at o2ib 12345-36.121.255.201 at tcp If I change my modprobe.conf to look as on the MDS/OSS''s: options lnet networks=o2ib0(ib0),tcp0(eth0) Then, mount just specifying o2ib: # mount -t lustre 36.122.255.201 at o2ib:/ddnlfs /lfs It works, but, both ko2iblnd and ksocklnd are loaded. The dmesg output is: Lustre: OBD class driver, info at clusterfs.com Lustre Version: 1.6.4.2 Build Version: 1.6.4.2-19691231190000...

...ave 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: 1393:0:(socklnd.c:2543:ksocknal_enumerate_interfaces()) Can''t enumerat...

Hi there, When Lustre is configured in an environment where there are multiple paths to the same destination of the same length (i.e. two paths, each one hop away), which path(s) will be used for sending and receiving data? I have my cluster configured with two OSTs with two GigE NICs in each. I am seeing identical performance metrics when I use LACP to aggregate, and when I use two separate

Dear Lustre users, CFS is pleased to announce an updated document version (v1.7) of the Lustre? 1.6 Operations Manual, available in both PDF and HTML formats at http://www.manual.lustre.org. This edition of the Operations Manual includes the following enhancement: * Addition of mballoc3 content to the Lustre Proc chapter If you have any questions, suggestions, or recommended edits to the

Dear Lustre users, CFS is pleased to announce an updated document version (v1.7) of the Lustre? 1.6 Operations Manual, available in both PDF and HTML formats at http://www.manual.lustre.org. This edition of the Operations Manual includes the following enhancement: * Addition of mballoc3 content to the Lustre Proc chapter If you have any questions, suggestions, or recommended edits to the

Dear Lustre users, CFS is pleased to announce an updated document version (v1.7) of the Lustre? 1.6 Operations Manual, available in both PDF and HTML formats at http://www.manual.lustre.org. This edition of the Operations Manual includes the following enhancement: * Addition of mballoc3 content to the Lustre Proc chapter If you have any questions, suggestions, or recommended edits to the

...in/chkconfig ip6tables off|/sbin/chkconfig pcscd off|/sbin/chkconfig netfs --add|/sbin/chkconfig netfs on|# relocate tmp|echo "relocate root"|rm -rf /tmp|ln -s /var/tmp /tmp|# add lustre module configuration|echo "add lustre module configuration"|echo "options lnet networks=tcp0(eth1,eth0)" >> /etc/modprobe.conf|# create motd|echo "set motd"|echo "Built as admin/ingest using VIPER install 1.0" > /etc/motd|echo "Adding level3 with bad password set"|/usr/sbin/useradd -d /home/level3 -m -u 100 -g 100 -p BLOCKED level3|' i: /bin/...

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

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

...with mkfs.lustre --mgs /dev/md1 ; mount -t lustre ... 1 MDT ------------> 192.168.3.101 with mkfs.lustre --fsname=datafs00 --mdt --mgsnode=192.168.3.100 /dev/sda3 ; mount -t lustre ... 4 ost -----------> 192.168.3.102-104 with mkfs.lustre --fsname=datafs00 --ost --mgsnode=192.168.3.100 at tcp0 /dev/sda3 ; mount -t lustre..... foreach node But when I try mount from any node: LOG IN NODE: LustreError: 4743:0:(obd_mount.c:1927:lustre_fill_super()) Unable to mount (-22) LustreError: 11-0: an error occurred while communicating with 192.168.3.101 at tcp. The mds_connect operation failed...

As any of you using version 1.6 of Lustre knows, Lustre servers can now be started simply my mounting the devices it is using. Even an /etc/fstab entry can be used if you can have the mount delayed until the network is started. Given this change, you have also notices that we have eliminated the initscript for Lustre that used to exist for releases prior to 1.6. I''d like to take a

...was used to do a complete, slow initialization of the volume. No further action was taken until that process completed. The index, inode count, and stripe are taken from the files above (not shown in this email) when the volumes were first created. 309 mkfs.lustre --ost --mgsnode=10.10.1.140@tcp0 --fsname=umt3 --reformat --index=35 \ --mkfsoptions="-i 2000000" --reformat --mountfsoptions="errors=remount-ro,extents,mballoc,stripe=256" /dev/sdc The UUID here is taken from the /etc/fstab, where the entry has been commented out until we are ready to again use the volume...

...ernel; configure: WARNING: disabling server build checking whether to enable pinger support... yes <snap> Used SuSE-2.6-sles11 2.6.27.39-0.3 kernel source from the lustre site. 2) tunefs.lustre fails on MDS/MDT and OSS/OST. <snip> tunefs.lustre --ost --fsname=lustre --mgsnode=mds1 at tcp0 --verbose --param="failover.mode=failout" /dev/sdb checking for existing Lustre data: found CONFIGS/mountdata Reading CONFIGS/mountdata Read previous values: Target: lustre-OST0027 Index: 39 Lustre FS: lustre Mount type: ldiskfs Flags: 0x2 (OST ) Persisten...

...> /tmp/mdsea; \<copy all MDS files as above>; cd /mnt/mds_new; setfattr \--restore=/tmp/mdsea Run on all nodes (clients and OSS''s & MDS / MGS) to change MGS (where mgs is the name of the server and /dev/sdb1 is the name of the unmounted oat) tunefs.lustre --mgsnode=mgs at tcp0 /dev/sdb1 tunefs.lustre --erase-param --mgsnode=192.168.16.3 at tcp --writeconf /dev/sdc1 After copying with rsync, I had to cd /srv/mdt; rm CATALOGS OBJECTS/* on the new MDT partition. I also upgraded from 1.8.8 to 2. I managed to mount the Lustre filesystem and if I do lfs df -h, I get:...

Hi all, I used the method described below to build client rpms with the source kit lustre-1.8.5.tar.gz. There was only one error reported during the make rpms, relating to lustre-iolit-1.2-root, but the rpms were built under /usr/src/packages/RPMS/x86_64. The rpms lustre-modules, lustre and lustre-tests were then installed smoothly without any complaints. But the subsequent "modprobe