From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH v2] xfstest: confirm mkfs.gfs[2] in test 032
Date: Sat, 01 Nov 2008 14:19:10 -0500 [thread overview]
Message-ID: <490CABAE.2070402@sandeen.net> (raw)
In-Reply-To: <490C801E.9070405@sandeen.net>
mkfs.gfs[2] asks for confirmation before mkfs'ing; without
this test 032 hangs when mkfs.gfs2 is present.
Also, mkfs.gfs needs a few more args to make it go.
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
---
Index: xfs-cmds/xfstests/032
===================================================================
--- xfs-cmds.orig/xfstests/032
+++ xfs-cmds/xfstests/032
@@ -43,6 +43,8 @@ do
[ $fs = vfat ] && postargs=2000
# these folks prompt before writing
[ $fs = jfs ] && preop="echo Y |"
+ [ $fs = gfs ] && preop="echo y |" && preargs="-p lock_nolock -j 1"
+ [ $fs = gfs2 ] && preop="echo y |"
[ $fs = reiserfs ] && preop="echo y |" && preargs="-f"
# cramfs mkfs requires a directory argument
[ $fs = cramfs ] && preargs=/proc/fs/xfs
next prev parent reply other threads:[~2008-11-01 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 16:13 [PATCH] xfstest: confirm mkfs.gfs[2] in test 032 Eric Sandeen
2008-11-01 19:19 ` Eric Sandeen [this message]
2008-11-12 9:42 ` [PATCH v2] " Christoph Hellwig
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=490CABAE.2070402@sandeen.net \
--to=sandeen@sandeen.net \
--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