[Ocfs2-users] No space left on device
Alexander Barton
alex at barton.de
Wed Sep 8 08:56:27 PDT 2010
Hi Tao!
Am 08.09.2010 um 16:22 schrieb Tao Ma:
> Hi,
>
> Alexander Barton wrote:
>
>> Hi Tao!
>>
>> Am 08.09.2010 um 10:53 schrieb Tao Ma:
>>
>>> Hi all
>>>
>>> On 09/08/2010 04:11 PM, Alexander Barton wrote:
>>>
>>>> Hi Sunil!
>>>>
>>>> Are there special steps one has to follow to recover such a filesystem that has been used with a buggy kernel?
>>>>
>>>> We had this problem with a Debian 2.6.27 kernel and updated to a recent „mainline“ kernel 2.6.33.x – but are still seeing the same problem: „no space left“ is reported when trying to write files to the filesystem (a few megabytes are often „too much“) although df(1) shows a lot (gigabytes) of free space.
>>>>
>>>> - Kernel 2.6.33-2-amd64 (2.6.33-1~experimental.4)
>>>> - OCFS2 Tools 1.4.3-1
>>
>>>
>>> Discontig block group is added in the last development cycle which mean 2.6.35 IIRC.
>>>
>>> As for the tools part, I have added the patches to the mail list and there is still one patch waiting for review.
>>>
>>>> Any hints?
>>>> Do you need more information?
>>
>>>
>>> yes, we have to make sure you meet with discontig block group problem if we have your stat_sysdir output.
>>
>>
>> It is about 275 KBytes, so I uploaded it here:
>> <http://gist.github.com/569970>
>>
>
> Does it happen now?
No. We deleted „lots“ of small cache files and are currently able to write to the filesystem.
> Your volume seems to have the similar problem, a large number of groups has small
> contiguous spaces that can't be used to allocate an inode.
> So do please wait for the patch for the ocfs2-tools to be included and the mainline kernel of 2.6.35.
Ok, thanks a lot for your answer!
Regards
Alex
More information about the Ocfs2-users
mailing list