linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: 800 GByte free, but "no space left"
Date: 06 Dec 2010 15:45:00 +0100	[thread overview]
Message-ID: <BbNRoIAi1uB@helmut.hullen.de> (raw)
In-Reply-To: <20101206132817.GD4273@carfax.org.uk>

Hallo, Hugo,

Du meintest am 06.12.10:

>>>    Can you try that again with either the latest 2.6.37-rc, or with
>>> the btrfs-unstable kernel? There's a bug in earlier versions that
>>> breaks the reporting of RAID types, which is what I wanted to see
>>> here.

>> Compiling 2.6.37-rc is no big problem, it only needs som time.

Compiling runs ..

>>>> And I don't dare running "balance" again - maybe it reduces the
>>>> available space again and again.

>>>    If you've hit the bug I think you have, then yes, it will.

>> Hmm - it can't get worse ...
>> If the error is related to the kernel or to the btrfs version and I
>> try a newer one: can that lead to more free space?

>    Not yet. I've taken the whole of December off work (using up my
> leave allocation for last year), and my plan is to get myself to the
> point where I can understand enough of the code to fix this
> particular problem.

I love such vacancies planning ...

If/when I install 2.6.37-rc4: should I update btrfs (from the 20101117  
version)?

How can I see that changing the kernel makes things better? It's more  
and more difficult to externalize (?) btrfs directories to other disks  
...

Viele Gruesse!
Helmut

  reply	other threads:[~2010-12-06 14:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimJ3dDdOFiQb8G=rrjCk2h68Y59oWdKEGH-80jN@mail.gmail.com>
2010-12-05  7:48 ` 800 GByte free, but "no space left" Helmut Hullen
2010-12-05  8:59   ` cwillu
2010-12-05  9:51     ` Helmut Hullen
2010-12-05 10:36       ` cwillu
2010-12-05 11:46         ` Helmut Hullen
2010-12-05 11:08   ` Evert Vorster
2010-12-05 11:22     ` Hugo Mills
2010-12-05 12:21       ` Helmut Hullen
2010-12-05 13:49       ` Evert Vorster
2010-12-05 14:33         ` Helmut Hullen
2010-12-05 18:00           ` Evert Vorster
2010-12-05 18:26             ` Helmut Hullen
2010-12-06  9:56               ` Brian Rogers
2010-12-06 11:41                 ` Hugo Mills
2010-12-05 20:28       ` Helmut Hullen
2010-12-06  7:43         ` Helmut Hullen
2010-12-06 11:43           ` Hugo Mills
2010-12-06 12:42             ` Helmut Hullen
2010-12-06 12:48               ` Hugo Mills
2010-12-06 13:13                 ` Helmut Hullen
2010-12-06 13:28                   ` Hugo Mills
2010-12-06 14:45                     ` Helmut Hullen [this message]
2010-12-06 15:18                       ` Hugo Mills
2010-12-06 17:13                         ` Helmut Hullen
2010-12-06 18:29                           ` Hugo Mills
2010-12-07 17:05                             ` Helmut Hullen
2010-12-07 17:25                               ` Hugo Mills
2010-12-07 17:44                                 ` Helmut Hullen
2010-12-05 11:35     ` Helmut Hullen
2010-12-02 18:23 Helmut Hullen
2010-12-03  3:28 ` Mike Fedyk
2010-12-03  6:47   ` Helmut Hullen
2010-12-04 17:17 ` Helmut Hullen

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=BbNRoIAi1uB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.de \
    --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).