All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kumlien <pomac@vapor.com>
To: Chris Ball <cjb@laptop.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [bug] Reclaim space.
Date: Wed, 10 Feb 2010 00:13:49 +0100	[thread overview]
Message-ID: <1265757229.5943.13.camel@pi> (raw)
In-Reply-To: <m3d40e2kdn.fsf@pullcord.laptop.org>

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

On tis, 2010-02-09 at 16:02 -0500, Chris Ball wrote:
> Hi,
> 
>    > Here's a patch to btrfsck from Josef that should fix this:
> 
> Sorry, that was an older patch.  This is the working one:

It didn't apply cleanly to latest git, so i remerged the patch...
The new output sure looks better in my eyes:

/dev/mapper/root      145G  135G   11G  93% /

=)

Thanks, I do wonder btw, btrfsck always seems to segfault when you check
a filesystem in real use - ie loged in users and daemons running - but
not on a normal 'single' user boot. Anything that could be done with
this? (It doesn't inspire confidence ;))

-- 
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-02-09 23:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 18:41 [bug] Reclaim space Ian Kumlien
2010-02-09 20:00 ` Chris Ball
2010-02-09 21:02   ` Chris Ball
2010-02-09 21:05     ` Ian Kumlien
2010-02-09 21:07       ` Chris Ball
2010-02-09 21:13         ` Ian Kumlien
2010-02-09 21:17           ` Chris Ball
2010-02-09 21:48             ` Ian Kumlien
2010-02-09 23:13     ` Ian Kumlien [this message]
2010-02-10 13:16       ` Oystein Viggen

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=1265757229.5943.13.camel@pi \
    --to=pomac@vapor.com \
    --cc=cjb@laptop.org \
    --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.