[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <C514E3D1-A4EB-4460-9994-EBD29CCC6817@gmail.com>
Date: Fri, 19 Mar 2010 10:18:12 -0400
From: Mark Rada <markrada26@...il.com>
To: "Yan, Zheng" <yanzheng@...n.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: Balance taking a lot longer than before
I don't have any files bigger than 5GB, and I'm using less than a quarter of my total disk space but I already have a lot of fragmentation?
Defragmenting won't help, will it? Is there anything I can do other than deleting the files?
—
Mark Rada
markrada26@...il.com
On 2010-03-19, at 3:32 AM, Yan, Zheng wrote:
> The loop is caused by fragmentaion of free space. Balance code is trying to
> relocate a large file extent, but it can't find a free space that is
> large enough.
>
> On Fri, Mar 19, 2010 at 11:28 AM, Mark Rada <marada@...terloo.ca> wrote:
>> Hmm, there seems to be a very very long list of "btrfs: found 1 extents" messages and nothing else in between them.
>>
>> Why would deleting large files help? I don't want to delete files on my server unless I have no other option.
>>
>> —
>> Mark Rada
>> marada@...terloo.ca
>>
>>
>> On 2010-03-18, at 11:19 PM, Yan, Zheng wrote:
>>
>>> On Fri, Mar 19, 2010 at 9:44 AM, Mark Rada <marada@...terloo.ca> wrote:
>>>> Hi devs,
>>>>
>>>> I've been using btrfs on my file server since 2.6.32 and after upgrading to .33 I noticed that rebalancing took way longer than before.
>>>>
>>>> I have a 5 disk array used for a btrfs md setup, different hard drive sizes, brands, and interfaces.
>>>>
>>>> The last time I rebalanced I was using about 800GB of space on the 4.6TB array, and I started before I went to sleep and it was done when I woke up.
>>>>
>>>> I'm in the middle of a rebalance right now, currently using 950GB, and it has been a full day and the rebalancing is not done yet. Is this an expected change? Is there any way to tell how much longer it will take? Do you need to know more info about the setup?
>>>>
>>>
>>> I guess it enters infinite loops. you can check it by checking if
>>> there are a lots of
>>> repeats messages in the kernel log. If it is true, you can try
>>> deleting some large
>>> files in that FS.
>>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists