| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <5ec358371001250725l40b13060md880001c96be165f@mail.gmail.com> Date: Mon, 25 Jan 2010 17:25:02 +0200 From: Marti Raudsepp <marti@...fo.org> To: Ing. Daniel Rozsnyó <daniel@...snyo.com> Cc: linux-kernel@...r.kernel.org Subject: Re: bio too big - in nested raid setup 2010/1/24 "Ing. Daniel Rozsnyó" <daniel@...snyo.com>: > Hello, > I am having troubles with nested RAID - when one array is added to the > other, the "bio too big device md0" messages are appearing: > > bio too big device md0 (144 > 8) > bio too big device md0 (248 > 8) > bio too big device md0 (32 > 8) I *think* this is the same bug that I hit years ago when mixing different disks and 'pvmove' It's a design flaw in the DM/MD frameworks; see comment #3 from Milan Broz: http://bugzilla.kernel.org/show_bug.cgi?id=9401#c3 Regards, Marti -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists