-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
We are using a home-grown set of init scripts. There is an lnet init
script to bring up the lnet networking, and a lustre init script to
start lustre services.
We tend to be paranoid about the possibility of double mounting a
multi-homed LUNs, so
Hi,
Lustre stripes in round robin manner. So let say that you have stripe
count set to 2 and stripe size set to 1MB. When you start write 3GB
file from a client to lustre it will send 1MB piece to OST1 and then
1MB piece to OST2 and it will keep doing that until it send 3GB or
until
I'm trying to do noncontiguous writes on a Lustre filesystem using
MPI-ROMIO routines. It is failing in ADIOI_Set_Lock with the message:
File locking failed in ADIOI_Set_lock. If the file system is NFS, you
need to use NFS version 3, ensure that the lockd daemon is running on
all the
I am at a point where my mds can effectively failover upon a hard or
soft reboot. However, the big problem is with getting the OSSs and
clients to mount to a failover MDS. The syntax according to my lustre
manual is something to the effect:
OSS:
mkfs.lustre -ost -fsname=lustrefs
When I shutdown a server running with the o2ib lnd, lnet hangs
indefinitely and the system does not shut down. Here's the error I get -
LustreError: 131-3: Received notification of device removal
Please shutdown LNET to allow this to proceed
It appears as though when the lustre file system is
When you say they can communicate, did you try lctl ping?
On Feb 21, 2008, at 4:57 AM, Tomec Martin wrote:
Isaac Huang napsal(a):
On Wed, Feb 20, 2008 at 11:19:06PM +0100, Tomec Martin wrote:
According to tutorial I started MGS and MDT on first machine (with
IP
192.168.2.55):
On Feb 21, 2008 13:14 -0800, Chadha, Narjit wrote:
The only thing left is to be able to mount
the failover mds configuration on the OSS. The sytax:
mkfs.lustre --ost -fsname=mylustre -mgsnid=lustre0[1-2] /dev/sdb1
I think this is a defect in the manual. It should be --fsname and
Ron,
I'm trying a slightly different strategy. I'm trying to backport the
TLB patch back to a RHEL5 kernel (which would work on SL5 too). If I
get this patch working, I can let you know. This may be easier than
trying to get Lustre running on a 2.6.23 system.
--Shane
-Original
