xfs
[Top] [All Lists]

Re: No space left on device on xfs filesystem with 1.6TB free

To: Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx>
Subject: Re: No space left on device on xfs filesystem with 1.6TB free
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Thu, 22 Jan 2009 11:39:45 -0600
Cc: Owen Dunn <osd1000@xxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <49784989.1000306@xxxxxxxxxxxxxxxx>
References: <alpine.LSU.2.00.0901211007200.19898@xxxxxxxxxxxxxxxxxxxxxx> <20090121225453.GN10158@disturbed> <20090122030955.GT10158@disturbed> <49784989.1000306@xxxxxxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.19 (X11/20090105)
Patrick Schreurs wrote:
> Dave Chinner wrote:
>> You've run out of inode space below 1TB or free space is
>> sufficiently fragmented below 1TB that new inode chunks cannot
>> be allocated.
> 
> Is this related to fs growth or can this happen with any xfs partition?

a grown fs may be more susceptible to it...

xfs dynamically allocates inodes, and inode numbers reflect their
location on disk.

For large-offset disk locations, the inode numbers grow large, and can
be > 32 bits, which causes problems for some applications.

By default xfs keeps inode numbers below 32 bits, and hence restricts
them to the lower part of the filesystem, with data going out towards
the end.

If your fs started out small, more of that low-offset space will be
occupied by data, and be unavailable for inodes even as the filesystem
grows; in short when the fs was small, you used up the space that the
larger fs would have liked to use for inodes.

-Eric

> Thanks,
> 
> Patrick Schreurs

<Prev in Thread] Current Thread [Next in Thread>