From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: no space left (was: version)
Date: 27 Jan 2011 14:49:00 +0100 [thread overview]
Message-ID: <BeeuNkKD1uB@helmut.hullen.de> (raw)
In-Reply-To: <1296114256-sup-4788@think>
Hallo, Chris,
Du meintest am 27.01.11:
>> crashes with the "dmesg" lines
>>
>> --------------------- dmesg -------------------
>>
>> bio too big device sdc (256 > 240)
>> bio too big device sdc (256 > 240)
>> bio too big device sdc (256 > 240)
>> bio too big device sdc (256 > 240)
>> ------------[ cut here ]------------
>> kernel BUG at fs/btrfs/volumes.c:2097!
> Ugh, this one is an old friend I thought I had fixed up. The two
> devices have different limits on the max size of the bio, and we're
> using one that is too large.
> I'll get it fixed for the next rc.
Sorry - the problem seems to exist in kernel 2.6.37 too.
/dev/sdb1 with about 8 GByte
/dev/sdc1 with about 12 GByte
mkfs.btrfs /dev/sdb1
mount /dev/sdb1 /mnt/btr
cp <dir with 6 GByte>
btrfs device add /dev/sdc1 /mnt/btr
looks good.
btrfs filesystem balance /mnt/btr
seems to look good.
But then (at about 14:34)
cp <dir with 2 Gbyte> /mnt/btr
sends the following lines to "/var/log/messages":
-------------- var/log/messages ----------------------
Jan 27 14:08:15 ElNath kernel: device fsid e144bfc5cb117745-
187a9339eb8c0daa devid 1 transid 7 /dev/sdb1
Jan 27 14:24:04 ElNath kernel: end_request: I/O error, dev fd0, sector 0
Jan 27 14:25:34 ElNath kernel: btrfs: relocating block group 7330660352 flags 1
Jan 27 14:25:35 ElNath last message repeated 2 times
Jan 27 14:25:35 ElNath kernel: btrfs: relocating block group 12582912 flags 1
Jan 27 14:25:36 ElNath kernel: btrfs: found 19 extents
Jan 27 14:25:36 ElNath kernel: btrfs: found 19 extents
Jan 27 14:25:36 ElNath kernel: btrfs: relocating block group 4194304 flags 4
Jan 27 14:26:37 ElNath kernel: end_request: I/O error, dev fd0, sector 0
Jan 27 14:34:28 ElNath kernel: bio too big device sdc1 (256 > 240)
Jan 27 14:34:59 ElNath last message repeated 2474 times
Jan 27 14:35:02 ElNath last message repeated 357 times
Jan 27 14:35:04 ElNath squid[3493]: NETDB state saved; 0 entries, 239 msec
but the system seems to copy all files, without any "no space left".
Does this error depend on the sequence (?) of the commands?
Earlier I always typed
mkfs.btrfs /dev/sdb1
mount /dev/sdb1 /mnt/btr
btrfs device add /mnt/sdc1 /mnt/btr
cp ...
btrfs filesystem balance /mnt/btr
and then copying more files led to "no space left".
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-01-27 13:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 21:06 btrfs, broken design? Benoît Thiébault
2011-01-20 21:20 ` Chris Mason
2011-01-21 5:25 ` Benoît Thiébault
2011-01-21 6:46 ` Chester
2011-01-21 8:11 ` Benoît Thiébault
2011-01-21 8:21 ` Hubert Kario
2011-01-21 9:54 ` version (was: btrfs, broken design?) Helmut Hullen
2011-01-21 12:21 ` Hugo Mills
2011-01-21 14:10 ` version Helmut Hullen
2011-01-21 14:32 ` version (was: btrfs, broken design?) Diego Calleja
2011-01-21 14:55 ` version Helmut Hullen
2011-01-21 15:12 ` version Hugo Mills
2011-01-21 15:19 ` version Helmut Hullen
2011-01-24 3:20 ` version Chris Samuel
2011-01-24 8:33 ` version Helmut Hullen
2011-01-24 21:14 ` version Johannes Hirte
2011-01-24 21:39 ` version Helmut Hullen
2011-01-24 22:46 ` version Chris Samuel
2011-01-25 1:03 ` version Chris Mason
2011-01-25 6:43 ` version Helmut Hullen
2011-01-25 14:37 ` version Helmut Hullen
2011-01-27 5:02 ` 2.6.38-rc2 oops's when rebalancing on different size drives (was Re: version) Chris Samuel
2011-01-27 7:45 ` version Chris Mason
2011-01-27 8:16 ` version Helmut Hullen
2011-01-27 13:28 ` version Helmut Hullen
2011-01-27 13:49 ` Helmut Hullen [this message]
2011-01-26 10:13 ` version (was: btrfs, broken design?) Erik Logtenberg
2011-01-26 14:13 ` Diego Calleja
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=BeeuNkKD1uB@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.