From: bmarzins@sourceware.org <bmarzins@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2/mount mount.gfs2.c util.c
Date: 25 Oct 2006 06:24:43 -0000 [thread overview]
Message-ID: <20061025062443.578.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: bmarzins at sourceware.org 2006-10-25 06:24:43
Modified files:
gfs2/mount : mount.gfs2.c util.c
Log message:
This is a bugfix for bz #211923.
When can't mount a filesystem because you already have it mounted, or some
similar reason, you print out a helpful message, so the user can fix the
problem.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/mount/mount.gfs2.c.diff?cvsroot=cluster&r1=1.19&r2=1.20
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/mount/util.c.diff?cvsroot=cluster&r1=1.17&r2=1.18
--- cluster/gfs2/mount/mount.gfs2.c 2006/10/14 20:16:19 1.19
+++ cluster/gfs2/mount/mount.gfs2.c 2006/10/25 06:24:43 1.20
@@ -190,6 +190,8 @@
umount_lockproto(proto, &mo, &sb, errno);
block_signals(SIG_UNBLOCK);
+ 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);
}
log_debug("mount(2) ok");
--- cluster/gfs2/mount/util.c 2006/10/16 15:05:30 1.17
+++ cluster/gfs2/mount/util.c 2006/10/25 06:24:43 1.18
@@ -448,6 +448,10 @@
rv = atoi(buf);
if (rv < 0) {
warn("lock_dlm_join: gfs_controld join error: %d", rv);
+ if (rv == -EEXIST)
+ warn("lock_dlm_join: mountgroup already exists. "
+ "Duplicate locktable name %s, or %s already "
+ "mounted\n", table, mo->dev);
goto out;
}
reply other threads:[~2006-10-25 6:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061025062443.578.qmail@sourceware.org \
--to=bmarzins@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).