mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Rada <markrada26@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Zheng Yan <yanzheng@21cn.com>
Subject: Re: Balance taking a lot longer than before
Date: Sat, 20 Mar 2010 01:58:39 -0400	[thread overview]
Message-ID: <0FB2627B-B950-4062-80D5-0BAEC3AF7AB3@gmail.com> (raw)
In-Reply-To: <C514E3D1-A4EB-4460-9994-EBD29CCC6817@gmail.com>

I'm happy to report that defragmenting fixed my problem. In fact, it did a really good job; I had to wrap it to recurse through a few folders I suspected were highly fragmented which took about half an hour run it a few times. Then I tried to rebalance again and not only did it work, but it only took a few hours.

—
Mark Rada
markrada26@gmail.com


On 2010-03-19, at 10:18 AM, Mark Rada wrote:

> 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@gmail.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@uwaterloo.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@uwaterloo.ca
>>> 
>>> 
>>> On 2010-03-18, at 11:19 PM, Yan, Zheng wrote:
>>> 
>>>> On Fri, Mar 19, 2010 at 9:44 AM, Mark Rada <marada@uwaterloo.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.
>>> 
> 


      reply	other threads:[~2010-03-20  5:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <77201DCC-CC67-4B00-8FFE-AAB17A5D18DA@mailservices.uwaterloo.ca>
     [not found] ` <3d0408631003182019i1509d363j98f94661679ea30b@mail.gmail.com>
     [not found]   ` <E9D4D14F-3CAA-487B-8651-97C43CF418B6@mailservices.uwaterloo.ca>
     [not found]     ` <3d0408631003190032s663624c1o528674f8010309f2@mail.gmail.com>
2010-03-19 14:18       ` Mark Rada
2010-03-20  5:58         ` Mark Rada [this message]

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=0FB2627B-B950-4062-80D5-0BAEC3AF7AB3@gmail.com \
    --to=markrada26@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yanzheng@21cn.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

all inboxes | Powered by JetHome®