No space left on device with 3.10-rc2

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: No space left on device with 3.10-rc2
Date: Sat, 25 May 2013 19:36:03 +0200	[thread overview]
Message-ID: <6232345.YVWHbJQOVs@merkaba> (raw)

Hi!

Now I got it myself what I read again and again on this mailinglist: During apt-get upgrade I get no space left on device.

But there is:

merkaba:~> df -hT /
Dateisystem                Typ   Größe Benutzt Verf. Verw% Eingehängt auf
/dev/mapper/merkaba-debian btrfs   19G     14G  4,6G   76% /


merkaba:[…]> ./btrfs fi df /
Disk size:                18.62GB
Disk allocated:           18.62GB
Disk unallocated:            0.00
Used:                     13.79GB
Free (Estimated):          4.84GB       (Max: 4.84GB, min: 4.84GB)
Data to disk ratio:         100 %
merkaba:[…]> ./btrfs fi disk-usage /
Data,Single: Size:17.61GB, Used:13.04GB
   /dev/mapper/merkaba-debian      17.61GB

Metadata,Single: Size:1.01GB, Used:768.00MB
   /dev/mapper/merkaba-debian       1.01GB

System,Single: Size:4.00MB, Used:4.00KB
   /dev/mapper/merkaba-debian       4.00MB

Unallocated:
   /dev/mapper/merkaba-debian         0.00
merkaba:[…]> ./btrfs dev disk-usage /
/dev/mapper/merkaba-debian         18.62GB
   Data,Single:             17.61GB
   Metadata,Single:          1.01GB
   System,Single:            4.00MB
   Unallocated:                0.00

merkaba:[…]> ./btrfs fi sh
[…]

Label: 'debian'  uuid: […]
        Total devices 1 FS bytes used 13.79GB
        devid    1 size 18.62GB used 18.62GB path /dev/dm-0

Btrfs v0.19-367-g711b24a



I think I will let it run a rebalance. Not working as well:

merkaba:~> btrfs fi ba /
ERROR: error during balancing '/' - No space left on device
There may be more info in syslog - try dmesg | tail
merkaba:~#19> dmesg | tail
[…]
[72914.023312] btrfs: relocating block group 19348324352 flags 1
[72914.131856] btrfs: 24 enospc errors during balance



merkaba:~#1> btrfs ba start -musage=5 / 
Done, had to relocate 0 out of 24 chunks
merkaba:~> btrfs ba start -m /       
ERROR: error during balancing '/' - No space left on device
There may be more info in syslog - try dmesg | tail
merkaba:~#19> btrfs ba start -musage=20 /
Done, had to relocate 0 out of 24 chunks
merkaba:~> btrfs ba start -musage=80 /
ERROR: error during balancing '/' - No space left on device
There may be more info in syslog - try dmesg | tail
merkaba:~#19> btrfs ba start -musage=20 /
Done, had to relocate 0 out of 24 chunks
merkaba:~> btrfs ba start -musage=30 /
Done, had to relocate 0 out of 24 chunks
merkaba:~> btrfs ba start -musage=40 /
Done, had to relocate 0 out of 24 chunks
merkaba:~> btrfs ba start -musage=50 / 
Done, had to relocate 0 out of 24 chunks
merkaba:~> btrfs ba start -musage=60 /
ERROR: error during balancing '/' - No space left on device
There may be more info in syslog - try dmesg | tail
merkaba:~#19> dmesg | tail
[…]
[72914.023312] btrfs: relocating block group 19348324352 flags 1
[72914.131856] btrfs: 24 enospc errors during balance
[72994.276484] btrfs: 5 enospc errors during balance
[73004.238190] btrfs: 4 enospc errors during balance
[73019.385757] btrfs: 1 enospc errors during balance


How do I get this filesystem to an operational state again despite
reformatting?

Seems there are still no space left on device bugs left. Or some have been
introduced with 3.10.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

next             reply	other threads:[~2013-05-25 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25 17:36 Martin Steigerwald [this message]
2013-05-25 17:54 ` No space left on device with 3.10-rc2 Martin Steigerwald

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=6232345.YVWHbJQOVs@merkaba \
    --to=martin@lichtvoll.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 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.