public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: how to use fstrim?
Date: Fri, 26 Jul 2013 16:37:37 -0500	[thread overview]
Message-ID: <51F2EC21.6000208@sandeen.net> (raw)
In-Reply-To: <51F2BD31.5060301@profihost.ag>

On 7/26/13 1:17 PM, Stefan Priebe wrote:
> Hi,
> 
> what is the right way to use fstrim on top of XFS? just doing fstrim -v -m 4194304 /
> 
> results sometimes (might depend on disk i/o) to hanging tasks and stack traces - fstrim needs > 5 min in these cases.

As always, it's better to include things like the actual stack traces you got, so we have some idea what's going on ...

How fast it goes probably depends quite a lot on the storage underneath.

So including storage information as well would also help us give you a meaningful answer...

And kernel version... etc.

http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F

-Eric

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

  reply	other threads:[~2013-07-26 21:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 18:17 how to use fstrim? Stefan Priebe
2013-07-26 21:37 ` Eric Sandeen [this message]
2013-07-27  1:50 ` [xfs-masters] " Dave Chinner
2013-07-30 19:37   ` Stefan Priebe
2013-07-30 22:34     ` Dave Chinner
2013-07-31 13:26   ` Greg Freemyer
2013-08-01  0:08     ` Dave Chinner

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=51F2EC21.6000208@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=s.priebe@profihost.ag \
    --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