linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Mark Marshall <markmarshall8@gmail.com>
Subject: Re: no space left on device
Date: Sat, 4 Aug 2012 11:26:12 +0200	[thread overview]
Message-ID: <201208041126.12533.Martin@lichtvoll.de> (raw)
In-Reply-To: <CAEuwOw4sABKXS3oJpFZPq9xpbbuNxZeTRN7UUQBjcGkiHCAqeQ@mail.gmail.com>

Am Freitag, 3. August 2012 schrieb Mark Marshall:
> Hi,

Hi Mark,

> I am new to btrfs, and just installed a new system with SLED 11 SP2 a
> few days ago.

Now you have a nice SLED 11 SP 2 with official BTRFS support from SUSE. 
Did you consider to ask SUSE support? ;)

> However the system seems to be in a real sad state now, saying there
> is no free space left on the device even though there is about 8GB
> left on the / filesystem.
> 
> A defragment works sometimes but then it goes back to the original
> state a day or two later. Other times the command just won't respond.
> 
> I've had this happen with 2-3 systems now, is there a solution? I
> can't keep going around to users machines and defragmenting all the
> time !

First read and understand

https://btrfs.wiki.kernel.org/index.php/FAQ#Aaargh.21_My_filesystem_is_full.2C_and_I.27ve_put_almost_nothing_into_it.21

plus the following FAQs in there.

Then come back with more information.

Possible a btrfs balance will work to make some trees smaller, but this 
depends on the current state of your BTRFS. The information you provided 
is not nearly enough for an exact diagnosis. A defragment likely won´t 
help tough.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  parent reply	other threads:[~2012-08-04  9:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 10:05 no space left on device Mark Marshall
2012-08-04  9:14 ` Chris Samuel
2012-08-04  9:26 ` Martin Steigerwald [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-12  9:51 No " Jakob Truelsen
2014-02-12 10:26 ` Hugo Mills
2014-02-12 10:45   ` Jakob Truelsen
2014-02-12 11:07     ` Hugo Mills
2014-02-12 10:34 ` Leonidas Spyropoulos
2012-11-01 13:35 no " Kenneth Johansson
2012-11-02 15:54 ` Kyle Gates
2012-11-02 15:59   ` Hugo Mills
2012-11-06 13:23   ` Kenneth Johansson
     [not found] <AANLkTinH225vC8fRbA7zk_iOEmyADFZMBS6b7gx1tOxm@mail.gmail.com>
2011-02-08  9:00 ` Leonidas Spyropoulos
2011-02-08  9:31   ` cwillu
2011-02-08 10:08     ` Leonidas Spyropoulos
2011-02-08 13:19       ` Helmut Hullen
2011-02-08 18:56         ` Erik Logtenberg
2011-02-08 19:43           ` Helmut Hullen
2011-02-12 14:11             ` Erik Logtenberg
2011-02-08 20:36           ` Helmut Hullen
2011-02-07 21:21 Leonidas Spyropoulos
2011-02-07 21:27 ` Erik Logtenberg
2011-02-07 23:58   ` Robert G.
2011-02-08  0:09 ` C Anthony Risinger
2010-07-30  5:31 Lubos Kolouch
     [not found] ` <AANLkTikBRfR45DZxZW9LM6wnREWrbysPCr9Z1d3YuYhC@mail.gmail.com>
2010-07-30 12:27   ` Lubos Kolouch
     [not found]     ` <AANLkTinBj1O-LapAeBCT2Y3A1ZhfFZ3AotCk6SZ-e-2U@mail.gmail.com>
2010-07-30 14:30       ` Leonidas Spyropoulos
2010-07-30 15:02         ` Lubos Kolouch
2010-07-30 15:09           ` Lubos Kolouch
2010-08-14 20:15             ` Lubos Kolouch
2008-12-08  9:46 No " Gabor MICSKO
2008-12-08 14:02 ` dcg

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=201208041126.12533.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=markmarshall8@gmail.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;
as well as URLs for NNTP newsgroup(s).