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 <uja.ornl@gmail.com>
Reviewed-on: http://review.whamcloud.com/254
Tested-by: Hudson
Reviewed-by: Brian J. Murrell <brian@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>

diff --git a/lustre/utils/mount_lustre.c b/lustre/utils/mount_lustre.c
index 464dca9..d1b9f61 100644 (file)
--- 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));
                         if (verbose)
                                 fprintf(stderr, "warning: opening %s: %s\n",
                                         real_path, strerror(errno));

-                        return rc;
+                        return 0;

                 }
 
                 if (atoi(buf) >= md_stripe_cache_size)
                 }
 
                 if (atoi(buf) >= md_stripe_cache_size)