hank peng wrote:
> 2009/7/27 Eric Sandeen <sandeen@xxxxxxxxxxx>:
>> hank peng wrote:
>>> 2009/7/27 Eric Sandeen <sandeen@xxxxxxxxxxx>:
>>>> 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
>> commit 6c31b93a14a453c8756ffd228e24910ffdf30c5d
>> Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
>> 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. :)