All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Mark Lord <kernel@teksavvy.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	xfs@oss.sgi.com, Linux Kernel <linux-kernel@vger.kernel.org>,
	Alex Elder <aelder@sgi.com>
Subject: Re: xfs: very slow after mount, very slow at umount
Date: Fri, 28 Jan 2011 10:39:29 +1100	[thread overview]
Message-ID: <20110127233929.GM21311@dastard> (raw)
In-Reply-To: <4D40EB2F.2050809@teksavvy.com>

On Wed, Jan 26, 2011 at 10:49:03PM -0500, Mark Lord wrote:
> On 11-01-26 10:30 PM, Dave Chinner wrote:
> > [Please cc xfs@oss.sgi.com on XFS bug reports. Added.]
> >
> > On Wed, Jan 26, 2011 at 08:22:25PM -0500, Mark Lord wrote:
> >> Alex / Christoph,
> >>
> >> My mythtv box here uses XFS on a 2TB drive for storing recordings and videos.
> >> It is behaving rather strangely though, and has gotten worse recently.
> >> Here is what I see happening:
> >>
> >> The drive mounts fine at boot, but the very first attempt to write a new file
> >> to the filesystem suffers from a very very long pause, 30-60 seconds, during which
> >> time the disk activity light is fully "on".
> >
> > Please post the output of xfs_info <mtpt> so we can see what you
> > filesystem configuration is.
> 
>    /dev/sdb1 on /var/lib/mythtv type xfs
> (rw,noatime,allocsize=64M,logbufs=8,largeio)
> 
>    [~] xfs_info /var/lib/mythtv
>    meta-data=/dev/sdb1              isize=256    agcount=7453, agsize=65536 blks
>             =                       sectsz=512   attr=2
>    data     =                       bsize=4096   blocks=488378638, imaxpct=5
>             =                       sunit=0      swidth=0 blks
>    naming   =version 2              bsize=4096   ascii-ci=0
>    log      =internal               bsize=4096   blocks=32768, version=2
>             =                       sectsz=512   sunit=0 blks, lazy-count=0
>    realtime =none                   extsz=4096   blocks=0, rtextents=0

7453 AGs means that the first write coud cause up to ~7500 disk
reads to occur as the AGF headers are read in to find where the
best free space extent for allocation lies.

That'll be your problem.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Mark Lord <kernel@teksavvy.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Alex Elder <aelder@sgi.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: xfs: very slow after mount, very slow at umount
Date: Fri, 28 Jan 2011 10:39:29 +1100	[thread overview]
Message-ID: <20110127233929.GM21311@dastard> (raw)
In-Reply-To: <4D40EB2F.2050809@teksavvy.com>

On Wed, Jan 26, 2011 at 10:49:03PM -0500, Mark Lord wrote:
> On 11-01-26 10:30 PM, Dave Chinner wrote:
> > [Please cc xfs@oss.sgi.com on XFS bug reports. Added.]
> >
> > On Wed, Jan 26, 2011 at 08:22:25PM -0500, Mark Lord wrote:
> >> Alex / Christoph,
> >>
> >> My mythtv box here uses XFS on a 2TB drive for storing recordings and videos.
> >> It is behaving rather strangely though, and has gotten worse recently.
> >> Here is what I see happening:
> >>
> >> The drive mounts fine at boot, but the very first attempt to write a new file
> >> to the filesystem suffers from a very very long pause, 30-60 seconds, during which
> >> time the disk activity light is fully "on".
> >
> > Please post the output of xfs_info <mtpt> so we can see what you
> > filesystem configuration is.
> 
>    /dev/sdb1 on /var/lib/mythtv type xfs
> (rw,noatime,allocsize=64M,logbufs=8,largeio)
> 
>    [~] xfs_info /var/lib/mythtv
>    meta-data=/dev/sdb1              isize=256    agcount=7453, agsize=65536 blks
>             =                       sectsz=512   attr=2
>    data     =                       bsize=4096   blocks=488378638, imaxpct=5
>             =                       sunit=0      swidth=0 blks
>    naming   =version 2              bsize=4096   ascii-ci=0
>    log      =internal               bsize=4096   blocks=32768, version=2
>             =                       sectsz=512   sunit=0 blks, lazy-count=0
>    realtime =none                   extsz=4096   blocks=0, rtextents=0

7453 AGs means that the first write coud cause up to ~7500 disk
reads to occur as the AGF headers are read in to find where the
best free space extent for allocation lies.

That'll be your problem.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2011-01-27 23:37 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27  1:22 xfs: very slow after mount, very slow at umount Mark Lord
2011-01-27  1:43 ` Mark Lord
2011-01-27  3:43   ` Dave Chinner
2011-01-27  3:43     ` Dave Chinner
2011-01-27  3:53     ` Mark Lord
2011-01-27  3:53       ` Mark Lord
2011-01-27  4:54       ` Mark Lord
2011-01-27  4:54         ` Mark Lord
2011-01-27 23:34       ` Dave Chinner
2011-01-27 23:34         ` Dave Chinner
2011-01-27  3:30 ` Dave Chinner
2011-01-27  3:30   ` Dave Chinner
2011-01-27  3:49   ` Mark Lord
2011-01-27  3:49     ` Mark Lord
2011-01-27  5:17     ` Stan Hoeppner
2011-01-27 15:12     ` Mark Lord
2011-01-27 15:12       ` Mark Lord
2011-01-27 15:40       ` Justin Piszcz
2011-01-27 15:40         ` Justin Piszcz
2011-01-27 16:03         ` Mark Lord
2011-01-27 16:03           ` Mark Lord
2011-01-27 19:40           ` Stan Hoeppner
2011-01-27 19:40             ` Stan Hoeppner
2011-01-27 20:11             ` david
2011-01-27 20:11               ` david
2011-01-27 23:53               ` Stan Hoeppner
2011-01-27 23:53                 ` Stan Hoeppner
2011-01-28  2:09                 ` david
2011-01-28  2:09                   ` david
2011-01-28 13:56                   ` Dave Chinner
2011-01-28 13:56                     ` Dave Chinner
2011-01-28 19:26                     ` david
2011-01-28 19:26                       ` david
2011-01-29  5:40                       ` Dave Chinner
2011-01-29  5:40                         ` Dave Chinner
2011-01-29  6:08                         ` david
2011-01-29  6:08                           ` david
2011-01-29  7:35                           ` Dave Chinner
2011-01-29  7:35                             ` Dave Chinner
2011-01-31 19:17                             ` Christoph Hellwig
2011-01-31 19:17                               ` Christoph Hellwig
2011-01-27 21:56             ` Mark Lord
2011-01-27 21:56               ` Mark Lord
2011-01-28  0:17               ` Dave Chinner
2011-01-28  0:17                 ` Dave Chinner
2011-01-28  1:22                 ` Mark Lord
2011-01-28  1:22                   ` Mark Lord
2011-01-28  1:36                   ` Mark Lord
2011-01-28  1:36                     ` Mark Lord
2011-01-28  4:14                   ` David Rees
2011-01-28  4:14                     ` David Rees
2011-01-28 14:22                     ` Mark Lord
2011-01-28 14:22                       ` Mark Lord
2011-01-28  7:31                   ` Dave Chinner
2011-01-28  7:31                     ` Dave Chinner
2011-01-28 14:33                     ` Mark Lord
2011-01-28 14:33                       ` Mark Lord
2011-01-28 23:58                       ` Dave Chinner
2011-01-28 23:58                         ` Dave Chinner
2011-01-28 19:18             ` Martin Steigerwald
2011-01-28 19:18               ` Martin Steigerwald
2011-01-27 20:24           ` John Stoffel
2011-01-27 20:24             ` John Stoffel
2011-01-27 23:41       ` Dave Chinner
2011-01-27 23:41         ` Dave Chinner
2011-01-28  0:59         ` Mark Lord
2011-01-28  0:59           ` Mark Lord
2011-01-27 23:39     ` Dave Chinner [this message]
2011-01-27 23:39       ` 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=20110127233929.GM21311@dastard \
    --to=david@fromorbit.com \
    --cc=aelder@sgi.com \
    --cc=hch@infradead.org \
    --cc=kernel@teksavvy.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.