From: "Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
To: fstests@vger.kernel.org
Cc: "Eryu Guan" <eguan@redhat.com>,
jfs-discussion@lists.sourceforge.net,
"Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
Subject: [xfstests PATCH] common/rc: support jfs in _scratch_mkfs_sized
Date: Fri, 14 Jul 2017 19:06:19 -0300 [thread overview]
Message-ID: <20170714220616.GA3975@debian.home> (raw)
Add support for jfs in _scratch_mkfs_sized. Fix the block size in 4096,
which seems to be the only option in jfs_mkfs.
Signed-off-by: Ernesto A. Fernández <ernesto.mnd.fernandez@gmail.com>
---
This change in common/rc is different from the one sent as part of
generic/447, which was not working as intended. I will soon send a revision
of that patch as well.
common/rc | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/common/rc b/common/rc
index b505365..5cb6b0c 100644
--- a/common/rc
+++ b/common/rc
@@ -1023,6 +1023,8 @@ _scratch_mkfs_sized()
ext2|ext3|ext4|ext4dev|udf|btrfs|reiser4|ocfs2)
def_blksz=`echo $MKFS_OPTIONS| sed -rn 's/.*-b ?+([0-9]+).*/\1/p'`
;;
+ jfs)
+ def_blksz=4096
esac
[ -n "$def_blksz" ] && blocksize=$def_blksz
@@ -1068,6 +1070,9 @@ _scratch_mkfs_sized()
(( fssize <= 100 * 1024 * 1024 )) && mixed_opt='--mixed'
$MKFS_BTRFS_PROG $MKFS_OPTIONS $mixed_opt -b $fssize $SCRATCH_DEV
;;
+ jfs)
+ ${MKFS_PROG}.$FSTYP $MKFS_OPTIONS $SCRATCH_DEV $blocks
+ ;;
reiser4)
# mkfs.resier4 requires size in KB as input for creating filesystem
$MKFS_REISER4_PROG $MKFS_OPTIONS -y -b $blocksize $SCRATCH_DEV \
--
2.1.4
next reply other threads:[~2017-07-14 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 22:06 Ernesto A. Fernández [this message]
2017-07-19 1:37 ` [xfstests PATCH v2] common/rc: support jfs in _scratch_mkfs_sized Ernesto A. Fernández
2017-07-19 3:15 ` Eryu Guan
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=20170714220616.GA3975@debian.home \
--to=ernesto.mnd.fernandez@gmail.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=jfs-discussion@lists.sourceforge.net \
/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