public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eugene Crosser <crosser@average.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC errors during raid1 rebalance
Date: Fri, 14 Mar 2014 02:38:56 +0400	[thread overview]
Message-ID: <53223380.3000308@average.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]

Hello,

I want to report that I have the same problem as Michael Russo, except in my
case there is definitely *a lot* of free space.

I had ext4 on a 1Tb LVM mirror. The filesystem was 96% full, with many multi-Gb
files. I successfully converted it into btrfs, removed ext2_saved subvolume, but
did *not* defragment or balance.

Then I added two fresh 4Tb disks to the filesystem, and tried to convert it to
raid1. My plan was to then delete the original LVM disk and have all my data
migrated to the new 4Tb disks under btrfs mirror.

But balancing cannot complete with the same symptoms:

[...]
[12746.391828] block group has cluster?: no
[12746.391830] 0 blocks of free space at or bigger than bytes is
[12747.420098] btrfs: 35 enospc errors during balance

root@pccross:~# btrfs fi sh
Label: 'export'  uuid: 02f39e9d-9115-4a79-9015-a3a9decb87cf
	Total devices 3 FS bytes used 798.15GB
	devid    3 size 3.64TB used 855.03GB path /dev/sdd1
	devid    2 size 3.64TB used 855.00GB path /dev/sdc1
	devid    1 size 891.51GB used 175.48GB path /dev/md5

Btrfs v0.20-rc1

root@pccross:~# btrfs fi df /export
Data, RAID1: total=849.00GB, used=650.25GB
Data: total=175.48GB, used=145.64GB
System: total=32.00MB, used=136.00KB
Metadata, RAID1: total=6.00GB, used=2.21GB

root@pccross:~# uname -a
Linux pccross 3.13.0-17-generic #37-Ubuntu SMP Mon Mar 10 21:44:01 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux

Attempt "btrfs device delete" fails with the same "no space" diagnostic.

I am running defragmentation on all files bigger than 1Gb now, and see what
happens. If that does not help, is there any other advice? I can collect
debugging data if needed.

Thanks,

Eugene


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 547 bytes --]

             reply	other threads:[~2014-03-13 22:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 22:38 Eugene Crosser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-03 17:23 ENOSPC errors during raid1 rebalance Mike Russo
2014-03-03 18:16 ` Duncan
2014-03-03 18:24   ` Michael Russo
2014-03-03 18:48     ` Chris Murphy
2014-03-03 19:24       ` Michael Russo
2014-03-03 20:41         ` Chris Murphy
2014-03-03 20:50           ` Michael Russo
2014-03-03 21:02             ` Chris Murphy
2014-03-03 18:39 ` Hugo Mills
2014-03-04 15:55   ` Michael Russo
2014-03-04 17:29     ` Chris Murphy
2014-03-04 18:54       ` Michael Russo
2014-03-04 19:30         ` Chris Murphy
2014-03-05  0:27   ` Mike Russo
2014-03-05  3:32     ` Chris Murphy
2014-03-05 22:13       ` Michael Russo
2014-03-06  7:41         ` Duncan
2014-03-07  1:13           ` Michael Russo
2014-03-07  8:02             ` Hugo Mills
2014-03-07 10:18               ` Duncan
2014-03-07 14:17               ` Mike Russo
2014-03-08  1:46                 ` Mike Russo
2014-03-05  4:08     ` Chris Murphy
2014-03-05 22:13       ` Michael Russo
2014-03-06 17:07         ` Chris Murphy

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=53223380.3000308@average.org \
    --to=crosser@average.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