similar to: Change to Lustre /proc symlink

Hi, Lustre 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

Chris, Perhaps you need to perform some write_conf like command. I''m not sure if this is needed in 1.6 or not. Shane ----- Original Message ----- From: lustre-discuss-bounces at lists.lustre.org <lustre-discuss-bounces at lists.lustre.org> To: lustre-discuss <lustre-discuss at lists.lustre.org> Sent: Fri Mar 07 12:03:17 2008 Subject: Re: [Lustre-discuss] Multihomed

Hi all, Here is the situation: I have 2 nodes MDS1 , MDS2 (10.0.0.22 , 10.0.0.23) I wish to use as failover MGS, active/active MDT with zfs. I have a jbod shelf with 12 disks, seen by both nodes as das (the shelf has 2 sas ports, connected to a sas hba on each node), and I am using lustre 2.4 on centos 6.4 x64 I have created 3 zfs pools: 1. mgs: # zpool

It seems that lustre puts its modules in /lib/modules/2.6.16.21-0.8-default despite the fact that my kernel is 2.6.16.21-0.8-smp ! uname -a Linux n32 2.6.16.21-0.8-smp #4 SMP Sun Sep 24 08:47:30 BST 2006 i686 i686 i386 GNU/Linux make[3]: Nothing to be done for `install-exec-am''. /bin/sh ../../mkinstalldirs /lib/modules/2.6.16.21-0.8-default/kernel/fs/lustre /usr/bin/install -c -m 644

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

Dear All, Yesterday evening or cluster has stopped. Two of our nodes tried to take 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

Hello list members, I started to develop a kernel module which hooks into Lustre 2.3 for controlling data access based on nid and uid/gid. The background is the following: Here at GSI we have currently a reserved uid/gid space which partner institutes are using to access our exported Lustre mounts. However, we currently have no mechanism to control (guaranty) that the reserved uid/gid space are

Hello, I am having trouble installing the server modules for lustre 2.1.4 and use mellanox''s OFED distribution so we may use infiniband. Would you folks look at my procedure and results below and let me know what you think? Thanks very much! The mellanox ofed installation builds and installs some kernel modules too, so I used this method to ensure OFED compiled against the correct

Hello CFS, I was wondering if the new SLES10 kernel will be part of the 1.6.4 release. It appears to be tracked by: https://bugzilla.lustre.org/show_bug.cgi?id=13874 As this contains a major security fix (privilege escalation), it is a mandatory upgrade in many places and it would be nice to not have to roll our own kernel. Thanks, Kit

I am trying to compile lustre like this : [onkar at localhost build-lustre]$ ./configure --with-kernel-source-header=/home/onkar/LUSTRE/linux-2.6.33.3/include --with-linux=/home/onkar/LUSTRE/linux-2.6.33.3 --with-linux-obj=/home/onkar/LUSTRE/linux-2.6.33.3 --with-linux-config=/home/onkar/LUSTRE/linux-2.6.33.3 checking build system type... i686-pc-linux-gnu checking host system type...

I am trying to compile lustre like this : [onkar at localhost build-lustre]$ ./configure --with-kernel-source-header=/home/onkar/LUSTRE/linux-2.6.33.3/include --with-linux=/home/onkar/LUSTRE/linux-2.6.33.3 --with-linux-obj=/home/onkar/LUSTRE/linux-2.6.33.3 --with-linux-config=/home/onkar/LUSTRE/linux-2.6.33.3 checking build system type... i686-pc-linux-gnu checking host system type...

Hi Guys, I had a situation yesterday where I had a 10Gbe adapter on my lustre client configured but not active (the cable was plugged in and had link but the port was down) and this actually brought down our cisco switch. This is a new port that I am setting up. The reason why the switch went down was due to the amount of broadcast traffic coming from this port even though it was shutdown:

Hello, We had a problem with our disk controller that required a reboot. 2 of our OSTs remounted and went through the recovery window but clients hang trying to access them. Also /proc/fs/lustre/obdfilter/$UUID/ is empty for that OST UUID. LDISKFS FS on dm-5, internal journal on dm-5:8 LDISKFS-fs: delayed allocation enabled LDISKFS-fs: file extents enabled LDISKFS-fs: mballoc enabled

Lustre 1.2.2 has been released! Lustre 1.2.2 contains a significant number of fixes over Lustre 1.2.1 and is a recommended update for anyone running earlier Lustre versions. The most user-visible among them are: - Allow users to set per-directory default striping values - Fix data coherency bugs with concurrent write/truncate - The blocks count is updated on clients for stat without revoking

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

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

Hi, We have seen a huge performance drop in 1.6.3, due to the checksum being enabled by default. I looked at the algorithm being used, and it is actually a CRC32, which is a very strong algorithm for detecting all sorts of problems, such as single bit errors, swapped bytes, and missing bytes. I''ve been experimenting with using a simple XOR algorithm. I''ve been able to recover

NOTE: BETA SOFTWARE, NOT FOR PRODUCTION USE Cluster File Systems is pleased to announce the next beta version of Lustre 1.6, which includes the following new features: * Dynamic service threads - within a small range, extra service threads are started automatically when the request queue builds up. * Mixed-endian environment fixes * Easy permanent OST removal * MGS failover * MGS proc