Also here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186842 http://forums.gentoo.org/viewtopic-t-448587.html Upgraded to 2.6.16 gentoo-sources, and now dmsetup no longer works. Error message: dm-stripe: Target length not divisible According to the post above, the problem also exists with dmraid.
Which device-mapper version? Please, post exact ebuild name and version when filing bugs.
(In reply to comment #1) > Which device-mapper version? Please, post exact ebuild name and version when > filing bugs. > Sorry, forgot about that. The version I'm using is: sys-fs/device-mapper-1.02.02 However, the version in my initrd (I use dmsetup to boot) is... dmsetup version: Library version: 1.01.01 (2005-03-29) Driver version: 4.4.0 That's quite old, so I'm guessing I should upgrade and see if the problem still exists?
(In reply to comment #2) > That's quite old, so I'm guessing I should upgrade and see if the problem still > exists? Sounds like a good idea... :)
Okay, just tried dmsetup 1.02.03 and the problem still exists. This is with gentoo-sources-2.6.16-r3. The error is: dm-stripe: Target length not divisible by chunk size.
How about 1.02.07? Really please try w/ latest available version when reporting bugs.
(In reply to comment #5) > How about 1.02.07? Really please try w/ latest available version when reporting > bugs. > Same error with 1.02.07. Rebuilt by initrd with 1.02.07 and I boot using 2.6.15 kernel - everything goes fine. I try and use the same initrd with a 2.6.16 kernel and I get the aforementioned error.
(In reply to comment #6) > (In reply to comment #5) > > How about 1.02.07? Really please try w/ latest available version when reporting > > bugs. > > > > Same error with 1.02.07. > > Rebuilt by initrd with 1.02.07 and I boot using 2.6.15 kernel - everything goes > fine. I try and use the same initrd with a 2.6.16 kernel and I get the > aforementioned error. > I read here: http://www.howtoforge.com/forums/archive/index.php/t-1664.html that the 2.6 kernels no longer support fakeraid setups (i.e. dmsetup). Is this true?
No, 2.6 no longer supports ataraid but dmraid is the replacement.
This problem is detailed at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186842 and seems to not be a bug. Are you using dmraid or just plain device-mapper? If just plain device mapper please post /etc/dmtab and describe how you created the setup in the first place
(In reply to comment #9) > This problem is detailed at > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186842 and seems to not be > a bug. > > Are you using dmraid or just plain device-mapper? > > If just plain device mapper please post /etc/dmtab and describe how you created > the setup in the first place > Unfortunately (due to a hard drive failure) I no longer have this setup. I've read elsewhere however that the problem is just that the raid-cluster-size is not a factor of the total size of the device I created, and the newer device-mapper in the kernel dropped support for non-whole clusters at the end of the device. It's not a bug - it was an intentional change in device-mapper.
Indeed, closing...
