public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: xfs@oss.sgi.com
Subject: Re: higher agcount on LVM2 thinp volumes
Date: Thu, 29 Aug 2013 20:44:20 -0500	[thread overview]
Message-ID: <521FF8F4.9040009@hardwarefreak.com> (raw)
In-Reply-To: <321D1F95-5603-4571-A445-A267DA5F670F@colorremedies.com>

On 8/29/2013 1:09 AM, Chris Murphy wrote:
> 
> Is it expected when formatting, using defaults, that a thinp volume compared to either a conventional LV or partition of the same size, should have a higher agcount?
> 
> 
> HDD, GPT partitioned, 100GB partition size:
> 
> [root@f19s ~]# mkfs.xfs /dev/sda7
> meta-data=/dev/sda7              isize=256    agcount=4, agsize=6553600 blks
>          =                       sectsz=512   attr=2, projid32bit=0
> data     =                       bsize=4096   blocks=26214400, imaxpct=25
>          =                       sunit=0      swidth=0 blks
> naming   =version 2              bsize=4096   ascii-ci=0
> log      =internal log           bsize=4096   blocks=12800, version=2
>          =                       sectsz=512   sunit=0 blks, lazy-count=1
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> 
> 
> A 400GB partition, made into PV, PV added to VG, and all extents put into a thinpool volume, a 100GB virtual sized LV:
> 
> [root@f19s ~]# mkfs.xfs /dev/mapper/vg1-data
> meta-data=/dev/mapper/vg1-data   isize=256    agcount=16, agsize=1638400 blks
>          =                       sectsz=512   attr=2, projid32bit=0
> data     =                       bsize=4096   blocks=26214400, imaxpct=25
>          =                       sunit=0      swidth=0 blks
> naming   =version 2              bsize=4096   ascii-ci=0
> log      =internal log           bsize=4096   blocks=12800, version=2
>          =                       sectsz=512   sunit=0 blks, lazy-count=1
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> 
> 
> 
> I get agcount=4 on a conventional LV as well. Why agcount=16 on thinp?

More information would be helpful, specifically WRT the device stack
underlying mkfs.xfs.  I.e. we need to know more about the LVM configuration.

See:

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

-- 
Stan


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

  reply	other threads:[~2013-08-30  1:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  6:09 higher agcount on LVM2 thinp volumes Chris Murphy
2013-08-30  1:44 ` Stan Hoeppner [this message]
2013-08-30  2:08   ` Chris Murphy
2013-08-30  2:58     ` Dave Chinner
2013-08-30  3:21       ` Chris Murphy
2013-08-30  3:38         ` Dave Chinner
2013-08-30 17:55           ` Chris Murphy
2013-08-31  1:22             ` Eric Sandeen
2013-09-01  3:39               ` Chris Murphy
2013-08-30  3:04 ` Eric Sandeen
2013-08-30  3:18   ` Chris Murphy
2013-08-30  3:19     ` Eric Sandeen
2013-08-30  3:24       ` Chris Murphy
2013-08-30  3:29         ` Chris Murphy
2013-08-30  3:35         ` 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=521FF8F4.9040009@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=lists@colorremedies.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