linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Tommy Faasen <tommy@zwanebloem.nl>
Cc: cwillu <cwillu@cwillu.com>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs out of inodes becomes corrupt
Date: Wed, 8 Feb 2012 11:13:25 +0000	[thread overview]
Message-ID: <20120208111325.GA19900@carfax.org.uk> (raw)
In-Reply-To: <20120206153514.GB8542@zwanebloem.nl>

[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]

On Mon, Feb 06, 2012 at 03:35:14PM +0000, Tommy Faasen wrote:
> I rolled a new kernel 3.2.4 and it picked everything up.
> No crashes, my disk was still full, with 40+ gigs free
> but now I can delete files and access them.
> 
> I'm running btrfs fi balance /mountpoint at the moment which I understand frees up the remaining space.

   Well, not quite. It has a side-effect that if you have an
over-allocation of space to one or other of data/metadata, it will
serve to reduce that allocation, giving back the over-allocated space
to the free pool, from where it can be reallocated by the other group
type.

   So if you have, say 5G allocated for metadata, but only 500M used,
you could gain back a large amount (but probably not all) of the
unused 4.5G by running a balance.

   Hugo.

> Thanks again for your assistance!
> 
> Tommy
> 
> On Mon, Feb 06, 2012 at 11:40:31AM +0000, Hugo Mills wrote:
> > On Mon, Feb 06, 2012 at 05:33:51AM -0600, cwillu wrote:
> > > >  3.0 is two revisions old -- something on the order of 6
> > > > months. There's been a lot of development since then, too. You really
> > > > should be running 3.2 or 3.2-rc2 (i.e. the latest released or latest
> > > > development version of the kernel).
> > > 
> > > I think you meant 3.2 or 3.3-rc2.
> > 
> >    I did indeed. Thanks for the correction.
> > 
> >    Hugo.
> > 

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
         --- Quantum Mechanics: the dreams stuff is made of. ---         

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2012-02-08 11:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05 19:18 Btrfs out of inodes becomes corrupt Tommy Faasen
2012-02-05 19:57 ` Hugo Mills
2012-02-06 11:33   ` cwillu
2012-02-06 11:40     ` Hugo Mills
2012-02-06 15:35       ` Tommy Faasen
2012-02-08 11:13         ` Hugo Mills [this message]
2012-02-08  6:41   ` Chris Samuel
2012-02-08  9:00     ` Felix Blanke

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=20120208111325.GA19900@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=cwillu@cwillu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tommy@zwanebloem.nl \
    /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).