linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Logtenberg <erik@logtenberg.eu>
To: linux-btrfs@vger.kernel.org
Subject: Re: Kernel error during btrfs balance
Date: Tue, 18 Jan 2011 14:22:51 +0100	[thread overview]
Message-ID: <4D35942B.2020601@logtenberg.eu> (raw)
In-Reply-To: <AANLkTikhU0N+zTWmZ-og43fDGEsaxsAV7fAeAqutyF_t@mail.gmail.com>

On 01/18/2011 01:54 AM, Yan, Zheng wrote:
> On Mon, Jan 17, 2011 at 10:14 PM, Erik Logtenberg <erik@logtenberg.eu> wrote:
>> Hi,
>>
>> btrfs balance results in:
>>
>> http://pastebin.com/v5j0809M
>>
>> My system: fully up-to-date Fedora 14 with rawhide kernel to make btrfs
>> balance do useful stuff to my free space:
>>
>> kernel-2.6.37-2.fc15.x86_64
>> btrfs-progs-0.19-12.fc14.x86_64
>>
>> Filesystem had 0 bytes free, should be 45G, so on darklings advice I ran
>> btrfs balance on the fs, while doing heavy I/O (re-running 5 backup jobs
>> that had failed due to ENOSP).
>> Up until the crash, btrfs balance did retrieve a couple of Gigs free
>> space though, so that part of the plan worked just fine.
>>
> 
> Please try 2.6.36 kernel.

Thanks for your (short) advice. Could you please elaborate. I was in
fact using a 2.6.35.10-74.fc14.x86_64 kernel before, but darkling
adviced me to switch to a newer kernel to reclaim free space by
balancing -- the idea was that newer kernels have better balancing
implementation, more effective at reclaiming free space.

Now your advice is to take a small step back again, from 2.6.37 to
2.6.36 (which is still higher than the 2.6.35 I was using before). Is
that because you think that 2.6.37 may have introduced the bug that I
ran into? Do you think that 2.6.36 is still recent enough to have the
effective balancing so that I will in fact be able to reclaim some free
space? Or is is just a shot in the dark with no reasoning whatsoever ;)

Please don't feel offended, but from your 4-word sentence I really can't
tell.

Thanks,

Erik.

  reply	other threads:[~2011-01-18 13:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 14:14 Kernel error during btrfs balance Erik Logtenberg
2011-01-17 14:31 ` Erik Logtenberg
2011-01-17 14:37   ` Erik Logtenberg
2011-01-17 14:39     ` Erik Logtenberg
2011-01-21  8:50   ` Erik Logtenberg
2011-01-21  9:19     ` Yan, Zheng 
2011-01-26  9:04       ` Erik Logtenberg
2011-01-26  9:27         ` Hugo Mills
2011-01-26  9:40           ` Helmut Hullen
2011-01-26  9:46             ` Erik Logtenberg
2011-01-29 10:56             ` Chris Samuel
2011-01-26  9:43           ` Erik Logtenberg
2011-01-18  0:54 ` Yan, Zheng 
2011-01-18 13:22   ` Erik Logtenberg [this message]
2011-01-18 13:58     ` Helmut Hullen
2011-01-18 14:13     ` Yan, Zheng 
2011-01-18 14:29       ` Erik Logtenberg

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=4D35942B.2020601@logtenberg.eu \
    --to=erik@logtenberg.eu \
    --cc=linux-btrfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).