From: Dave Hall <kdhall@binghamton.edu>
To: xfs@oss.sgi.com
Subject: Slightly Urgent: XFS No Space Left On Device
Date: Mon, 30 Mar 2015 14:19:59 -0400 [thread overview]
Message-ID: <551993CF.4060908@binghamton.edu> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2538 bytes --]
Hello,
I have an XFS file system that's getting 'No space left on device'
errors. xfs_fsr also complains of 'No space left'. The XFS Info is:
# xfs_info /data
meta-data=/dev/sdb1 isize=256 agcount=19,
agsize=268435440 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=4882431488, imaxpct=5
= sunit=16 swidth=160 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal bsize=4096 blocks=521728, version=2
= sectsz=512 sunit=16 blks,
lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
# df -h .
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 19T 12T 7.0T 62% /data
# df -ih .
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sdb1 3.7G 4.7M 3.7G 1% /data
xfs_db freesp shows that AG 0 seems to be full. I've included the
freesp for the first few AGs, but the rest seem pretty consistent with
AGs 1 - 4 that I've included below.
xfs_db> freesp -s -e 1000000000 -a 0
from to extents blocks pct
1 268435440 1930 3795 100.00
total free extents 1930
total free blocks 3795
average free extent size 1.96632
xfs_db> freesp -s -e 1000000000 -a 1
from to extents blocks pct
1 268435440 287006 173832255 100.00
total free extents 287006
total free blocks 173832255
average free extent size 605.675
xfs_db> freesp -s -e 1000000000 -a 2
from to extents blocks pct
1 268435440 272425 94291252 100.00
total free extents 272425
total free blocks 94291252
average free extent size 346.118
xfs_db> freesp -s -e 1000000000 -a 3
from to extents blocks pct
1 268435440 286421 110208404 100.00
total free extents 286421
total free blocks 110208404
average free extent size 384.778
xfs_db> freesp -s -e 1000000000 -a 4
from to extents blocks pct
1 268435440 277220 107118347 100.00
total free extents 277220
total free blocks 107118347
average free extent size 386.402
xfs_db>
Is there any way to figure out which files/directories are clogging up
AG 0? Any other ways to abate this issue? Any way to assure
proportional usage of AGs?
Thanks.
-Dave
[-- Attachment #1.2: Type: text/html, Size: 3907 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-03-30 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 18:19 Dave Hall [this message]
2015-03-30 19:45 ` Slightly Urgent: XFS No Space Left On Device Dave Chinner
2015-04-01 19:53 ` Dave Hall
2015-04-02 0:12 ` Dave Chinner
2015-04-02 14:32 ` Dave Hall
2015-04-02 14:36 ` Grozdan
2015-04-02 14:41 ` Grozdan
2015-04-02 22:36 ` 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=551993CF.4060908@binghamton.edu \
--to=kdhall@binghamton.edu \
--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.