public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: paran@lysator.liu.se (Pär Andersson)
To: linux-btrfs@vger.kernel.org
Subject: btrfs-vol -b endless loop
Date: Wed, 03 Feb 2010 23:25:12 +0100	[thread overview]
Message-ID: <87636ej6t3.fsf@nsc.liu.se> (raw)

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

Hi,

I have a 11G btrfs file system where "btrfs-vol -b" get stuck in a
loop. The "found 7 extents" messages and heavy disk io continues until I
reboot:

[26223.544037] btrfs: relocating block group 42079027200 flags 36
[26228.082740] btrfs: found 2457 extents
[26228.104515] btrfs: relocating block group 41407938560 flags 1
[26228.423981] btrfs: found 124 extents
[26229.514583] btrfs: found 124 extents
[26229.544160] btrfs: found 7 extents
[26229.812494] btrfs: found 7 extents
[26230.453720] btrfs: found 7 extents
[26230.733233] btrfs: found 7 extents
[26231.383321] btrfs: found 7 extents
[26231.652815] btrfs: found 7 extents
...

The error is repeatable. btrfsck does not report any errors:

root@faran:~# btrfsck /dev/sda5
found 9035055104 bytes used err is 0
total csum bytes: 8293152
total tree bytes: 542867456
total fs tree bytes: 503087104
btree space waste bytes: 108089491
file data blocks allocated: 8492187648
 referenced 10314125312
Btrfs Btrfs v0.19

The kernel is Linus' master from two days ago, and seems to have all the
latest btrfs code merged.

Regards,
Pär Andersson

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

             reply	other threads:[~2010-02-03 22:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 22:25 Pär Andersson [this message]
2010-02-04  2:59 ` btrfs-vol -b endless loop Yan, Zheng 
2010-02-12 22:46   ` Pär Andersson

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=87636ej6t3.fsf@nsc.liu.se \
    --to=paran@lysator.liu.se \
    --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