linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: xfs@oss.sgi.com
Cc: linux-fsdevel@vger.kernel.org, Richard Weinberger <richard@nod.at>
Subject: [PATCH] Do not check ocfs2
Date: Sun,  3 Mar 2013 01:05:50 +0100	[thread overview]
Message-ID: <1362269150-21478-1-git-send-email-richard@nod.at> (raw)

We cannot run fsck.ocfs2 because the file system
is most likely mounted on another node.

Signed-off-by: Richard Weinberger <richard@nod.at>
---
 common.rc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/common.rc b/common.rc
index f5180fe..00c075d 100644
--- a/common.rc
+++ b/common.rc
@@ -1419,6 +1419,9 @@ _check_test_fs()
     udf)
 	# do nothing for now
 	;;
+    ocfs2)
+	# other nodes may have mounted the fs
+	;;
     btrfs)
 	_check_btrfs_filesystem $TEST_DEV
 	;;
@@ -1448,6 +1451,9 @@ _check_scratch_fs()
     nfs*)
 	# Don't know how to check an NFS filesystem, yet.
 	;;
+    ocfs2)
+	# other nodes may have mounted the fs
+	;;
     btrfs)
 	_check_btrfs_filesystem $SCRATCH_DEV
 	;;
-- 
1.8.1.2


             reply	other threads:[~2013-03-03  0:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03  0:05 Richard Weinberger [this message]
2013-03-03  1:19 ` [PATCH] Do not check ocfs2 Dave Chinner
2013-03-03  9:02   ` Richard Weinberger
2013-03-03 22:04     ` Eric Sandeen
2013-03-03 22:19       ` Richard Weinberger
2013-03-03 22:40         ` Eric Sandeen
2013-03-03 22:53           ` Richard Weinberger
2013-03-03 22:57             ` Eric Sandeen
2013-03-04  0:42               ` Dave Chinner
2013-03-04 21:05                 ` Joel Becker
2013-03-04 22:09                   ` Richard Weinberger
2013-03-04 22:57                     ` Joel Becker

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=1362269150-21478-1-git-send-email-richard@nod.at \
    --to=richard@nod.at \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).