From: Christoph Hellwig <hch@infradead.org>
To: Daniel Goller <morfic@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: State of XFS on ARM
Date: Wed, 3 Feb 2010 15:38:33 -0500 [thread overview]
Message-ID: <20100203203833.GA31908@infradead.org> (raw)
In-Reply-To: <13bb8ce11002031234t4b02b199g5b8dfd65ea48aa13@mail.gmail.com>
On Wed, Feb 03, 2010 at 02:34:43PM -0600, 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?
The primary use of the large buffers where this matters is the log.
So you just need to cleanly unmount and mount the filesystem again,
and the issues your previously reported should be gone.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-02-03 20:37 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 [this message]
2010-02-03 20:46 ` Eric Sandeen
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=20100203203833.GA31908@infradead.org \
--to=hch@infradead.org \
--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