From: Dave Chinner <david@fromorbit.com>
To: Michel Verbraak <info1stsetup@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Question about continous blocks for inode due to 'no space left on device' problem
Date: Sat, 6 Feb 2016 09:30:23 +1100 [thread overview]
Message-ID: <20160205223023.GL459@dastard> (raw)
In-Reply-To: <CAAgKQi+AOZO_K9Garmz3G6C1X8TuTRxrfF1MP2HPEZ3JkdE41w@mail.gmail.com>
On Fri, Feb 05, 2016 at 02:13:00PM +0100, Michel Verbraak wrote:
> All,
>
> Recently we ran into a problem where our filesystem (300GB in size)
> reported 'no space left on device' (ENOSPC) but when we looked at disk
> space usage and inode usage it was around 52% for disk space and 11% for
> inode. (sorry do not have a save of the output of df command).
....
> meta-data=/dev/sdb isize=256 agcount=6, agsize=19660800
Inode allocation requires aligned 16k extents.
......
> Some extra info about the system and files on the system:
> - Ubuntu 12.04.5 LTS
> - Kernel: Linux ealxs00170 3.2.0-97-generic #137-Ubuntu SMP Thu Dec 17
> 18:11:47 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> - 32 million files of which about 75% is smaller than 1k. Files are
> separated over different folders to keep the number of files per folder low.
You have lots of small single block files which will cause free
space to tend towards small extents as the filesystem fills up...
> - mount options: defaults,noatime,inode64,nobarrier
>
> Regards,
>
> Michel Verbraak.
>
> Store 03 (root@server):~# xfs_db -c freesp /dev/sdb
> from to extents blocks pct
> 1 1 3282633 3282633 9.03
> 2 3 3416223 8372325 23.03
> 4 7 6175009 24700036 67.94
Yup, no more aligned 4 block extents in the filesystem.
This is what the experimental sparse inode feature in current
kernels addresses - it allows unaligned block allocation for inodes
and so allows you to abuse the filesystem all the way up to 100%
full with workloads like this.
But without moving to a current 4.4 kernel and reformatting all your
filesystems, there's absolutely nothing you can do about it except
grow the filesystem to be larger every time you drive the filesystem
into this condition.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-02-05 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 13:13 Question about continous blocks for inode due to 'no space left on device' problem Michel Verbraak
2016-02-05 22:30 ` Dave Chinner [this message]
2016-02-08 13:09 ` Michel Verbraak
2016-02-08 14:35 ` Brian Foster
2016-02-08 15:13 ` Michel Verbraak
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=20160205223023.GL459@dastard \
--to=david@fromorbit.com \
--cc=info1stsetup@gmail.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