All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael L. Semon" <mlsemon35@gmail.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH 2/2] xfstests: Add JFS support to _scratch_mkfs_sized
Date: Fri, 06 Sep 2013 16:59:36 -0400	[thread overview]
Message-ID: <522A4238.8050906@gmail.com> (raw)

This code works, with a little bit of tinkering.  I wanted to shovel 
it off to another function but didn't know what to do with the 
arguments.  In particular, the number_of_blocks value has to come 
after the dev name.

Thanks!

Michael

>From cb46931b9313d001813be459f829f551d955d781 Mon Sep 17 00:00:00 2001
From: "Michael L. Semon" <mlsemon35@gmail.com>
Date: Fri, 6 Sep 2013 05:50:05 -0400
Subject: [PATCH 2/2] xfstests: Add JFS support to _scratch_mkfs_sized

Add _scratch_mkfs_sized support for JFS.  Calculations are here
due to a jfs_mkfs log calculation issue when the file system size
is smaller than the partition size.  This issue is avoided by
specifying the log size (in megabytes) on the command line.
---
 common/rc | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/common/rc b/common/rc
index 191e9e5..58997d7 100644
--- a/common/rc
+++ b/common/rc
@@ -612,6 +612,15 @@ _scratch_mkfs_sized()
     btrfs)
 	$MKFS_BTRFS_PROG $MKFS_OPTIONS -b $fssize $SCRATCH_DEV
 	;;
+    jfs)
+	_scratch_options mkfs
+        jfs_log_sized=`expr $fssize / 16777216`
+	if `expr $jfs_log_sized \> 128`; then
+	    jfs_log_sized=128
+	fi
+	$MKFS_JFS_PROG -s $jfs_log_sized $SCRATCH_OPTIONS $MKFS_OPTIONS \
+	     $SCRATCH_DEV `expr $fssize / 4096` > /dev/null
+        ;;
     *)
 	_notrun "Filesystem $FSTYP not supported in _scratch_mkfs_sized"
 	;;
-- 
1.8.3.2

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

                 reply	other threads:[~2013-09-06 20:59 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=522A4238.8050906@gmail.com \
    --to=mlsemon35@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.