All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Strangeness on btrfs balance..
Date: 05 Feb 2011 12:34:00 +0100	[thread overview]
Message-ID: <BfIFFcRi1uB@helmut.hullen.de> (raw)
In-Reply-To: <AANLkTin=G4c90Ew44gg=4E4joJPf6wizww=jqS0g8o1D@mail.gmail.com>

Hallo, Evert,

Du meintest am 05.02.11:

> I have kernel version 2.6.36.3, compiled with gcc 4.4.5, btrfstools
> version 0.19+20101101

> I have a btrfs filesystem (/data) consisting of two 1TB hard disks,
> raid0.

> I added in another 1TB hard drive.

> root@X86-64:~# btrfs filesystem show
> failed to read /dev/sdh
> failed to read /dev/sdg
> failed to read /dev/sdf
> failed to read /dev/sde
> failed to read /dev/sr0
> failed to read /dev/fd0u800
> failed to read /dev/fd0

That's a "well known" error; the fix isn't yet implemented.

> Any idea of why this is happening?
> Last few lines of dmesg:
> floppy0: disk absent or changed during operation
> end_request: I/O error, dev fd0, sector 128
> end_request: I/O error, dev fd0, sector 0

May be that's another "well known" error; there is a fix too ...


> btrfs: found 69 extents
> btrfs: relocating block group 1897465380864 flags 9
> btrfs: found 95 extents
> btrfs: found 95 extents
> btrfs: relocating block group 1895317897216 flags 9
> btrfs: found 81 extents
> btrfs: found 81 extents

Just wait some time.
When I remember correctly: the "relocating" message appears every minute  
(slightly rounded).
In your example there's a difference of about 1/1000, you have to wait  
about 1000 minutes.

Viele Gruesse!
Helmut

      parent reply	other threads:[~2011-02-05 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05 10:31 Strangeness on btrfs balance Evert Vorster
2011-02-05 10:44 ` Felix Blanke
2011-02-05 11:34 ` Helmut Hullen [this message]

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=BfIFFcRi1uB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.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.