From: Eric Sandeen <sandeen@sandeen.net>
To: Daniel Goller <morfic@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: State of XFS on ARM
Date: Wed, 03 Feb 2010 14:46:11 -0600 [thread overview]
Message-ID: <4B69E093.6000105@sandeen.net> (raw)
In-Reply-To: <13bb8ce11002031234t4b02b199g5b8dfd65ea48aa13@mail.gmail.com>
Daniel Goller wrote:
> Any particular stress test you can suggest, to use once i try git for
> xfs on this Marvell box?
> To try to help bringing up issues faster than through normal use of this box?
Run it through the xfstests suite:
http://git.kernel.org/?p=fs/xfs/xfstests-dev.git;a=summary
(I have a sheevaplug too, thanks to some nice folks @Marvell, and
I really need to get regular qa going on it in return... have been
too busy so far) :(
There's a readme in the tree, but basically just create a local.config like:
# - setenv TEST_DEV "device containing TEST PARTITION"
# - setenv TEST_DIR "mount point of TEST PARTITION"
# - setenv SCRATCH_DEV "device containing SCRATCH PARTITION"
# - setenv SCRATCH_MNT "mount point for SCRATCH PARTITION"
TEST_DEV=/dev/sdb1
TEST_DIR=/mnt/test
SCRATCH_DEV=/dev/sdb3
SCRATCH_MNT=/mnt/scratch
mkfs.xfs $TEST_DEV, and then run
#./check -g auto
-Eric
> Thanks in advance for any suggestions,
>
> Daniel
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-02-03 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 3:24 State of XFS on ARM Daniel Goller
2010-02-02 3:52 ` Eric Sandeen
2010-02-02 11:23 ` Christoph Hellwig
2010-02-02 15:42 ` Richard Sharpe
2010-02-02 16:12 ` James Bottomley
2010-02-03 2:19 ` Daniel Goller
2010-02-03 20:34 ` Daniel Goller
2010-02-03 20:38 ` Christoph Hellwig
2010-02-03 20:46 ` Eric Sandeen [this message]
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=4B69E093.6000105@sandeen.net \
--to=sandeen@sandeen.net \
--cc=morfic@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox