From: Eric Sandeen <sandeen@sandeen.net>
To: hank peng <pengxihan@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: How to solve "No space left" problem on my 32bit machine?
Date: Mon, 27 Jul 2009 08:40:45 -0500 [thread overview]
Message-ID: <4A6DAE5D.6060704@sandeen.net> (raw)
In-Reply-To: <389deec70907262347g1ca3637fn469596ec1e05148@mail.gmail.com>
hank peng wrote:
> 2009/7/27 Eric Sandeen <sandeen@sandeen.net>:
>> hank peng wrote:
>>> Hi, folks:
>>> I have a 2.5T file system formatted with XFS, df tells me it still
>>> have about 10G space available, but I can't create new files or
>>> directory any more. Return message is "No space left on this device".
>>> I searched solution for this problem through google, and found this:
>>> http://oss.sgi.com/archives/xfs/2005-06/msg00347.html. I think it is a
>>> known "No space left" problem. I wonder whether it can only
>>> be solved on 64-bit machine? If on my 32-bit machine, what should I do?
>> On very recent kernels you can use 64-bit inodes on 32-bit machines; you
>> can try mounting with -o inode64 t allow this.
>>
> I tried -o inode64 option, but kernel gives me error message:
> XFS: inode64 option not allowed on this system
> I doubt this option can't be used on 32-bit machine.
That's why I said you need a very recent kernel, it was added relatively
recently:
commit 6c31b93a14a453c8756ffd228e24910ffdf30c5d
Author: Christoph Hellwig <hch@infradead.org>
Date: Fri Nov 28 14:23:32 2008 +1100
[XFS] allow inode64 mount option on 32 bit systems
I believe this went into 2.6.29.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-27 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 3:30 How to solve "No space left" problem on my 32bit machine? hank peng
2009-07-26 15:39 ` Emmanuel Florac
2009-07-27 1:48 ` Eric Sandeen
2009-07-27 6:47 ` hank peng
2009-07-27 13:40 ` Eric Sandeen [this message]
2009-07-27 15:48 ` hank peng
2009-08-03 14:32 ` hank peng
2009-08-03 18:55 ` Eric Sandeen
2009-08-06 8:47 ` hank peng
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=4A6DAE5D.6060704@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@oss.sgi.com \
--cc=pengxihan@gmail.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