public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian Bornträger" <borntraeger@de.ibm.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: regression post 2.6.30: device mapper fails on some logical volumes
Date: Thu, 16 Jul 2009 07:36:04 +0200	[thread overview]
Message-ID: <200907160736.09885.borntraeger@de.ibm.com> (raw)
In-Reply-To: <20090715214051.GB6399@redhat.com>

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

  reply	other threads:[~2009-07-16  5:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 16:52 regression post 2.6.30: device mapper fails on some logical volumes Christian Bornträger
2009-07-15 21:40 ` Mike Snitzer
2009-07-16  5:36   ` Christian Bornträger [this message]
2009-07-16 14:44     ` Mike Snitzer
2009-07-16 15:14       ` Christian Bornträger
2009-07-16 15:46       ` Christian Bornträger
2009-07-16 20:20         ` Mike Snitzer
2009-07-16 21:14           ` Christian Bornträger

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=200907160736.09885.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agk@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=snitzer@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox