<div dir="ltr"><div>Thanks a lot. </div>Can you guide me how to push upstream for the approval. Which branch should I push to? Any list of testcases I should perform before I could push?<div> </div><div>I have created the following two patches. PFA </div><div> </div><div>Regards,</div><div>Tejaswini</div></div><div class="gmail_extra"> <div class="gmail_quote">On Mon, Jul 6, 2015 at 11:15 PM, Benjamin Marzinski <<a href="mailto:bmarzins@redhat.com" target="_blank">bmarzins@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Jun 30, 2015 at 11:22:37AM +0530, Tejaswini Poluri wrote: > Thanks Ben. So should I push the code to the upstream and get an approval? > Regards, Yes. Thanks! -Ben > Tejaswini > On Tue, Jun 30, 2015 at 12:50 AM, Benjamin Marzinski <div><div class="h5">> <[1]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a>> wrote: > > On Fri, Jun 26, 2015 at 12:21:48PM +0530, Tejaswini Poluri wrote: > > Yes I agree that having the same code in both cli_add_map() and > ev_add_map > > is not necessary. Hence I would suggest removing get_refwwid() code > from > > ev_add_map as it is not being used by anyone. > > > > ev_add_map(param, NULL, vecs) would create the multipath device by > using > > the get_refwwid() code and but all the functions above it like > > (dm_get_minor, dm_get_major and dm_mapname) would fail and it > wouldn't > > enter any of the other code in ev_add_map like > > 1.dm_map_present, > > 2.add_map_without_path > > 3. sync_map_state > > which are responsible for registering the map and displaying it. > > > > So, I think moving the below code from ev_add_map to cli_add_map > should be > > a good idea right. > > > > r = get_refwwid(dev, DEV_DEVMAP, vecs->pathvec,&refwwid); > > > > > > if (refwwid) { > > > r = coalesce_paths(vecs, NULL, refwwid,0); > > > dm_lib_release(); > > > } > > What do u think? > > I agree. We aren't using the code in ev_add_map, so it's presence there > is simply confusing. > > -Ben > > > > Regards, > > Tejaswini > > On Fri, Jun 26, 2015 at 4:32 AM, Benjamin Marzinski </div></div><div><div class="h5">> > <[1][2]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a>> wrote: > > > > On Tue, Jun 23, 2015 at 03:48:26PM +0530, Tejaswini Poluri wrote: > > > Hi Ben, > > > > > > This is regarding the add map issue I have been discussing. > Posting > > the > > > issue again to remind. > > > > > > Case 1 : remove and add map. > > > root@x86-generic-64:~# multipathd -k'show maps' > > > name sysfs uuid > > > dmpath0 dm-0 1IET_00010001 > > > root@x86-generic-64:~# multipathd -k'remove map dmpath0' > > > ok > > > root@x86-generic-64:~# multipathd -k'show maps' > > > root@x86-generic-64:~# multipathd -k'add map dmpath0' > > > ok > > > root@x86-generic-64:~# multipathd -k'show maps' > > > root@x86-generic-64:~# > > > Once a map is removed, we are able to add it only using > #multipath > > > command and not using multipathd tools. > > > > > > I have fixed the problem with two approaches. I would like > you to > > review > > > the same. > > > Patch1 : By making 'remove map dmpath0' to remove only the > map and > > not the > > > device. I have added extra functions discard_map and > dm_remove_map > > so as > > > to not interfere with the existing code. > > > > > > Patch 2: The approach you have suggested.By getting wwid > from the > > mapname > > > and doing coalesce_paths. I have just moved the following > code in > > > ev_add_map to cli_add_map. > > > > This is the general idea we'd like to go with. However, looking > at the > > latest upstream code, I don't think you should pull code in from > > ev_add_map() to cli_add_map() like your patch does. cli_add_map() > > already calls ev_add_map(), and ev_add_map() is certainly able to > add > > the map if it doesn't already exist. > > > > You would just need to call it with > > > > ev_add_map(param, NULL, vecs); > > > > and ev_add_map() will happily create you a new multipath device. > All > > you need to do is make sure that all the functions that > ev_add_map() > > calls with alias can accept a NULL value there. > > > > This might not be the best way to go about this, however. It > turns out > > that right now, even though ev_add_map() technically has the > ability to > > create new maps, nothing currently uses it, and it really doesn't > make > > sense for it to be there. Instead of just copying that code, you > could > > pull the map creation code out of ev_add_map() and add it to > > cli_add_map(), for those situations where the requested device > doesn't > > already exist. > > > > But having the code in both cli_add_map() and ev_add_map() when > one > > already calls the other doesn't seem necessary. > > > > -Ben > > > > > > > > r = get_refwwid(dev, DEV_DEVMAP, vecs->pathvec,&refwwid); > > > > > > if (refwwid) { > > > r = coalesce_paths(vecs, NULL, refwwid,0); > > > dm_lib_release(); > > > } > > > > > > changed dev to param. > > > > > > I have tested the same in all 3 versions -0.4.8, 0.4.9 and > 0.5.0. > > It would > > > be great if you can review the same so that it doesn't cause > any > > extra > > > side effects. > > > I guess Patch2 is the way u have suggested me in the > previous mail. > > Please > > > review it and share your views. > > > Regards, > > > Tejaswini > > > On Fri, Jun 12, 2015 at 2:21 AM, Benjamin Marzinski </div></div><div><div class="h5">> > > <[1][2][3]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a>> wrote: > > > > > > On Wed, Jun 10, 2015 at 11:46:51AM +0530, Tejaswini Poluri > wrote: > > > > > > > > > We are testing multipathd tools with all the > possible > > options > > > and the > > > > > following fails. > > > > > > > > > > Case 1 : remove and add map. > > > > > root@x86-generic-64:~# multipathd -k'show maps' > > > > > name sysfs uuid > > > > > dmpath0 dm-0 1IET_00010001 > > > > > root@x86-generic-64:~# multipathd -k'remove map > > dmpath0' > > > > > ok > > > > > root@x86-generic-64:~# multipathd -k'show maps' > > > > > root@x86-generic-64:~# multipathd -k'add map > dmpath0' > > > > > ok > > > > > root@x86-generic-64:~# multipathd -k'show maps' > > > > > root@x86-generic-64:~# > > > > > Once a map is removed, we are able to add it > only using > > > #multipath > > > > > command and not using multipathd tools. > > > > > > > > It is working the way it was designed, but possibly > it would > > make > > > sense > > > > to change the design. > > > > > > > > You have mentioned that it would make sense to change > the > > design to > > > add > > > > map. Are there plans to change the design ? > > > > I am trying to understand the code flow to change the > > design. Can > > > you > > > > guide me if we should stop removing the device from > in the > > remove > > > map code > > > > flow or start adding the device and the map in the > add map > > code > > > flow. > > > > > > > > have tried to understand the remove map code flow of > > multipathd in > > > 0.4.8 > > > > code. > > > > > > I think that we want multipath to actually remove the map > > (instead of > > > just not monitoring it) when you call "remove map <map>". > We just > > want > > > "add map <map>" to try to create the map if it doesn't > exist. To > > do > > > that, you would need to first firgure out what WWID is > associated > > with > > > <map>. Presumably, <map> could either be an alias, wwid, > or even > > the > > > name of a path in the map. Once you found the map, you > would have > > to > > > call the code to create the map. > > > > > > Also, to answer your IRC question, no the 0.4.8 code is > not still > > being > > > developed upstream. All upstream patches only go against > the > > current > > > head. There are no other upstream branches. > > > > > > -Ben > > > > > > > > ev_remove_map (char * devname, struct vectors * vecs) > > > > > > > > flush_map(mpp, vecs); > > > > > > > > dm_flush_map(mpp->alias, > > DEFAULT_TARGET); > > > > > > > > if > > (!dm_map_present(mapname)) > > > > > > > > return 0; > > > > > > > > if (dm_type(mapname, type) <= 0) > > > > > > > > return 1; > > > > > > > > if (dm_remove_partmaps(mapname)) > > > > > > > > return 1; > > > > > > > > if (dm_get_opencount(mapname)) { > > > > > > > > condlog(2, "%s: map in use", mapname); > > > > > > > > return 1; > > > > > > > > } > > > > > > > > r = dm_simplecmd(DM_DEVICE_REMOVE, mapname); > > > > > > > > if (r) { > > > > > > > > condlog(4, "multipath map %s removed", > > mapname); > > > > > > > > return > 0; > > > > > > > > } > > > > > > > > > > > > > > > > orphan_paths(vecs->pathvec, > mpp); > > > > > > > > remove_map(mpp, vecs, > > stop_waiter_thread, > > > 1); > > > > > > > > Is removing this below line, the right step to stop > removing > > the > > > device ? > > > > r = dm_simplecmd(DM_DEVICE_REMOVE, mapname); > > > > > > > > Regards, > > > > > > > > Tejaswini > > > > > > > > On Mon, Jun 8, 2015 at 11:15 AM, Tejaswini Poluri </div></div>> > > > <[1][2][3][4]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a>> wrote: > > > > > > > > Thanks a lot Ben for the quick and detailed reply. > I have > > been > > > > struggling to understand and conclude the issues > with > > multipath > > > as I am > > > > the only one working from my team. Your inputs help > me a > > lot. > > > Thanks > > > > again. > > > > Regards, > > > > Tejaswini > > > > On Sat, Jun 6, 2015 at 3:36 AM, Benjamin Marzinski <div><div class="h5">> > > > <[2][3][4][5]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a>> wrote: > > > > > > > > On Fri, Jun 05, 2015 at 02:31:20PM +0530, > Tejaswini > > Poluri > > > wrote: > > > > > Hii Ben, > > > > > > > > > > We are testing multipathd tools with all the > > possible > > > options and > > > > the > > > > > following fails. > > > > > > > > > > Case 1 : remove and add map. > > > > > root@x86-generic-64:~# multipathd -k'show > maps' > > > > > name sysfs uuid > > > > > dmpath0 dm-0 1IET_00010001 > > > > > root@x86-generic-64:~# multipathd -k'remove > map > > dmpath0' > > > > > ok > > > > > root@x86-generic-64:~# multipathd -k'show > maps' > > > > > root@x86-generic-64:~# multipathd -k'add map > > dmpath0' > > > > > ok > > > > > root@x86-generic-64:~# multipathd -k'show > maps' > > > > > root@x86-generic-64:~# > > > > > Once a map is removed, we are able to add it > only > > using > > > > #multipath > > > > > command and not using multipathd tools. > > > > > > > > It is working the way it was designed, but > possibly it > > would > > > make > > > > sense > > > > to change the design. The "remove map" command, > not > > only stops > > > > multipathd from monitoring the multipath device, > but it > > removes > > > it > > > > from > > > > the system as well. The "add map" command makes > > multipath > > > monitor an > > > > already existing multipath device that in wasn't > > previously > > > > monitoring. > > > > These commands do this for historical reasons. > > multipathd > > > wasn't > > > > originally in charge of creating multipath > devices, > > multipath > > > was. > > > > Once > > > > it had created the device, it ran > > > > > > > > multipathd -k"add map <MAP>" > > > > > > > > to make multipathd start monitoring it. However > things > > haven't > > > worked > > > > this way since RHEL4, so possibly "add map" > should > > actually > > > create the > > > > device if it doesn't currently exist. > > > > > Case 2 : Active paths test case > > > > > # while true ; do sleep 3 ; multipathd > -k'remove > > path sdb' > > > ; > > > > multipathd > > > > > -k'add path sdb' ; multipathd -k'show maps > status' > > ; done > > > > > ok > > > > > ok > > > > > name failback queueing paths dm-st > > > > > dmpath0 - - 1 active // It should be 2. > > > > > > > > This is simply a timing issue. What you are > seeing it > > the > > > number of > > > > active paths. These are paths that the kernel > can use. > > The > > > "add path" > > > > command doesn't update the kernel state. This > happens > > later in > > > > response > > > > to the kernel reloading the device table. So, in > a > > second or > > > two, this > > > > will say 2, as expected. > > > > > > > > > We would like to know if the test cases are > valid > > and if > > > these > > > > are bugs or > > > > > any design issues. > > > > > > > > > > Case 3 : Fail path and reinstate path > > > > > root@x86-generic-64:~# multipathd -k"fail > path > > sdc"; > > > multipathd > > > > > -k'reinstate path sdc'; multipathd -k"show > paths"; > > > > > > [ 3962.708523] device-mapper: > multipath: > > Failing path > > > 8:32. > > > > > > ok > > > > > > ok > > > > > > hcil dev dev_t pri dm_st chk_st > > next_check > > > > > > 4:0:0:1 sdc 8:32 1 [active][faulty] > > .......... > > > 1/20 > > > > <==CHECK > > > > > > 5:0:0:1 sdd 8:48 1 [active][ready] > > XX........ > > > 4/20 > > > > > sdc path becomes [active][ready] only after > the > > polling > > > interval > > > > but not > > > > > immediately after the reinstate path > command. > > > > > You have answered that this is a design > issue. But > > we have > > > heard > > > > from our > > > > > test team that the same test case works in > RHEL6. > > Did you > > > observe > > > > it? > > > > > I am also finding that the test cases fail > because > > we are > > > trying > > > > to do > > > > > multiple commands at one shot. Please share > your > > thoughts > > > so > > > > that it > > > > > could help me in debugging the issues > further. > > > > > > > > > > > > > It's totally possible that the checker state is > > immediately > > > updated in > > > > RHEL6. Like I said before, what it currently > does, > > although > > > correct, > > > > is confusing, and perhaps we need a different > checker > > state for > > > paths > > > > where the "fail path" command has been used. > > > > > > > > -Ben > > > > > Regards, > > > > > Tejaswini > > > > > On Tue, May 19, 2015 at 5:37 PM, Tejaswini > Poluri </div></div>> > > > > <[1][3][4][5][6]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a>> > wrote: > > > > > > > > > > Thanks a lot Ben. I will look into it > more. > > > > > On Mon, May 18, 2015 at 9:57 PM, Benjamin > > Marzinski > > > > > <[2][4][5][6][7]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a>> <div><div class="h5">> wrote: > > > > > > > > > > On Mon, May 18, 2015 at 02:09:27PM > +0530, > > Tejaswini > > > Poluri > > > > wrote: > > > > > > Hii, > > > > > > We are trying to test multipath > setup in > > our > > > target and > > > > tried the > > > > > various > > > > > > commands of multipathd demaon and > we find > > the > > > following > > > > error: > > > > > > root@x86-generic-64:~# multipathd > -k"fail > > path > > > sdc"; > > > > multipathd > > > > > > -k'reinstate path > > > > > > sdc'; multipathd -k"show paths"; > > > > > > [ 3962.708523] device-mapper: > multipath: > > Failing > > > > path 8:32. > > > > > > ok > > > > > > ok > > > > > > hcil dev dev_t pri dm_st > chk_st > > next_check > > > > > > 4:0:0:1 sdc 8:32 1 > [active][faulty] > > .......... > > > 1/20 > > > > <<<=== > > > > > CHECK > > > > > > 5:0:0:1 sdd 8:48 1 > [active][ready] > > XX........ > > > 4/20 > > > > > > sdc path becomes [active][ready] > only > > after the > > > polling > > > > interval > > > > > but not > > > > > > immediately after the reinstate > path > > command. > > > > > > I am observing this in latest > multipath > > tools in > > > ubuntu > > > > machine > > > > > as well. > > > > > > Please let me know if its a known > issue or > > if I > > > am doing > > > > > something wrong. > > > > > > Regards. > > > > > > Tejaswini > > > > > > > > > > the reinstate command is supposed to > reinstate > > the > > > device > > > > with the > > > > > kernel, and it does that. The checker > state > > doesn't > > > change > > > > until the > > > > > next time that the path is checked. I > agree > > that it's > > > odd > > > > that the > > > > > check state switches to faulty as soon > as you > > fail the > > > path, > > > > but it > > > > > doesn't switch back until the next check > after > > you > > > reinistate > > > > it. > > > > > > > > > > The issue is that multipathd needs to > override > > the > > > checker > > > > output, > > > > > so that a failed path won't be > immeditately > > > reinstated. Once > > > > the > > > > > path comes back, multipathd wants to > record the > > switch > > > in the > > > > checker > > > > > thread, so that it can refresh path > information > > what > > > wasn't > > > > > automatically done when the path was > > reinstated. > > > However, it > > > > may make > > > > > more sense to have a different checker > state > > for when > > > the > > > > device is > > > > > in the failed state, so that it's > obvious that > > the > > > checker > > > > state is > > > > > being overruled. > > > > > > > > > > -Ben > > > > > > > > > > > -- > > > > > > dm-devel mailing list </div></div>> > > > > > [3][5][6][7][8]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > > > > > > > > [4][6][7][8][9]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > > > > > > > > -- > > > > > dm-devel mailing list > > > > > [5][7][8][9][10]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > > > > > > > [6][8][9][10][11]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > > > > > > > > References > > > > > > > > > > Visible links > > > > > 1. > mailto:[9][10][11][12]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > > > > 2. > mailto:[10][11][12][13]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > > > 3. > mailto:[11][12][13][14]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > > > 4. > > > > [12][13][14][15]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > > > 5. > mailto:[13][14][15][16]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > > > 6. > > > > [14][15][16][17]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > > > > > > References > > > > > > > > Visible links > > > > 1. mailto:[16][17][18]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > > > 2. mailto:[17][18][19]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > > 3. mailto:[18][19][20]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > > > 4. mailto:[19][20][21]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > > 5. mailto:[20][21][22]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > > 6. > [21][22][23]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > > 7. mailto:[22][23][24]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > > 8. > [23][24][25]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > > 9. mailto:[24][25][26]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > > > 10. mailto:[25][26][27]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > > 11. mailto:[26][27][28]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > > 12. > [27][28][29]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > > 13. mailto:[28][29][30]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > > 14. > [29][30][31]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > > > > References > > > > > > Visible links > > > 1. mailto:[31][32]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > 2. mailto:[32][33]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > > 3. mailto:[33][34]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > 4. mailto:[34][35]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > > 5. mailto:[35][36]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > 6. mailto:[36][37]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > 7. [37][38]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > 8. mailto:[38][39]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > 9. [39][40]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > 10. mailto:[40][41]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > > 11. mailto:[41][42]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > 12. mailto:[42][43]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > 13. [43][44]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > 14. mailto:[44][45]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > 15. [45][46]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > 16. mailto:[46][47]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > > 17. mailto:[47][48]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > 18. mailto:[48][49]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > > 19. mailto:[49][50]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > 20. mailto:[50][51]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > 21. [51][52]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > 22. mailto:[52][53]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > 23. [53][54]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > 24. mailto:[54][55]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > > 25. mailto:[55][56]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > > 26. mailto:[56][57]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > 27. [57][58]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > 28. mailto:[58][59]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > > 29. [59][60]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > > > References > > > > Visible links > > 1. mailto:[61]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 2. mailto:[62]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 3. mailto:[63]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 4. mailto:[64]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 5. mailto:[65]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 6. mailto:[66]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 7. mailto:[67]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 8. [68]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 9. mailto:[69]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 10. [70]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 11. mailto:[71]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 12. mailto:[72]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 13. mailto:[73]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 14. [74]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 15. mailto:[75]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 16. [76]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 17. mailto:[77]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 18. mailto:[78]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 19. mailto:[79]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 20. mailto:[80]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 21. mailto:[81]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 22. [82]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 23. mailto:[83]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 24. [84]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 25. mailto:[85]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 26. mailto:[86]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 27. mailto:[87]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 28. [88]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 29. mailto:[89]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 30. [90]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 31. mailto:[91]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 32. mailto:[92]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 33. mailto:[93]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 34. mailto:[94]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 35. mailto:[95]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 36. mailto:[96]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 37. [97]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 38. mailto:[98]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 39. [99]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 40. mailto:[100]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 41. mailto:[101]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 42. mailto:[102]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 43. [103]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 44. mailto:[104]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 45. [105]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 46. mailto:[106]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 47. mailto:[107]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 48. mailto:[108]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 49. mailto:[109]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 50. mailto:[110]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 51. [111]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 52. mailto:[112]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 53. [113]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 54. mailto:[114]<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > > 55. mailto:[115]<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > > 56. mailto:[116]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 57. [117]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > 58. mailto:[118]<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > > 59. [119]<a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > > References > > Visible links > 1. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 2. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 3. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 4. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 5. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 6. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 7. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 8. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 9. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 10. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 11. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 12. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 13. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 14. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 15. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 16. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 17. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 18. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 19. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 20. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 21. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 22. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 23. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 24. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 25. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 26. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 27. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 28. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 29. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 30. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 31. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 32. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 33. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 34. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 35. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 36. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 37. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 38. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 39. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 40. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 41. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 42. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 43. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 44. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 45. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 46. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 47. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 48. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 49. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 50. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 51. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 52. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 53. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 54. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 55. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 56. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 57. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 58. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 59. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 60. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 61. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 62. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 63. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 64. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 65. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 66. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 67. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 68. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 69. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 70. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 71. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 72. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 73. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 74. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 75. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 76. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 77. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 78. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 79. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 80. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 81. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 82. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 83. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 84. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 85. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 86. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 87. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 88. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 89. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 90. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 91. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 92. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 93. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 94. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 95. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 96. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 97. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 98. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 99. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 100. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 101. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 102. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 103. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 104. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 105. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 106. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 107. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 108. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 109. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 110. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 111. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 112. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 113. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 114. mailto:<a href="mailto:tejaswinipoluri3@gmail.com">tejaswinipoluri3@gmail.com</a> > 115. mailto:<a href="mailto:bmarzins@redhat.com">bmarzins@redhat.com</a> > 116. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 117. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> > 118. mailto:<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a> > 119. <a href="https://www.redhat.com/mailman/listinfo/dm-devel" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/dm-devel</a> </blockquote></div> </div>