public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: zkabelac@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2/scripts fsadm.sh
Date: Wed, 10 Nov 2010 10:03:00 -0000	[thread overview]
Message-ID: <20101110100307.3127.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	zkabelac@sourceware.org	2010-11-10 10:03:07

Modified files:
	scripts        : fsadm.sh 

Log message:
	Scan also 'mount' output for mounted filesystem.
	
	As util-linux package seems to give all the time different names,
	try harder to figure out, where is the given lv possible mounted
	and scan /proc/mounts and if not found there, test also 'mount' output.
	
	/dev/dm-xxx
	/dev/mapper/vg-lv
	/dev/vg/lv
	
	All of them could be used different combination in /proc/mount and mount output.
	
	Patch fixes regression for older systems where new detection code failed to
	find valid combination.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/fsadm.sh.diff?cvsroot=lvm2&r1=1.21&r2=1.22

--- LVM2/scripts/fsadm.sh	2010/11/01 14:08:52	1.21
+++ LVM2/scripts/fsadm.sh	2010/11/10 10:03:07	1.22
@@ -199,6 +199,10 @@
 	# for empty string try again with real volume name
 	test -z "$MOUNTED" && MOUNTED=$($GREP ^"$RVOLUME" $PROCMOUNTS)
 
+	# for systems with different device names - check also mount output
+	test -z "$MOUNTED" && MOUNTED=$($MOUNT | $GREP ^"$VOLUME")
+	test -z "$MOUNTED" && MOUNTED=$($MOUNT | $GREP ^"$RVOLUME")
+
 	# cut device name prefix and trim everything past mountpoint
 	# echo translates \040 to spaces
 	MOUNTED=${MOUNTED#* }


             reply	other threads:[~2010-11-10 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 10:03 zkabelac [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-11 12:17 zkabelac
2010-10-08 11:18 zkabelac
2008-01-08 16:45 zkabelac
2007-12-17 14:47 agk

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=20101110100307.3127.qmail@sourceware.org \
    --to=zkabelac@sourceware.org \
    --cc=lvm-devel@redhat.com \
    --cc=lvm2-cvs@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 read-only IMAP folder(s) and NNTP newsgroup(s).