From: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: hold enough space for global_rsv
Date: Thu, 8 Mar 2012 20:22:25 +0100 [thread overview]
Message-ID: <20120308202225.01ad2ffd@fem.tu-ilmenau.de> (raw)
In-Reply-To: <20120306145032.697641a3@fem.tu-ilmenau.de>
Am Tue, 6 Mar 2012 14:50:32 +0100
schrieb Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>:
> I've backed up the filesystem, deleted the subvolumes, recreated them
> and copied the data back. Now everything seems to work again. I've
> also a full image of the damaged filesystem for further
> investigation. If someone has an idea for testing, I'm happy to try
> it.
It's much worse than I thought. After a short time the same error
happened again (no space left on device). So recreated the filesystem
(mkbtrfs with default values) and copied the data from the backup back,
but the error still came back. I'm now on kernel 3.2 which seems to
work. I'll try to bisect the bad commit. For info, df says:
Filesystem Size Used Avail Use% Mounted on
rootfs 200G 128G 69G 66% /
/dev/sda1 200G 128G 69G 66% /
rc-svcdir 1.0M 128K 896K 13% /lib64/rc/init.d
cgroup_root 10M 52K 10M 1% /sys/fs/cgroup
udev 10M 168K 9.9M 2% /dev
shm 2.0G 0 2.0G 0% /dev/shm
/dev/sda1 200G 128G 69G 66% /home
and btrfs fi df:
Data: total=149.01GB, used=118.57GB
System, DUP: total=8.00MB, used=24.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=6.38GB, used=4.55GB
Metadata: total=8.00MB, used=0.0
Kernel 3.3-rc6 fails on this with "no space left on device".
next prev parent reply other threads:[~2012-03-08 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 9:51 [PATCH] Btrfs: hold enough space for global_rsv Liu Bo
2012-01-27 15:25 ` Chris Mason
2012-02-27 13:29 ` Johannes Hirte
2012-02-28 2:06 ` Liu Bo
2012-03-06 13:50 ` Johannes Hirte
2012-03-08 19:22 ` Johannes Hirte [this message]
2012-03-09 1:28 ` Liu Bo
2012-03-10 20:12 ` Johannes Hirte
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=20120308202225.01ad2ffd@fem.tu-ilmenau.de \
--to=johannes.hirte@fem.tu-ilmenau.de \
--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 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).