From: David Chinner <dgc@sgi.com>
To: "Huszár Viktor Dénes" <hvd@dwo.hu>
Cc: 'Emmanuel Florac' <eflorac@intellique.com>, xfs@oss.sgi.com
Subject: Re: free space problem
Date: Tue, 1 Apr 2008 10:35:18 +1000 [thread overview]
Message-ID: <20080401003518.GK103491721@sgi.com> (raw)
In-Reply-To: <20080331173724.24BB68D1DF4@cuda.sgi.com>
On Mon, Mar 31, 2008 at 07:36:56PM +0200, Huszár Viktor Dénes wrote:
> -----Original Message-----
> From: Emmanuel Florac [mailto:eflorac@intellique.com]
> Sent: Monday, March 31, 2008 9:40 AM
> To: Huszár Viktor Dénes; xfs@oss.sgi.com
> Subject: Re: free space problem
>
> Le Mon, 31 Mar 2008 02:31:16 +0200 vous écriviez:
>
> >Then maybe you simply ran out of inodes. It's common if you have lots
> >of small files. There is a way to increase the number of inodes but I
> >don't remember it right now.
> --
> No, unfortunately not. There are not many small files and the inode usage is
> 1%. See.
Yes, but if you have fragemented free space then it is possible that there
are not enough free extents large enough (or aligned correctly) to
allocate more inodes. The number of "free inodes" reported doesn't take
this into account; it only looks at the number of free blocks and converts
that to a theoretical number of inodes that could be allocated in that
space (i.e. it assumes perfect fit and no waste).
In this "not quite full filesystem" situation, you can write data to the
filesystem, but any attempt to create a new inode (new file, directory,
etc) will fail with ENOSPC. This sounds like the symptoms you are
reporting....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-04-01 0:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080331093951.100ec125@galadriel.home>
2008-03-31 17:36 ` free space problem Huszár Viktor Dénes
2008-04-01 0:35 ` David Chinner [this message]
2008-04-01 3:08 ` Huszár Viktor Dénes
2008-04-06 16:09 ` Huszár Viktor Dénes
2008-04-06 16:26 ` KELEMEN Peter
2008-04-06 16:38 ` Huszár Viktor Dénes
2008-04-07 2:18 ` David Chinner
2008-05-29 10:20 ` Huszár Viktor Dénes
2008-05-29 10:29 ` Emmanuel Florac
2008-05-29 10:55 ` Emmanuel Florac
2008-05-29 13:26 ` Huszár Viktor Dénes
2008-05-29 14:57 ` Dave Chinner
2008-05-29 17:37 ` Huszár Viktor Dénes
[not found] ` <20080529132624.19286105D9@mailwash5.pair.com>
2008-05-29 13:30 ` Emmanuel Florac
2008-03-30 20:29 Huszár Viktor Dénes
2008-03-30 21:54 ` Emmanuel Florac
2008-03-31 0:31 ` Huszár Viktor Dénes
2008-03-31 0:38 ` David Chinner
2008-03-31 17:43 ` Huszár Viktor Dénes
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=20080401003518.GK103491721@sgi.com \
--to=dgc@sgi.com \
--cc=eflorac@intellique.com \
--cc=hvd@dwo.hu \
--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