Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@redhat.com>
To: "Martin Bürger" <mbuerger@edu.uni-klu.ac.at>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: space info full
Date: Mon, 6 Oct 2008 14:27:24 -0400	[thread overview]
Message-ID: <20081006182723.GB2840@unused.rdu.redhat.com> (raw)
In-Reply-To: <200810040945.56118.mbuerger@edu.uni-klu.ac.at>

On Sat, Oct 04, 2008 at 09:45:55AM +0200, Martin B=FCrger wrote:
> Hello,
> 'space info full' was the only message I got from dmesg. df reports:
>

space info full doesn't mean the disk is full, just means we've allocat=
ed all of
the block group chunks that the filesystem can hold, so you will get th=
at
message well before you actually run out of disk space.  As it stands n=
ow btrfs
has a short circuit when you hit ~15% free to go ahead an ENOSPC to avo=
id
hitting the many BUG()'s that are sitting around to handle ENOSPC.
=20
> /dev/sdb1             33551720  28504548   5047172 =20
> 85% /mnt/btrfstest
>=20
> df -i reports:
> /dev/sdb1                  0       0       0    -  /mnt/btrfstest
>=20
> Any (e.g., touch, rm) operation on that mounted filesystem lets the=20
> CPU rise and the system hang...
>

are you running the latest git trees of both btrfs-unstable and
btrfs-progs-unstable?  I'd expect BUG()'s or something like that, shoul=
dn't be
getting hangs.  Thanks,

Josef=20
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-10-06 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-04  7:45 space info full Martin Bürger
2008-10-04 12:17 ` Yan Zheng
2008-10-06 18:27 ` Josef Bacik [this message]
2008-10-06 20:28   ` Martin Bürger

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=20081006182723.GB2840@unused.rdu.redhat.com \
    --to=jbacik@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mbuerger@edu.uni-klu.ac.at \
    /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