From: Patrick Schreurs <patrick@news-service.com>
To: linux-xfs@oss.sgi.com
Subject: Re: No space left on device on xfs filesystem with 1.6TB free
Date: Wed, 21 Jan 2009 21:08:52 +0100 [thread overview]
Message-ID: <497780D4.8090004@news-service.com> (raw)
In-Reply-To: <gl7n76$6et$1@ger.gmane.org>
Bryon Roche wrote:
> On Wed, 21 Jan 2009 10:33:10 +0000, Owen Dunn wrote:
>
>> I'm running SuSE Linux Enterprise Server 10 SP2, on a 32-bit i386 Linux
>> machine with kernel version 2.6.16.60-0.33-smp. I appear to have
>> version 2.9.4 of xfsprogs.
>>
>> I have a 6TB xfs filesystem which has been grown twice from 2TB, and
>> which appears to have 1.6TB and plenty of inodes free. However,
>> attempts to create a new file fail with ENOSPC:
> You probably need to mount with inode64 then, to allow xfs to make inodes
> in the later space in the FS.
We've seen this on 64-bit 2.6.23.x and 2.6.27.x kernels with inode64
mounted partitions. xfsprogs 2.8.11 (Debian Etch).
Unfortunately we've never been able to track this down.
Patrick Schreurs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-21 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 10:33 No space left on device on xfs filesystem with 1.6TB free Owen Dunn
2009-01-21 17:49 ` Bryon Roche
2009-01-21 20:08 ` Patrick Schreurs [this message]
[not found] ` <20090121225453.GN10158@disturbed>
2009-01-22 3:09 ` Dave Chinner
2009-01-22 10:25 ` Patrick Schreurs
2009-01-22 17:39 ` Eric Sandeen
2009-01-22 14:15 ` Christian Kujau
2009-01-22 23:25 ` Dave Chinner
2009-01-23 8:21 ` Christian Kujau
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=497780D4.8090004@news-service.com \
--to=patrick@news-service.com \
--cc=linux-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