All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Samuel Granjeaud <samuel.granjeaud@inserm.fr>
Cc: xfs@oss.sgi.com
Subject: Re: Run out of inodes?
Date: Fri, 29 Aug 2014 07:48:06 -0400	[thread overview]
Message-ID: <20140829114806.GA17610@bfoster.bfoster> (raw)
In-Reply-To: <54005108.1020203@inserm.fr>

On Fri, Aug 29, 2014 at 12:08:08PM +0200, Samuel Granjeaud wrote:
> Hi,
> 
> Sorry if the answer is obvious, but I didn't find any clear answer after
> googling.
> 
> I have a XFS system of 18T over LVM. Recently, I could not create new files
> or directories.
> 
> # mkdir tempo
> mkdir: cannot create directory `tempo': No space left on device
> 
> After deleting a few files, this command runs successfully.
> 
> So I think that the system runs out of something, inodes I guess.
> 
> But the df diagnosis does not enlight it: only 1% used.
> 
> # df -ht xfs
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/mapper/vg1_backup-backup
>                        18T   12T  6.6T  63% /mnt/vg1_backup/backup
> # df -it xfs
> Filesystem            Inodes   IUsed   IFree IUse% Mounted on
> /dev/mapper/vg1_backup-backup
>                      18874040320  530042 18873510278    1%
> /mnt/vg1_backup/backup
> 
> So what is wrong? How should I solve the problem?
> 
> I read about xfs_grow -m, but I am not sure if it could help.
> Of course, I rebooted the system before my trials.
> 

You should probably include more information for context:

http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F

That aside... is inode64 enabled? Is imaxpct set to a non-default value?
Also, how is this filesystem used? I notice it's named as some kind of
backup volume.

Brian

> Best regards,
> Samuel
> 
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

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

  parent reply	other threads:[~2014-08-29 11:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 10:08 Run out of inodes? Samuel Granjeaud
2014-08-29 11:43 ` Emmanuel Florac
2014-08-29 11:48 ` Brian Foster [this message]
2014-08-29 13:29   ` Samuel Granjeaud
2014-08-29 15:02     ` Eric Sandeen
2014-08-29 15:22       ` Samuel Granjeaud
2014-08-30 19:33       ` Samuel GRANJEAUD IR/INSERM
2014-08-31  2:46         ` Eric Sandeen
2014-09-01 19:19         ` Emmanuel Florac
2014-09-02  7:22           ` Samuel Granjeaud

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=20140829114806.GA17610@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=samuel.granjeaud@inserm.fr \
    --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.