All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Adamski <k@adamski.org>
To: Stefan Ring <stefanrin@gmail.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
	Joe Landman <joe.landman@gmail.com>,
	linux-raid <linux-raid@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: very slow file deletion on an SSD
Date: Sun, 27 May 2012 09:15:04 -0400	[thread overview]
Message-ID: <1338124504.28212.255.camel@oxygen.netxsys.com> (raw)
In-Reply-To: <CAAxjCEzX4dmm6YuR__1_a6mw+D=vizV0VrCLqCC-d5GSgkbE6g@mail.gmail.com>

On Sun, 2012-05-27 at 09:34 +0200, Stefan Ring wrote:
> >> [root@siFlash test]# xfs_bmap -vp 2.r.96.0
> >> xfs_bmap: xfsctl(XFS_IOC_GETBMAPX) iflags=0x4 ["2.r.96.0"]: Cannot allocate memory
> >
> > Try filefrag -v maybe, if your e2fsprogs is new enough.
> >
> > Trying to remember, ENOMEM in bmap rings a bell... but this is possibly indicative of an extremely fragmented file.
> 
> True, I've had it happen with extremely fragmented files.
> 
> I've started playing around with discard myself only recently, but so
> far I like the approach of using fstrim a lot better than the discard
> option: http://xfs.org/index.php/FITRIM/discard

Check what blockdev --getra <md device> is set to. I used to have a
several second deletes on large (4GB) fragmented files when ra was the
default 256. Once I changed it to 4096 (best value will depend on your
setup) the deletes became instant.

K


WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Adamski <k@adamski.org>
To: Stefan Ring <stefanrin@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>,
	xfs@oss.sgi.com, Eric Sandeen <sandeen@sandeen.net>,
	Joe Landman <joe.landman@gmail.com>
Subject: Re: very slow file deletion on an SSD
Date: Sun, 27 May 2012 09:15:04 -0400	[thread overview]
Message-ID: <1338124504.28212.255.camel@oxygen.netxsys.com> (raw)
In-Reply-To: <CAAxjCEzX4dmm6YuR__1_a6mw+D=vizV0VrCLqCC-d5GSgkbE6g@mail.gmail.com>

On Sun, 2012-05-27 at 09:34 +0200, Stefan Ring wrote:
> >> [root@siFlash test]# xfs_bmap -vp 2.r.96.0
> >> xfs_bmap: xfsctl(XFS_IOC_GETBMAPX) iflags=0x4 ["2.r.96.0"]: Cannot allocate memory
> >
> > Try filefrag -v maybe, if your e2fsprogs is new enough.
> >
> > Trying to remember, ENOMEM in bmap rings a bell... but this is possibly indicative of an extremely fragmented file.
> 
> True, I've had it happen with extremely fragmented files.
> 
> I've started playing around with discard myself only recently, but so
> far I like the approach of using fstrim a lot better than the discard
> option: http://xfs.org/index.php/FITRIM/discard

Check what blockdev --getra <md device> is set to. I used to have a
several second deletes on large (4GB) fragmented files when ra was the
default 256. Once I changed it to 4096 (best value will depend on your
setup) the deletes became instant.

K

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

  reply	other threads:[~2012-05-27 13:15 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25 10:37 very slow file deletion on an SSD Joe Landman
2012-05-25 10:37 ` Joe Landman
2012-05-25 10:45 ` Bernd Schubert
2012-05-25 10:45   ` Bernd Schubert
2012-05-25 10:49   ` Joe Landman
2012-05-25 10:49     ` Joe Landman
2012-05-25 14:48     ` Roberto Spadim
2012-05-25 14:48       ` Roberto Spadim
2012-05-25 16:57 ` Ben Myers
2012-05-25 16:57   ` Ben Myers
2012-05-25 16:54   ` Joe Landman
2012-05-25 16:54     ` Joe Landman
2012-05-25 16:59   ` Christoph Hellwig
2012-05-25 16:59     ` Christoph Hellwig
2012-05-26 16:00     ` David Brown
2012-05-26 16:00       ` David Brown
2012-05-26 19:56 ` Stan Hoeppner
2012-05-26 19:56   ` Stan Hoeppner
2012-05-26 23:18 ` Dave Chinner
2012-05-26 23:25   ` Joe Landman
2012-05-26 23:25     ` Joe Landman
2012-05-27  0:07     ` Dave Chinner
2012-05-27  0:07       ` Dave Chinner
2012-05-27  0:10       ` joe.landman
2012-05-27  0:10         ` joe.landman
2012-05-27  1:49       ` Joe Landman
2012-05-27  1:49         ` Joe Landman
2012-05-27  2:40         ` Eric Sandeen
2012-05-27  2:43           ` Eric Sandeen
2012-05-27  7:34           ` Stefan Ring
2012-05-27 13:15             ` Krzysztof Adamski [this message]
2012-05-27 13:15               ` Krzysztof Adamski
2012-05-27 14:59               ` joe.landman
2012-05-27 14:59                 ` joe.landman
2012-05-27 16:07                 ` Eric Sandeen
2012-05-27 16:07                   ` Eric Sandeen
2012-05-27 17:14                   ` Joe Landman
2012-05-27 17:14                     ` Joe Landman
2012-05-27 19:24                     ` Peter Grandi
2012-05-27 17:17                   ` Joe Landman
2012-05-27 17:17                     ` Joe Landman
2012-05-26 23:55   ` Joe Landman
2012-05-26 23:55     ` Joe Landman
2012-05-27  0:07     ` Jon Nelson

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=1338124504.28212.255.camel@oxygen.netxsys.com \
    --to=k@adamski.org \
    --cc=joe.landman@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=stefanrin@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.