All of lore.kernel.org
 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 08:43:00 +0100	[thread overview]
Message-ID: <BbNQohPi1uB@helmut.hullen.de> (raw)
In-Reply-To: <BbJQ3vED1uB@helmut.hullen.de>

Hallo,

I wrote am 05.12.10:

>>>>>>       devid    2 size 1.35TB used 1.35TB path /dev/sdc3
>>>>>>       devid    1 size 1.81TB used 1.35TB path /dev/sdf2

>>> Here devid 2 is at 100%, and hence you are getting the no more
>>> space left errors. So, the 300 TB is on the bigger disk, and not
>>> usable for you right now.

>>    I _think_ that a balance is all that's needed at this point. It
>> can't hurt, anyway (other than taking quite a long time).

> After running "balance" it looks better:

> Label: 'MM2'  uuid: ad7c0668-316c-4a79-ba00-3b505b9d99b4
> 	Total devices 2 FS bytes used 2.39TB
> 	devid    2 size 1.35TB used 1.20TB path /dev/sdc3
> 	devid    1 size 1.81TB used 1.20TB path /dev/sdf2

And now:

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sdc3            3400799848 2569770888 831028960  76% /srv/MM

But after copying about 300 MByte (part of a 1.5-GByte *.mpg) I got "no  
space left on device". Looks like balancing has stolen about 300 GByte.

Time to buy a 3-TByte disk ...

Viele Gruesse!
Helmut

  reply	other threads:[~2010-12-06  7:43 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 [this message]
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
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=BbNQohPi1uB@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.