How to solve "No space left" problem on my 32bit machine?

How to solve "No space left" problem on my 32bit machine?

[hank peng]

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?



-- 
The simplest is not all best but the best is surely the simplest!

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: How to solve "No space left" problem on my 32bit machine?

[Emmanuel Florac]

Le Sun, 26 Jul 2009 11:30:03 +0800 vous écriviez:

> If on my 32-bit machine, what should I do?

2.5TB is far from the 32 bits limit (16 TB). You're probably out of
inodes (lots of small files?). You can add some with xfs_growfs, though.

-- 
--------------------------------------------------
Emmanuel Florac               www.intellique.com   
--------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: How to solve "No space left" problem on my 32bit machine?

[Eric Sandeen]

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.

Be warned though that some applications use 32-bit stat calls still,
rather than 64-bit variants, and you may have some problems.  You should
file bugs against any such applications that you find...

-eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: How to solve "No space left" problem on my 32bit machine?

[hank peng]

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.

> Be warned though that some applications use 32-bit stat calls still,
> rather than 64-bit variants, and you may have some problems.  You should
> file bugs against any such applications that you find...
>
> -eric
>



-- 
The simplest is not all best but the best is surely the simplest!

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: How to solve "No space left" problem on my 32bit machine?

[Eric Sandeen]

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

Re: How to solve "No space left" problem on my 32bit machine?

[hank peng]

2009/7/27 Eric Sandeen <sandeen@sandeen.net>:
> 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.
>
thx, i will try ASAP
> -Eric
>
>



-- 
The simplest is not all best but the best is surely the simplest!

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: How to solve "No space left" problem on my 32bit machine?

[hank peng]

2009/7/27 Eric Sandeen <sandeen@sandeen.net>:
> 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.
>
I tried 2.6.30 and test it
1. create an exact 2T LVM
2. create XFS on it
3. mont it with inode64 option
4. write files on it to full extent
5. use xfs_grow to expand it to 2.5T
6. touch a file and no error message returned
7. 'ls -l' can not show the file I created above.

So I think I should do something on userspace tools, but how?
> -Eric
>
>



-- 
The simplest is not all best but the best is surely the simplest!

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: How to solve "No space left" problem on my 32bit machine?

[Eric Sandeen]

hank peng wrote:
> 2009/7/27 Eric Sandeen <sandeen@sandeen.net>:
>> 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.
>>
> I tried 2.6.30 and test it
> 1. create an exact 2T LVM
> 2. create XFS on it
> 3. mont it with inode64 option
> 4. write files on it to full extent
> 5. use xfs_grow to expand it to 2.5T
> 6. touch a file and no error message returned
> 7. 'ls -l' can not show the file I created above.
> 
> So I think I should do something on userspace tools, but how?

Doesn't sound like a userspace problem.  So touch succeeds (maybe echo
$? after to be sure) but ls shows no file?  Anything in dmesg after that?

I'd have to find a 32-bit box w/ > 2T to test this I guess.  :)

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: How to solve "No space left" problem on my 32bit machine?

[hank peng]

2009/8/4 Eric Sandeen <sandeen@sandeen.net>:
> hank peng wrote:
>> 2009/7/27 Eric Sandeen <sandeen@sandeen.net>:
>>> 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.
>>>
>> I tried 2.6.30 and test it
>> 1. create an exact 2T LVM
>> 2. create XFS on it
>> 3. mont it with inode64 option
>> 4. write files on it to full extent
>> 5. use xfs_grow to expand it to 2.5T
>> 6. touch a file and no error message returned
>> 7. 'ls -l' can not show the file I created above.
>>
>> So I think I should do something on userspace tools, but how?
>
> Doesn't sound like a userspace problem.  So touch succeeds (maybe echo
> $? after to be sure) but ls shows no file?  Anything in dmesg after that?
>
> I'd have to find a 32-bit box w/ > 2T to test this I guess.  :)
>
It is because I use "ls" command in old version of busybox, after I
update busybox to the latest, it is OK now.

I don't check the source code of old version, but i am sure it is the reason.



> -Eric
>



-- 
The simplest is not all best but the best is surely the simplest!

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs