archive mirror
 help / color / mirror / Atom feed
From: Steve Lord <>
To: Jose Luis Alarcon <>
Cc: Nathan Scott <>,
	Linux Kernel <>
Subject: Re: xfs problems (2.6.0-test2)
Date: 01 Aug 2003 08:55:40 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, 2003-08-01 at 02:58, Jose Luis Alarcon wrote:
> >
> >Hi there,
> >
> >What XFS blocksize are you using, and what is your page size?
> >There are known issues when using blocksizes smaller than the
> >page size in the 2.6 XFS code at the moment.
> >
>   Hi Nathan, and congratilations for the SGI work.
>   Now i have a Mandrake with the 2.5.75 kernel and XFS in
> all partitions. The filesystem looks work very well.
>   I am planning install 2.6.0-test3 when it comes and i wanna
> ask you: how can i know what blocksize am i using?, and how
> know what is the page size in my system?.
>   Thanks you, very much, in advance.
>   Regards.
>   Jose.

Use the xfs_info command on a mount point:

meta-data=/xfs                   isize=256    agcount=8, agsize=131031
         =                       sectsz=512  
data     =                       bsize=4096   blocks=1048241, imaxpct=25
         =                       sunit=0      swidth=0 blks, unwritten=1
naming   =version 2              bsize=4096  
log      =internal               bsize=4096   blocks=16384, version=1
         =                       sectsz=512   sunit=0 blks
realtime =none                   extsz=65536  blocks=0, rtextents=0

bsize=4096 is the vlock size.



Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email:

  reply	other threads:[~2003-08-01 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01  7:58 xfs problems (2.6.0-test2) Jose Luis Alarcon
2003-08-01 13:55 ` Steve Lord [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-01  2:31 Mariusz Zielinski
2003-08-01  2:40 ` Nathan Scott
2003-08-01  4:38   ` Chris Meadors

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).