From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: [PATCH] fix xfsqa on whole disks
Date: Mon, 24 Nov 2008 23:22:59 -0500 [thread overview]
Message-ID: <20081125042259.GA22092@infradead.org> (raw)
mkfe2fs unfortunately hasn't heard about real enterprise setups using
whole disks and needs the -F option to create a filesystem on those
without asking stupid questions that make the testcases block forever.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: xfstests/032
===================================================================
RCS file: /cvs/xfs-cmds/xfstests/032,v
retrieving revision 1.14
diff -u -p -r1.14 032
--- xfstests/032 29 May 2008 17:01:09 -0000 1.14
+++ xfstests/032 25 Nov 2008 04:18:59 -0000
@@ -46,6 +46,10 @@ do
[ $fs = reiserfs ] && preop="echo y |" && preargs="-f"
# cramfs mkfs requires a directory argument
[ $fs = cramfs ] && preargs=/proc/fs/xfs
+ [ $fs = ext2 ] && preargs="-F"
+ [ $fs = ext3 ] && preargs="-F"
+ [ $fs = ext4 ] && preargs="-F"
+ [ $fs = ext4dev ] && preargs="-F"
# overwite the first few Kb - should blow away superblocks
src/devzero -n 20 $SCRATCH_DEV >/dev/null
Index: xfstests/049
===================================================================
RCS file: /cvs/xfs-cmds/xfstests/049,v
retrieving revision 1.16
diff -u -p -r1.16 049
--- xfstests/049 29 Jun 2007 06:16:22 -0000 1.16
+++ xfstests/049 25 Nov 2008 04:18:59 -0000
@@ -60,7 +60,7 @@ echo "--- mounts" >> $seq.full
mount >> $seq.full
_log "Create ext2 fs on scratch"
-mkfs -t ext2 $SCRATCH_DEV >> $seq.full 2>&1 \
+mkfs -t ext2 -F $SCRATCH_DEV >> $seq.full 2>&1 \
|| _fail "!!! failed to mkfs ext2"
_log "Mount ext2 fs on scratch"
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2008-11-25 4:23 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=20081125042259.GA22092@infradead.org \
--to=hch@infradead.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