Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Yan Zheng <ukernel@gmail.com>
To: "Martin Bürger" <mbuerger@edu.uni-klu.ac.at>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: space info full
Date: Sat, 04 Oct 2008 20:17:23 +0800	[thread overview]
Message-ID: <48E75ED3.1000404@gmail.com> (raw)
In-Reply-To: <200810040945.56118.mbuerger@edu.uni-klu.ac.at>

Martin B=C3=BCrger wrote:
> Hello,
> 'space info full' was the only message I got from dmesg. df reports:
>=20
> /dev/sdb1             33551720  28504548   5047172 =20
> 85% /mnt/btrfstest

The output of df can be inaccurate. Although df shows the FS is 85% ful=
l,
It's possible the FS is completely full.

>=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...

btrfs can't properly handle disk full condition currently. ENOSPC can
result in BUG()

>=20
> I was filling up the partition with compilebench to the ration=20
> mentioned above. During this process I tried to create a subvolume=20
> with
> 	btrfsctl -s sub_vol /mnt/btrfstest
> which did not, as opposed to the advices from the INSTALL file,=20
> create anything within /mnt/btrfstest.

Please try mount the FS with -o subvol=3D. option, you will see the new
subvol.

Regards
Yan Zheng
--
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

  reply	other threads:[~2008-10-04 12:17 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 [this message]
2008-10-06 18:27 ` Josef Bacik
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=48E75ED3.1000404@gmail.com \
    --to=ukernel@gmail.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