public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Mike Russo <mike@PaperSolve.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: ENOSPC errors during raid1 rebalance
Date: Mon, 3 Mar 2014 18:39:11 +0000	[thread overview]
Message-ID: <20140303183911.GL13899@carfax.org.uk> (raw)
In-Reply-To: <DF16C10AFF7F394A8C8A09C9405478890BCBE534@EXHOST.stardatecomputer.com>

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

On Mon, Mar 03, 2014 at 05:23:43PM +0000, Mike Russo wrote:
> Hi guys -
> I'm trying to convert a disk from single (/dev/sdc1) to RAID1 (dev/sdd1), and the filesystem was previously ext4 but the conversion seemed to go just fine, and I have no snapshots. System and metadata convert, and almost all my data converts, but there are 70 stubborn GB (14 blocks of 5GB each) that refuse to convert and I get ENOSPC errors when trying to reallocate them.

   This is just a guess, but you might have some large (>1GB) extents
in there that span across multiple chunks. I'd suggest running a btrfs
defrag on any particularly big files and see if that helps the situation.

   Hugo.

> Here's my vital stats: (on kernel 3.14-rc4):
> 
> root@ossy:/usr/src/btrfs-progs# /usr/src/btrfs-progs/btrfs fi show
> Label: MyBook  uuid: c99cbefb-6a56-41e2-8f99-19f8b5f67884
>         Total devices 2 FS bytes used 1.09TiB
>         devid    1 size 1.82TiB used 1.12TiB path /dev/sdc1
>         devid    2 size 1.82TiB used 1.05TiB path /dev/sdd1
> 
> Btrfs v3.12
> root@ossy:/usr/src/btrfs-progs# /usr/src/btrfs-progs/btrfs fi df /mymedia
> Data, RAID1: total=1.04TiB, used=1.03TiB
> Data, single: total=70.00GiB, used=64.98GiB
> System, RAID1: total=32.00MiB, used=160.00KiB
> Metadata, RAID1: total=2.00GiB, used=1.33GiB
> 
> 
> I've already done a -dusage=0 and -dusage=5 balance and that cleans up anything that gets left around when these 14 blocks fail get moved.    When mounting with enospc_debug I get messages like this for each block with the problem:
> 
> 
> Mar  3 11:58:16 ossy kernel: [52724.423024] BTRFS: block group 935262683136 has 5368709120 bytes, 5321801728 used 0 pinned 0 reserved [readonly]
> Mar  3 11:58:16 ossy kernel: [52724.423025] BTRFS info (device sdd1): block group has cluster?: no
> Mar  3 11:58:16 ossy kernel: [52724.423026] BTRFS info (device sdd1): 0 blocks of free space at or bigger than bytes is
> Mar  3 11:58:16 ossy kernel: [52724.423027] BTRFS: block group 942778875904 has 5368709120 bytes, 5309296640 used 0 pinned 0 reserved [readonly]
> Mar  3 11:58:16 ossy kernel: [52724.423028] BTRFS info (device sdd1): block group has cluster?: no
> Mar  3 11:58:16 ossy kernel: [52724.423029] BTRFS info (device sdd1): 0 blocks of free space at or bigger than bytes is
> 
> I don't have the space to reformat and if this is a genuine bug I'm sure you guys want to fix it too. What else can I do to resolve or help? 
> 
> 
> Sincerely,
> 
> Michael Russo, Systems Engineer
> PaperSolve, Inc.
> 268 Watchogue Road
> Staten Island, NY 10314
> 

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
   --- Nothing wrong with being written in Perl... Some of my best ---   
                      friends are written in Perl.                       

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

  parent reply	other threads:[~2014-03-03 18:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2014-03-13 22:38 Eugene Crosser

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=20140303183911.GL13899@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mike@PaperSolve.com \
    /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