All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srini <v.vvsrini@gmail.com>
To: dm-devel@redhat.com
Subject: Linux 2.6.19.1 device mapper error
Date: Mon, 12 Feb 2007 06:23:54 +0530	[thread overview]
Message-ID: <25b3869e0702111653re7487ffq1ff1f2ebf263bc20@mail.gmail.com> (raw)

On further debugging, we found that if we are using a kernel version
2.6.16, the device mapper was functioning correctly as expected. The
device mapper version in 2.6.16 is 4.5.0-ioctl and the device mapper
version in  2.6.19.1 kernel is 4.11.0-ioctl.

Is there a difference between the 4.5.0 version and 4.11.0 version
that could be causing the problem that we are facing? Is there a list
of changes that has gone into device-mapper between these two
versions?

Thanks in advance for your inputs,

Srini

On 2/8/07, Srini <v.vvsrini@gmail.com> wrote:
> Hi all,
>
> I am currently trying to create a snapshot through EVMS (v2.5.4) and I am getting an error from the device mapper module in the kernel version 2.6.19.1 (dmesg). The following is the error message:
>
> device-mapper: table: 253:2: snapshot-origin: unknown target type
> device-mapper: ioctl: error adding target to table
> device-mapper: table: 253:7: snapshot: requires exactly 4 arguments
> device-mapper: ioctl: error adding target to table
> device-mapper: table: 253:7: snapshot: requires exactly 4 arguments
> device-mapper: ioctl: error adding target to table
>
> The lsmod command on the same machine shows the dm-snapshat module to have been successfully inserted:
>
> -bash-3.00# lsmod
> Module                  Size  Used by    Not tainted
> dm_snapshot 17192 1 - Live 0xf8948000
> dm_mod 51736 14 dm_snapshot, Live 0xf8906000
> nfsd 216944 0 - Live 0xf89c4000
> exportfs 5632 1 nfsd, Live 0xf88cf000
>
> The device mapper version itself (as printed in dmesg) is as follows:
>
> device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised:    dm-devel@redhat.com
>
> Since the device mapper is returning an error, the EVMS Snapshot plugin is returning an invalid argument (EINVAL) and exiting.
>
> Any help would be much highly appreciated since we have been facing this issue for a week now...
>
> Thanks in advance for all  your inputs,
>
> srini

                 reply	other threads:[~2007-02-12  0:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=25b3869e0702111653re7487ffq1ff1f2ebf263bc20@mail.gmail.com \
    --to=v.vvsrini@gmail.com \
    --cc=dm-devel@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 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.