From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mike Snitzer <snitzer@gmail.com>
Cc: martin.petersen@oracle.com, linux-kernel@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
dm-devel@redhat.com, Jens Axboe <jens.axboe@oracle.com>,
Heinz Diehl <htd@fancy-poultry.org>
Subject: Re: todays git regression (2.6.32-04008.g3ff6a46): lot of device mapper warnings
Date: Wed, 09 Dec 2009 20:14:03 -0500 [thread overview]
Message-ID: <yq1bpi7vdes.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <170fa0d20912091656s31575d0cneaf899e1781bdc16@mail.gmail.com> (Mike Snitzer's message of "Wed, 9 Dec 2009 19:56:46 -0500")
>>>>> "Mike" == Mike Snitzer <snitzer@gmail.com> writes:
Mike> On the surface I thought this might be the reason for the
Mike> warnings, but Martin's lcm() looks perfectly fine; can't see why
Mike> it would cause these warnings to appear all of a sudden... but I
Mike> figured I'd share.
The warning is caused by an error in stacking discard granularity. I
have a fix but I'd like to run verify all my oddball alignment combos
before submitting.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mike Snitzer <snitzer@gmail.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Heinz Diehl <htd@fancy-poultry.org>,
linux-kernel@vger.kernel.org, martin.petersen@oracle.com,
Christian Borntraeger <borntraeger@de.ibm.com>,
dm-devel@redhat.com
Subject: Re: todays git regression (2.6.32-04008.g3ff6a46): lot of device mapper warnings
Date: Wed, 09 Dec 2009 20:14:03 -0500 [thread overview]
Message-ID: <yq1bpi7vdes.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <170fa0d20912091656s31575d0cneaf899e1781bdc16@mail.gmail.com> (Mike Snitzer's message of "Wed, 9 Dec 2009 19:56:46 -0500")
>>>>> "Mike" == Mike Snitzer <snitzer@gmail.com> writes:
Mike> On the surface I thought this might be the reason for the
Mike> warnings, but Martin's lcm() looks perfectly fine; can't see why
Mike> it would cause these warnings to appear all of a sudden... but I
Mike> figured I'd share.
The warning is caused by an error in stacking discard granularity. I
have a fix but I'd like to run verify all my oddball alignment combos
before submitting.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2009-12-10 1:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 9:49 todays git regression (2.6.32-04008.g3ff6a46): lot of device mapper warnings Christian Borntraeger
2009-12-09 21:25 ` Heinz Diehl
2009-12-09 21:45 ` Jens Axboe
2009-12-09 22:07 ` Jens Axboe
2009-12-10 0:56 ` Mike Snitzer
2009-12-10 0:56 ` Mike Snitzer
2009-12-10 1:14 ` Martin K. Petersen [this message]
2009-12-10 1:14 ` Martin K. Petersen
2009-12-11 9:28 ` Christian Borntraeger
2009-12-11 9:28 ` Christian Borntraeger
2009-12-11 16:47 ` Martin K. Petersen
2009-12-11 16:47 ` [dm-devel] " Martin K. Petersen
2009-12-10 11:08 ` Christian Borntraeger
2009-12-10 14:08 ` Heinz Diehl
2009-12-12 1:51 ` Christian Kujau
2009-12-15 21:58 ` Christian Kujau
2009-12-15 22:02 ` Jens Axboe
2009-12-15 22:08 ` Martin K. Petersen
2009-12-15 22:16 ` Jens Axboe
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=yq1bpi7vdes.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=borntraeger@de.ibm.com \
--cc=dm-devel@redhat.com \
--cc=htd@fancy-poultry.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.