All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Tsvetkov <alexander.tsvetkov@oracle.com>
To: xfs@oss.sgi.com
Subject: maxpct option for small xfs filesystems
Date: Mon, 26 Jan 2015 19:14:43 +0300	[thread overview]
Message-ID: <54C667F3.8040303@oracle.com> (raw)

Hello,

I'm trying to understand the expected behaviour of "maxpct" option in 
case of small xfs filesystem
comparing the maximum percentage defined for this option with the 
percentage of actually allocated
inodes in filesystem, but the result of prepared test case doesn't 
correspond to the expectations:

[root@fedora ~]#mkfs.xfs -f -d size=16m -i maxpct=1 /dev/sdb2
[root@fedora ~]# mount /dev/sdb2 /mnt/scratch/
[root@fedora ~]# mount | grep scratch
/dev/sdb2 on /mnt/scratch type xfs 
(rw,relatime,seclabel,attr2,inode64,noquota)
[root@fedora ~]# xfs_info /mnt/scratch/
meta-data=/dev/sdb2        isize=256    agcount=1, agsize=4096 blks
                  =                       sectsz=512   attr=2, projid32bit=1
                  =                       crc=0        finobt=0
data          =                       bsize=4096   blocks=4096, imaxpct=1
                  =                       sunit=0      swidth=0 blks
naming     =version 2        bsize=4096   ascii-ci=0 ftype=0
log            =internal           bsize=4096   blocks=853, version=2
                  =                       sectsz=512   sunit=0 blks, 
lazy-count=1
realtime    =none               extsz=4096   blocks=0, rtextents=0

then trying to fill filesystem with lot of empty files until enospc 
obtained and break the loop:

[root@fedora ~]# for i in {0..100000}; do str=$(mktemp 
--tmpdir=/mnt/scratch tmp.XXXXXXXXXX); echo $str; done

filesystem is full with created files:

[root@fedora ~]# df -Th | grep scratch
/dev/sdb2      xfs        13M   13M  148K  99% /mnt/scratch

and from the number of actually created inodes:

[root@fedora ~]# xfs_db -c "blockget -n" -c "ncheck" /dev/sdb2 | wc -l
40512

it's calculated the space allocated for file inodes 9.9Mb (40512*256b 
inode size) that is about 77% of filesystem
space instead of defined maximum with maxpct=1% or even default 25% value.

Thanks,
Alexander Tsvetkov

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

             reply	other threads:[~2015-01-26 16:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 16:14 Alexander Tsvetkov [this message]
2015-01-26 22:37 ` maxpct option for small xfs filesystems Dave Chinner
2015-01-27 16:23   ` Alexander Tsvetkov
2015-01-27 16:31     ` Eric Sandeen
2015-01-27 19:15       ` Eric Sandeen
2015-01-28 10:41       ` Alexander Tsvetkov
2015-01-28 15:44         ` Eric Sandeen
2015-01-28 18:05         ` 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=54C667F3.8040303@oracle.com \
    --to=alexander.tsvetkov@oracle.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.