linux-kernel - Re: regression post 2.6.30: device mapper fails on some logical volumes

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 16 Jul 2009 07:36:04 +0200
From:	Christian Bornträger <borntraeger@...ibm.com>
To:	Mike Snitzer <snitzer@...hat.com>
Cc:	Alasdair G Kergon <agk@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: regression post 2.6.30: device mapper fails on some logical volumes

Am Mittwoch 15 Juli 2009 23:40:52 schrieb Mike Snitzer:

>
> > [    6.048168] device-mapper: table: 253:59: target device dasde1 is
> > misaligned
>
> Christian,
>
> Which kernel are you using?  I believe these warnings have been fixed
> with this commit (which should be part of 2.6.31-rc2):
> ea9df47cc92573b159ef3b4fda516c32cba9c4fd
>
> Mike

Mike,

I see the problem with 2.6.31-rc3. Given the content of patch ea9df4...it might 
be of interest that my dasd devices have a hard sector size of 4k:

$ sudo blockdev --getss /dev/dasdf1
4096
$ sudo blockdev --getbsz /dev/dasdf1
4096

Since I always get confused by the internal 512 bytes vs. hard sector size vs. 
block size vs. file system block size I dont know if that is important.

Christian
--
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/