From: alexander.tsvetkov@oracle.com
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: dmsetup arguments
Date: Wed, 19 Jun 2013 18:42:02 +0400 [thread overview]
Message-ID: <51C1C33A.5040501@oracle.com> (raw)
In-Reply-To: <20130618132346.GT29338@dastard>
On 06/18/13 17:23, Dave Chinner wrote:
> On Tue, Jun 18, 2013 at 04:08:44PM +0400, alexander.tsvetkov@oracle.com wrote:
>> On 06/18/13 05:26, Dave Chinner wrote:
>>> On Fri, Jun 14, 2013 at 12:51:25PM +0400, alexander.tsvetkov@oracle.com wrote:
>>>> Hi,
>>>>
>>>> XFStests suite generic/311 test fails on command: "sbin/dmsetup load
>>>> flakey-test --table "0 150000001 flakey /dev/sdc2 0 0 180 1
>>>> drop_writes" with error: "device-mapper: reload ioctl on flakey-test
>>>> failed: Invalid argument", so as I understand the command format
>>>> provided to ioctl is incorrect here. Kernel logs has message:
>>>>
>>>> "Jun 13 16:47:15 tests kernel: device-mapper: table: 252:3: flakey:
>>>> dm-flakey: Invalid argument count
>>>> Jun 13 16:47:15 tests kernel: device-mapper: ioctl: error adding
>>>> target to table"
>>> What kernel and version of dmsetup are you using? If it is too old
>>> to support the flakey target, then we need a new require rule check
>>> for the test to avoid old versions of dmsetup...
>> Kernel version is 2.6.39, version of device-mapper-libs is 1.02.77.
> So it's an old version of both the kernel and DM, so it's probably
> not been tested at all. Like I said - it probably needs a better
> check in _require_dm_flakey() to determine if the test should be run
> or not.
>
I agree about kernel version, but why DM version of 1.02.77 is also old?
I though that I am using the latest version of DM referenced by these
sources:
"Releases
The userspace code (dmsetup and libdevmapper) is now maintained
alongside the LVM2 source available from http://sources.redhat.com/lvm2/."
http://www.sourceware.org/dm/
and
"Source code
The source code is stored in git and can be accessed with git clone
git://git.fedorahosted.org/git/lvm2.git
There is a web interface to git at http://git.fedorahosted.org/git/lvm2.git"
http://sources.redhat.com/lvm2/
so finally I've got DM of version 1.02.77 within lvm2 package of version
2.02.98 from http://git.fedorahosted.org/git/lvm2.git, it's of latest
released version in the provided list.
Most recent lvm2 package from master branch of 2.02.99 version contains
DM ofversion 1.02.78 which has no attribute "drop_writes" in sources as
well.
Thanks,
Alexander Tsvetkov
> Patches are welcome...
>
> Cheers,
>
> Dave.
>
> PS: please reply-to-all for mailing list traffic, not by private
> email. I've re-added the XFS list to the CC list.
>
> PPS: Top posting destroys the context of your reply - nobody has any
> idea of what part of the previous message you are responding to.
> Repsonding inline is much easier to follow with when conversions get
> long...
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-06-19 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 8:51 dmsetup arguments alexander.tsvetkov
2013-06-18 1:26 ` Dave Chinner
[not found] ` <51C04DCC.7010401@oracle.com>
2013-06-18 13:23 ` Dave Chinner
2013-06-19 14:42 ` alexander.tsvetkov [this message]
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=51C1C33A.5040501@oracle.com \
--to=alexander.tsvetkov@oracle.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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