search for: lctl

...m default value 250s to something longer I tried example from manual: set_timeout <secs> Sets the timeout (obd_timeout) for a server to wait before failing recovery. We performed that experiment on our test lustre installation with one OST. storage02 is our OSS [root at storage02 ~]# lctl dl 0 UP mgc MGC10.143.245.3 at tcp 31259d9b-e655-cdc4-c760-45d3df426d86 5 1 UP ost OSS OSS_uuid 3 2 UP obdfilter home-md-OST0001 home-md-OST0001_UUID 7 [root at storage02 ~]# lctl --device 2 set_timeout 600 set_timeout has been deprecated. Use conf_param instead. e.g. conf_param lustre-MDT...

...ard defaults over TCP/IP. Everything worked very nicely usnig a real, static --mgsnode=a.b.c.x value which was the actual IP of the MGS/MDS system1 node. I am now trying to integrate it with Pacemaker-1.1.7. I believe I have most of the set-up completed with a particular exception. The "lctl ping" command cannot ping the pacemaker IP alias (say a.b.c.d). The generic ping command in RHEL 6.2 can successfully access the interface. The Pacemaker alias IP (for failover of the combnied MGSMDS node with Fibre Channel multipath storage shared between both MGS/MDS-configured machines) w...

Hello, lfs prints different obd(idx) compared to lctl dl. We use single striping. cluster1 tmp # lfs find --obd scia-OST0017_UUID /data/scia/L0/V0.00/20100327/SCI_NL__0PNPDE20100327_193441_000040582088_00071_42209_1158.N1 /data/scia/L0/V0.00/20100327/SCI_NL__0PNPDE20100327_193441_000040582088_00071_42209_1158.N1 cluster1 tmp # lfs getstripe /data/s...

Hi; One of our OSTs filled up. Once we realized this, we executed lctl --device 9 deactivate on our fs''s combo MDS/MGS machine. We saw in the syslog that the OST in question was deactivated: Lustre: setting import ufhpc-OST0008_UUID INACTIVE by administrator request However, ''lfs df'' on the clients does not show that the OST is deactivat...

...gh 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-192.168.135.81 at tcp<mailto:12345-192.168.135.81 at tcp> # lctl ping 192.168.135.80 at tcp<mailto:192.168.135.80 at tcp> failed to ping 192.168.135.80 at tcp<mailto:192.168...

...ight, 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 ib0 configured with th...

Hi I want my lustre do such things during OST failed: if some file has stripe data on th failed OST, any operation on the file will return IO error without blocking, and also at this moment I can create and read/write new file or read/write files which have no stripe data on the failed OST without blocking. What should I do ? How to configure? thanks! swin -------------- next part

...r()) Unable to process log: -2 LustreError: 11043:0:(obd_config.c:392:class_cleanup()) Device 2 not setup Lustre: client 0000010430934400 umount complete LustreError: 11043:0:(obd_mount.c:1924:lustre_fill_super()) Unable to mount (-2) > > Another thing to try, if that doesn''t work lctl > ping your MDS/MGS/OSS nids, like so: > > 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...

Hi, We run four-node Lustre 2.3, and I needed to both change hardware under MGS/MDS and reassign an OSS ip. Just the same, I added a brand new 10GE network to the system, which was the reason for MDS hardware change. I ran tunefs.lustre --writeconf as per chapter 14.4 in Lustre Manual, and everything mounts fine. Log regeneration apparently works, since it seems to do something, but

...ta again. 1-2 mins later, they would lock up again. The oss''s were dumping stacks all over the place, crawling along and generally making our lustrefs unuseable. After trying different kernels, raid card drivers, changing write back policy on the raid cards etc. the solution was to lctl set_param obdfilter.*.writethrough_cache_enable=0 lctl set_param obdfilter.*.read_cache_enable=0 on all the nodes with the 3ware cards. Has anyone else seen this? I am completely baffled as to why it only affects our nodes with 3ware cards. These nodes were working very well under 1.8.3......

All, I''ve added a new 2.2 TB OST to my cluster easily enough, but this new disk array is meant to replace several smaller OSTs that I used to have of which were only 120 GB, 500 GB, and 700 GB. Adding an OST is easy, but how do I REMOVE the small OSTs that I no longer want to be part of my cluster? Is there a command to tell luster to move all the file stripes off one of the nodes?

...journals enabled. Question is whether the procedure: umount <filesystem> on all clients umount <osts> on all OSSes e2fsck <ost-device> on all OSSes for all all OSTs tune2fs -O ^has_journal <ost-device> on all OSSes for all all OSTs lctl set_param obdfilter.*.sync_journal=0 on all OSSes mount <osts> on all OSSes mount <filesystem> on all clients is correct to do the job? (I hope it isn''t neccessary to recreate a FS from scratch.) Many thanks in advance. Cheers -Frank Heckes...

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

...earlier 1.6-versions did). However, we had this weird incident where an active client (it was copying 4GB files and running ls at the time) got evicted by the MDS and all OST''s. After a while logs indicate that it did recover the connection to the MDT, but not the OST''s ... lctl ping between the client and mds/oss''s still worked. After a while I got tired of waiting for it to recover and did umount -f, which also hung. So, what should happen in situations like this? What can I do to debug it? Has anyone else seen this? 130.239.78.238 is the client, 130.239.78....

on our cluster that has been running lustre for about 1 month. I have 1 MDT/MGS and 1 OSS with 2 OST''s. Our cluster uses all Gige and has about 608 nodes 1854 cores. We have allot of jobs that die, and/or go into high IO wait, strace shows processes stuck in fstat(). The big problem is (i think) I would like some feedback on it that of these 608 nodes 209 of them have in dmesg

Some clients have been removed several weeks ago but are still listed in: ls -l /proc/fs/lustre/obdfilter/*/exports/ This was found after tracing back mystery tcp packets to the OSS. Although this is causing no damage, it raises the question of when former clients will be cleared from the OSS. Is there a way to manually remove these exports from the OSS? -- Regards, David

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

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

...module exports the function: int 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...

...ng lustre-mgs/mgs on /mnt/lustre/local/MGS Mounting lustre-mdt0/mdt0 on /mnt/lustre/local/fs0-MDT0000 mount.lustre: mount lustre-mdt0/mdt0 at /mnt/lustre/local/fs0-MDT0000 failed: Input/output error Is the MGS running? # service lustre status local running attached lctl-dk.local01 If I run the same command again, I get a different error: # service lustre start local Mounting lustre-mgs/mgs on /mnt/lustre/local/MGS mount.lustre: according to /etc/mtab lustre-mgs/mgs is already mounted on /mnt/lustre/local/MGS Mounting lustre-mdt0/mdt0 o...