Re: Adding new resiliency type to LVM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks. verbose mode exposed more parts of code in device mapper code
that I had to implement in order for my new target type "dyre" to get
identified.

My current problem is when there is an ioctl call, I am getting an
error with errno set to 22, which corresponds to "Invalid argument".

Could you please tell me where can I get the kernel part of the code
which handles the device mapper target? similar to "striped" target, I
think I need to add code there for my "dyre" target.

Thank you again for your help.
Regards,


On Fri, Nov 20, 2015 at 8:17 AM, Alasdair G Kergon <agk@xxxxxxxxxx> wrote:
> On Thu, Nov 19, 2015 at 04:25:44PM -0500, Shehbaz Jaffer wrote:
>> ln -s /dev/dm-0 /dev/mapper/vol_vg-root
>
> Lots of pieces of code are involved - if you are using udev, then udev rules
> are responsibly for managing it.
>
> For debugging, check you have 'activation/verify_udev_operations' set to 1 in
> lvm.conf.
>
> Alasdair
>
> --
> dm-devel mailing list
> dm-devel@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/dm-devel



-- 
Shehbaz Jaffer
First Year Graduate Student
Sir Edward S Rogers Sr Department of Electrical and Computer Engineering
University of Toronto

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel



[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux