On Fri, 2009-11-20 at 09:31 +0100, Heiko Schröter wrote: > Hello, Hi,
> A user can stall the lustre mount by not using a FQN Filename. > Example file: /lustre_automount/myfile.dat This sounds very strange and does not represent what I would think is correct behaviour. > > When lustre is *NOT* mounted a user can stall the client mount with 'ls > /lustre_automount/myfile' (no asterik after myfile !) IOW, an invalid filename? > for at minimum 100s. > Error messages as in 2) will popup with the 'lnet_try_match_md()' sequence. Hrm. That seems very strange, given that automount should be using the same mount command in both instances. > lustre: 1.6.6 Do you have an opportunity to test this on a newer release? > vanilla-kernel 2.6.22.19 Ideally on one of the platforms you can download binary RPMs from us for (i.e. RHEL5 or SLES10)? > 2) Mounting failed: > Nov 19 17:43:09 quadcore2 automount[21803]: attempting to mount entry > /lustre_automount > Nov 19 17:43:09 quadcore2 Lustre: Client fs_lustre-client has started > Nov 19 17:43:09 quadcore2 automount[21803]: mount(generic): mounted > m...@tcp0:m...@tcp0:/fs_lustre type lustre on /lustre_automount > Nov 19 17:43:09 quadcore2 automount[21803]: mounted /lustre_automount > Nov 19 17:43:10 quadcore2 LustreError: > 25321:0:(lib-move.c:111:lnet_try_match_md()) Matching packet from > 12345-192.168.16....@tcp, match 776 length 1336 too big: 1272 left, 1272 > allowed I think this is the key to this issue. There was one or more bugs around this symptom fixed in the 1.6.6-1.6.7 time frame. Perhaps even an upgrade to 1.6.7.2 might prove fruitful. It would likely require and MDS upgrade at least and should probably include clients and OSSes as well. Cheers, b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
