From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Creating backup snapshots (8 per filesystem) causes No space left on device?
Date: Sun, 15 Apr 2012 08:07:41 -0700 [thread overview]
Message-ID: <20120415150740.GA10248@merlins.org> (raw)
Howdy,
I have a little script that creates hourly/daily/weekly snapshots on a device that
otherwise has plenty of disk space free:
gandalfthegreat:~# df -h | grep cryptroot
/dev/mapper/cryptroot 232G 144G 85G 63% /
/dev/mapper/cryptroot 232G 144G 85G 63% /usr
/dev/mapper/cryptroot 232G 144G 85G 63% /var
/dev/mapper/cryptroot 232G 144G 85G 63% /home
/dev/mapper/cryptroot 232G 144G 85G 63% /tmp
/dev/mapper/cryptroot 232G 144G 85G 63% /mnt/btrfs_pool1
I have kernel 3.3.1.
The FAQ of course talks about the topic:
https://btrfs.wiki.kernel.org/articles/f/a/q/FAQ_1fe9.html
but I can't get the filesystem show command to output anything useful:
gandalfthegreat:~# btrfs filesystem show /dev/mapper/cryptroot
Btrfs Btrfs v0.19
gandalfthegreat:~#
and the btrfs df ssems to show that I'm ok:
gandalfthegreat:~# btrfs filesystem df /home
Data: total=169.01GB, used=134.70GB
System, DUP: total=8.00MB, used=28.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=5.88GB, used=4.39GB
Metadata: total=8.00MB, used=0.00
gandalfthegreat:~#
I read about rebalance but it's a mostly new fliesystem will little churn, and I'm
not anywhere close to full filesystem yet.
So far, when this happened, I've had to delete a set of older snapshots.
This would make sense if I was close to full, but at 63% I'm nowhere that.
Any idea what's going on and how I can debug further and more specifically
what I should capture next time I get a no free space error in userspace?
Thanks,
Marc
gandalfthegreat:/mnt/btrfs_pool1# l
total 4
dr-xr-xr-x 1 root root 2210 Apr 15 08:00 ./
drwxr-xr-x 1 root root 112 Feb 12 17:38 ../
drwxr-xr-x 1 root root 12 Feb 12 17:57 home/
drwxr-xr-x 1 root root 12 Feb 12 17:57 home_daily_20120412_00:01:01/
drwxr-xr-x 1 root root 12 Feb 12 17:57 home_daily_20120413_00:01:02/
drwxr-xr-x 1 root root 12 Feb 12 17:57 home_daily_20120414_00:01:01/
drwxr-xr-x 1 root root 12 Feb 12 17:57 home_daily_20120415_00:01:01/
drwxr-xr-x 1 root root 12 Feb 12 17:57 home_hourly_20120415_06:00:01/
drwxr-xr-x 1 root root 12 Feb 12 17:57 home_hourly_20120415_07:00:01/
drwxr-xr-x 1 root root 12 Feb 12 17:57 home_hourly_20120415_08:00:01/
drwxr-xr-x 1 root root 12 Feb 12 17:57 home_weekly_20120415_00:02:01/
drwxr-xr-x 1 root root 436 Apr 3 07:26 root/
drwxr-xr-x 1 root root 436 Apr 3 07:26 root_daily_20120412_00:01:01/
drwxr-xr-x 1 root root 436 Apr 3 07:26 root_daily_20120414_00:01:01/
drwxr-xr-x 1 root root 436 Apr 3 07:26 root_daily_20120415_00:01:01/
drwxr-xr-x 1 root root 436 Apr 3 07:26 root_hourly_20120415_06:00:01/
drwxr-xr-x 1 root root 436 Apr 3 07:26 root_hourly_20120415_07:00:01/
drwxr-xr-x 1 root root 436 Apr 3 07:26 root_hourly_20120415_08:00:01/
drwxr-xr-x 1 root root 436 Apr 3 07:26 root_weekly_20120415_00:02:01/
drwxrwxrwt 1 root root 7476 Apr 15 08:05 tmp/
drwxrwxrwt 1 root root 7156 Apr 12 00:01 tmp_daily_20120412_00:01:01/
drwxrwxrwt 1 root root 7130 Apr 13 00:01 tmp_daily_20120413_00:01:02/
drwxrwxrwt 1 root root 7236 Apr 14 00:01 tmp_daily_20120414_00:01:01/
drwxrwxrwt 1 root root 7368 Apr 15 00:01 tmp_daily_20120415_00:01:01/
drwxrwxrwt 1 root root 7368 Apr 15 06:00 tmp_hourly_20120415_06:00:01/
drwxrwxrwt 1 root root 7368 Apr 15 07:00 tmp_hourly_20120415_07:00:01/
drwxrwxrwt 1 root root 7476 Apr 15 08:00 tmp_hourly_20120415_08:00:01/
drwxrwxrwt 1 root root 7368 Apr 15 00:02 tmp_weekly_20120415_00:02:01/
drwxr-xr-x 1 root root 206 Mar 31 11:07 usr/
drwxr-xr-x 1 root root 206 Mar 31 11:07 usr_daily_20120412_00:01:01/
drwxr-xr-x 1 root root 206 Mar 31 11:07 usr_daily_20120413_00:01:02/
drwxr-xr-x 1 root root 206 Mar 31 11:07 usr_daily_20120414_00:01:01/
drwxr-xr-x 1 root root 206 Mar 31 11:07 usr_daily_20120415_00:01:01/
drwxr-xr-x 1 root root 206 Mar 31 11:07 usr_hourly_20120415_06:00:01/
drwxr-xr-x 1 root root 206 Mar 31 11:07 usr_hourly_20120415_07:00:01/
drwxr-xr-x 1 root root 206 Mar 31 11:07 usr_hourly_20120415_08:00:01/
drwxr-xr-x 1 root root 206 Mar 31 11:07 usr_weekly_20120415_00:02:01/
drwxr-xr-x 1 root root 130 Feb 12 23:52 var/
drwxr-xr-x 1 root root 130 Feb 12 23:52 var_daily_20120412_00:01:01/
drwxr-xr-x 1 root root 130 Feb 12 23:52 var_daily_20120413_00:01:02/
drwxr-xr-x 1 root root 130 Feb 12 23:52 var_daily_20120414_00:01:01/
drwxr-xr-x 1 root root 130 Feb 12 23:52 var_daily_20120415_00:01:01/
drwxr-xr-x 1 root root 130 Feb 12 23:52 var_hourly_20120415_06:00:01/
drwxr-xr-x 1 root root 130 Feb 12 23:52 var_hourly_20120415_07:00:01/
drwxr-xr-x 1 root root 130 Feb 12 23:52 var_hourly_20120415_08:00:01/
drwxr-xr-x 1 root root 130 Feb 12 23:52 var_weekly_20120415_00:02:01/
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next reply other threads:[~2012-04-15 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 15:07 Marc MERLIN [this message]
2012-04-15 16:19 ` Creating backup snapshots (8 per filesystem) causes No space left on device? cwillu
[not found] ` <CAGy7Utjp79TVTnHyCqr1+iEr7c3g0_3X74CKLe91817DoK48DA@mail.gmail.com>
2012-04-15 16:27 ` Marc MERLIN
2012-04-17 14:16 ` Marc MERLIN
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=20120415150740.GA10248@merlins.org \
--to=marc@merlins.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 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).