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:	Wed, 15 Jul 2009 17:40:52 -0400
From:	Mike Snitzer <snitzer@...hat.com>
To:	Christian Bornträger <borntraeger@...ibm.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

On Wed, Jul 15 2009 at 12:52pm -0400,
Christian Bornträger <borntraeger@...ibm.com> wrote:

> Hello Mike,
> 
> your patch
> commit 754c5fc7ebb417b23601a6222a6005cc2e7f2913
> Author: Mike Snitzer <snitzer@...hat.com>
> Date:   Mon Jun 22 10:12:34 2009 +0100
> 
>     dm: calculate queue limits during resume not load
> 
> causes some problems during startup (/sbin/lvm vgchange -a y) on my s390 system.
> The logical volumes space-home and space-test dont come up (device-mapper: 
> resume ioctl faile: Invalid argument) and dmesg has:
> 
> [    4.450974] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-
> devel@...hat.com                                                                           
> [    4.567024] device-mapper: table: 253:0: target device dasdf1 is misaligned
...
> [    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

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