From 76aa18132e117b2a984edc62e731a4ca9efca4e8 Mon Sep 17 00:00:00 2001 From: James Simmons Date: Fri, 18 Feb 2011 13:58:41 -0500 Subject: [PATCH 1/1] No bugzilla for this. One of the test failing was config-sanity.sh test number 37. So I tracked it down to way. The reason was the mounts were failing. Upon investigation I discovered the test caught a error reported back by the mount. I tracked it down to the section of code in the patch. Basically mount_lustre.c attempts to set the stripe_cache_size for /dev/mdX devices. The problem is this extra feature is present for certain classes of md devices. In the case of our test bed we are one of the classes that lacks this enhancement. So instead of failing to mount in that case we just print a warning that the special param is not present but still succed to mount. Change-Id: Ib8a743e77b5e6994e2640c51b781f7d0d345d5a7 Signed-off-by: James Simmons Reviewed-on: http://review.whamcloud.com/254 Tested-by: Hudson Reviewed-by: Brian J. Murrell Reviewed-by: Oleg Drokin --- lustre/utils/mount_lustre.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lustre/utils/mount_lustre.c b/lustre/utils/mount_lustre.c index 464dca9..d1b9f61 100644 --- a/lustre/utils/mount_lustre.c +++ b/lustre/utils/mount_lustre.c @@ -463,7 +463,7 @@ set_params: if (verbose) fprintf(stderr, "warning: opening %s: %s\n", real_path, strerror(errno)); - return rc; + return 0; } if (atoi(buf) >= md_stripe_cache_size) -- 1.8.3.1