[Lustre-discuss] Luster access locking up login nodes

[Brock Palen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ahh didn't realize this was related to that.  Good to know fix in the  
works  (2 x4500's on the way so we have made a commitment to lustre).

How would I make this option the default on boot?  There isn't an  
llite module I see on the clients.
I can pdsh to all the clients, but machines to get rebooted some times.

Brock Palen
www.umich.edu/~brockp
Center for Advanced Computing
brockp at umich.edu
(734)936-1985



On May 16, 2008, at 4:13 PM, Brian J. Murrell wrote:
> On Fri, 2008-05-16 at 15:48 -0400, Brock Palen wrote:
>> I have seen this behavior a few times.
>> Under heavy IO lustre will just stop and dmesg will have the  
>> following:
>
> Review the list archives for statahead problems.
>
> b.
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFILe2TMFCQB4Bvz5QRAvuRAKCG94UfDQvSxcBXCPSxThLuirrGbACfUsTm
hobLA1aA+AHrZd4mwkY5sKQ=
=3Gzv
-----END PGP SIGNATURE-----