cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2/mount mount.gfs2.c
Date: 6 Aug 2007 19:23:41 -0000	[thread overview]
Message-ID: <20070806192341.21877.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	teigland at sourceware.org	2007-08-06 19:23:40

Modified files:
	gfs2/mount     : mount.gfs2.c 

Log message:
	Remove check_sys_fs() since it breaks on-demand fs module loading from the
	kernel (already changed on RHEL5 branch).
	Use strerror() instead of errno in another spot to be more user friendly.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/mount/mount.gfs2.c.diff?cvsroot=cluster&r1=1.25&r2=1.26

--- cluster/gfs2/mount/mount.gfs2.c	2007/07/19 22:20:50	1.25
+++ cluster/gfs2/mount/mount.gfs2.c	2007/08/06 19:23:40	1.26
@@ -155,6 +155,7 @@
 		lock_dlm_leave(mo, sb, mnterr);
 }
 
+#if 0
 static void check_sys_fs(char *fsname)
 {
 	DIR *d;
@@ -176,6 +177,7 @@
 	die("fs type \"%s\" not found in /sys/fs/, is the module loaded?\n",
 	    fsname);
 }
+#endif
 
 int main(int argc, char **argv)
 {
@@ -199,7 +201,11 @@
 		exit(EXIT_SUCCESS);
 	}
 
-	check_sys_fs(fsname);
+	/* This breaks on-demand fs module loading from the kernel; could we
+	   try to load the module first here and then check again and fail if
+	   nothing?  I'd really like to avoid joining the group and then
+	   backing out if the mount fails to load the module. */
+	/* check_sys_fs(fsname); */
 
 	read_options(argc, argv, &mo);
 	check_options(&mo);
@@ -227,7 +233,8 @@
 
 		if (errno == EBUSY)
 			die("%s already mounted or %s busy\n", mo.dev, mo.dir);
-		die("error %d mounting %s on %s\n", errno, mo.dev, mo.dir);
+		die("error mounting %s on %s: %s\n", mo.dev, mo.dir,
+		    strerror(errno));
 	}
 	log_debug("mount(2) ok");
 	mount_result_lockproto(proto, &mo, &sb, 0);



             reply	other threads:[~2007-08-06 19:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 19:23 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-18 17:51 [Cluster-devel] cluster/gfs2/mount mount.gfs2.c adas
2008-01-18 17:51 adas
2007-08-06 19:26 teigland
2007-07-26 16:36 cfeist
2007-07-26 16:34 cfeist
2007-07-19 22:21 adas
2007-07-19 22:21 adas
2007-07-19 22:20 adas
2007-05-14 19:08 rpeterso
2007-05-14 19:01 rpeterso
2007-04-23 19:18 teigland
2007-04-23 19:18 teigland
2006-08-11 16:59 teigland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070806192341.21877.qmail@sourceware.org \
    --to=teigland@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).