public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Czerner <lczerner@redhat.com>
To: xfs@oss.sgi.com
Cc: Lukas Czerner <lczerner@redhat.com>
Subject: [PATCH 10/10] xfstests: Remount file system if MOUNT_OPTIONS changed
Date: Wed, 10 Jul 2013 16:00:39 +0200	[thread overview]
Message-ID: <1373464839-31535-11-git-send-email-lczerner@redhat.com> (raw)
In-Reply-To: <1373464839-31535-1-git-send-email-lczerner@redhat.com>

When MOUNT_OPTIONS change we should remount TEST_DEV to put the changes
in effect. This will allow us to have different MOUNT_OPTIONS in sections
in configuration file.

Signed-off-by: Lukas Czerner <lczerner@redhat.com>
---
 README.config-sections | 8 ++++++++
 check                  | 8 ++++++++
 2 files changed, 16 insertions(+)

diff --git a/README.config-sections b/README.config-sections
index 4d60272..2849fd5 100644
--- a/README.config-sections
+++ b/README.config-sections
@@ -36,6 +36,14 @@ For every section xfstests will run with specified options and will produce
 separate results in the '$RESULT_BASE/$section_name' directory.
 
 
+Different mount options
+-----------------------
+
+Specifying different mount options in difference config sections is allowed.
+When MOUNT_OPTIONS differs in the following section TEST_DEV will be remounted
+with new MOUNT_OPTIONS automatically before running the test.
+
+
 Multiple file systems
 ---------------------
 
diff --git a/check b/check
index e6f6066..2d9496f 100755
--- a/check
+++ b/check
@@ -393,6 +393,7 @@ fi
 
 for section in $HOST_OPTIONS_SECTIONS; do
 	OLD_FSTYP=$FSTYP
+	OLD_MOUNT_OPTIONS=$MOUNT_OPTIONS
 	get_next_config $section
 
 	mkdir -p $RESULT_BASE
@@ -420,6 +421,13 @@ for section in $HOST_OPTIONS_SECTIONS; do
 			echo $out
 			exit 1
 		fi
+	elif [ "$OLD_MOUNT_OPTIONS" != "$MOUNT_OPTIONS" ]; then
+		_umount_or_remount_ro $TEST_DEV 2>&1> /dev/null
+		out=`_mount_or_remount_rw "$MOUNT_OPTIONS" $TEST_DEV $TEST_DIR`
+		if [ $? -ne 1 ]; then
+			echo $out
+			exit 1
+		fi
 	fi
 
 	init_rc
-- 
1.8.3.1

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2013-07-10 14:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 14:00 [RFC][PATCH 00/10] xfstests: Add support for config section Lukas Czerner
2013-07-10 14:00 ` [PATCH 01/10] xfstests: Run all tests when nothing is specified Lukas Czerner
2013-07-10 14:00 ` [PATCH 02/10] xfstests: Export all important variables in common/config Lukas Czerner
2013-07-10 14:00 ` [PATCH 03/10] xfstests: Refactor code for obtaining test list Lukas Czerner
2013-07-10 14:00 ` [PATCH 04/10] xfstests: Allow to recheck options in common/rc Lukas Czerner
2013-07-10 14:00 ` [PATCH 05/10] xfstests: Allow to re-read configuration Lukas Czerner
2013-07-10 14:00 ` [PATCH 06/10] xfstests: Allow to specify RESULT_BASE directory Lukas Czerner
2013-07-10 14:00 ` [PATCH 07/10] xfstests: Prepare for config section Lukas Czerner
2013-07-10 14:00 ` [PATCH 08/10] xfstests: Add support for sections in config file Lukas Czerner
2013-07-10 14:00 ` [PATCH 09/10] xfstests: Allow to recreate TEST_DEV Lukas Czerner
2013-07-10 14:00 ` Lukas Czerner [this message]

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=1373464839-31535-11-git-send-email-lczerner@redhat.com \
    --to=lczerner@redhat.com \
    --cc=xfs@oss.sgi.com \
    /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