All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: xfs@oss.sgi.com
Subject: XFS filesystem reports as full though it isn't
Date: Fri, 16 May 2008 22:27:55 +0200	[thread overview]
Message-ID: <20080516222755.3e557c00@galadriel.home> (raw)


I have a 64 bits (x86_64) machine running Linux 2.6.22.19 with a 24TB
XFS filesystem. There are some 15TB of data on it. All is well, no
error except that I can't create a single file (touch foo : no space
left on device). I don't understand what can be going wrong... 

History : this filesystem was extended (xfs_growfs) from 16TB to 24.

I've tought about all XFS problems I can remember of; first, inode
exhaustion :

cluster1:/proc/sys/fs# df -i
Sys. de fich.         Inodes   IUtil.  ILib. %IUti. Mont?sur
/dev/sda1                  0       0       0    -  /
tmpfs                2058624       3 2058621    1% /lib/init/rw
udev                 2058624    1445 2057179    1% /dev
tmpfs                2058624       1 2058623    1% /dev/shm
/dev/mapper/vg0-lv0  25379856384    4287 25379852097    1% /mnt/raid

OK so there's still plenty of inodes available here, that should be OK.
Then maybe we have something wrong elsewhere :

cluster1:/proc/sys/fs# xfs_db -r -c 'freesp -s -a 0' /dev/vg0/lv0
   from      to extents  blocks    pct
      1       1       5       5  71.43
      2       3       1       2  28.57
total free extents 6
total free blocks 7
average free extent size 1.16667

7 blocks free? But there are 9 TB of free space! 

Here is the output from xfs_info /dev/vg0/lv0

meta-data=/dev/vg0/lv0           isize=256    agcount=47,
agsize=137245616 blks =                       sectsz=512   attr=0
data     =                       bsize=4096   blocks=6344964096,
imaxpct=25 =                       sunit=16     swidth=32 blks,
unwritten=1 naming   =version 2              bsize=4096  
log      =internal               bsize=4096   blocks=32768, version=1
         =                       sectsz=512   sunit=0 blks
realtime =none                   extsz=131072 blocks=0, rtextents=0

I fail to see nothing special there however.

The only significant thing I see is that the FS is really close to 16
TB of allocated data (15.7TB). I tried mounting it with "inode64"
option with no more loving.

Any help would be tremendously welcome. Users are starving for more
space and they can't even create a single file! 

-- 
--------------------------------------------------
Emmanuel Florac               www.intellique.com   
--------------------------------------------------

             reply	other threads:[~2008-05-16 20:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 20:27 Emmanuel Florac [this message]
2008-05-18 12:45 ` XFS filesystem reports as full though it isn't Emmanuel Florac
2008-05-18 13:18 ` Christoph Hellwig
2008-05-18 13:21   ` Christoph Hellwig
2008-05-18 13:42     ` Emmanuel Florac
2008-05-19 20:10       ` Emmanuel Florac
2008-05-20  6:10         ` David Chinner
2008-05-20 10:17           ` Emmanuel Florac
2008-05-20 10:19         ` Christoph Hellwig
2008-05-20 12:39           ` Emmanuel Florac
2008-05-19 11:31 ` Christian Røsnes
2008-05-19 11:48   ` Christian Røsnes
2008-05-19 20:39     ` Emmanuel Florac

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=20080516222755.3e557c00@galadriel.home \
    --to=eflorac@intellique.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.