xfs
[Top] [All Lists]

Re: Premature "No Space left on device" on XFS

To: xfs@xxxxxxxxxxx
Subject: Re: Premature "No Space left on device" on XFS
From: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Fri, 7 Oct 2011 13:40:24 +0200
In-reply-to: <20111007013711.GW3159@dastard>
Organization: it-management http://it-management.at
References: <4E8E079B.4040103@xxxxxxxxxxxxx> <20111007013711.GW3159@dastard>
User-agent: KMail/1.13.6 (Linux/3.0.3-zmi; KDE/4.6.0; x86_64; ; )
On Freitag, 7. Oktober 2011 Dave Chinner wrote:
> And with 1.7 million inodes in it. That's a lot for a tiny
> filesystem, and not really a use case that XFS is well suited to.
> XFS will work, but it won't age gracefully under these conditions...

But which FS would fit better for that? We have similar usages, so I'm 
curious.

> As it is, your problem is most likely fragmented free space (an
> aging problem). Inodes are allocated in chunks of 64, so require an
> -aligned- contiguous 16k extent for the default 256 byte inode size.
> If you have no aligned contiguous 16k extents free then inode
> allocation will fail.

Would this be a use case for the "noikeep" mount option?

When would be the time XFS drops inode clusters that are already empty, 
when I use noikeep on an aged XFS with lots of such unused inode 
allocations?

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

// Haus zu verkaufen: http://zmi.at/langegg/

Attachment: signature.asc
Description: This is a digitally signed message part.

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