public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Sander van Schie / True <Sander.vanSchie@true.nl>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: Issue with "no space left on device"
Date: Thu, 17 Aug 2017 12:47:52 -0400	[thread overview]
Message-ID: <20170817164751.GA62570@bfoster.bfoster> (raw)
In-Reply-To: <1502981688167.22881@true.nl>

On Thu, Aug 17, 2017 at 02:54:48PM +0000, Sander van Schie / True wrote:
> Hello,
> 
> I have a 35 GB XFS partition with both plenty of free space and inodes, but I'm still getting the error "No space left on device" when trying to create new files.
> 
> Mount options:
> 
> # mount | grep vdc1
> /dev/vdc1 on /mnt type xfs (rw,relatime,attr2,inode64,noquota)
> 
> Used disk space:
> 
> # df /dev/vdc1
> Filesystem     1K-blocks     Used Available Use% Mounted on
> /dev/vdc1       36681200 16066576  20614624  44% /mnt
> 
> Used inodes:
> 
> # df -i /dev/vdc1
> Filesystem     Inodes  IUsed  IFree IUse% Mounted on
> /dev/vdc1      917440 199616 717824   22% /mnt
> 
> xfs info:
> 
> # xfs_info /dev/vdc1
> meta-data=/dev/vdc1              isize=2048   agcount=4, agsize=2293695 blks

With 2k sized inodes, the most likely cause is free space fragmentation.
What does 'xfs_db -c "freesp -s" <dev>' print for this fs?

Brian

>          =                       sectsz=512   attr=2, projid32bit=1
>          =                       crc=1        finobt=1 spinodes=0
> data     =                       bsize=4096   blocks=9174779, imaxpct=5
>          =                       sunit=0      swidth=0 blks
> naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
> log      =internal               bsize=4096   blocks=4479, version=2
>          =                       sectsz=512   sunit=0 blks, lazy-count=1
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> 
> 
> I've already tried repairing and rebooting, which unfortunately didn't help.
> 
> Any idea what's wrong?
> 
> Thanks!
> 
> - Sander--
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-08-17 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 14:54 Issue with "no space left on device" Sander van Schie / True
2017-08-17 16:47 ` Brian Foster [this message]
2017-08-17 17:15   ` Sander van Schie
2017-08-17 17:45     ` Eric Sandeen
2017-08-17 20:11       ` Sander van Schie
2017-08-17 21:21         ` Eric Sandeen
2017-08-17 21:28           ` Eric Sandeen
2017-08-17 21:44             ` Sander van Schie

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=20170817164751.GA62570@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=Sander.vanSchie@true.nl \
    --cc=linux-xfs@vger.kernel.org \
    /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