[ovirt-users] Re: Removed FC LUN causes multipath to spam syslog
Removal of LUN is pure linux task.I would go like this:1. Set the storage domain in maintenance2. Detach the storage domain3. I'm not sure if any LVM tasks should be done manually or are done by the Engine4. Add the wwid into multipath blacklist 5. Remove all paths (sdXYZ)6. Unzone the LUN Best Regards,Strahil Nikolov On Fri, Mar 5, 2021 at 15:52, Juhani Rautiainen wrote: Hi! I had already booted the first node so I tried this on the second node. After cleaning up with dmsetup I ran ansible script again. It claimed success put multipathd was still checking for paths. I tried to do 'systemctl reload multipathd' but instead did restart (too quick fingers). Anyway it worked. There was some kind of hiccup because of that as the engine seemed to re-activate the node. No hosts went down so in the end it worked. Thanks for the help, Juhani On Fri, Mar 5, 2021 at 1:46 PM Vojtech Juranek wrote: > > On Friday, 5 March 2021 12:16:56 CET Juhani Rautiainen wrote: > > Hi! > > > > Ansible script fails and reason seems to be those stale DM links. We > > are currently still in 4.3.10 as I wanted to do this change before the > > upgrade to 4.4. We have SHE and it is currently on a 3PAR disk. When > > we upgrade we can do the SHE change at the same time as I didn't want > > to do two SHE restores (1st in 4.3 and then in 4.4). As there wasn't > > any hint how you can remove those stale DM links the best solution > > probably is to put nodes in maintenance and reboot them. > > you can remove the stale links by > > dmsetup remove -f /dev/mapper/ > > > > BTW I did dezone those disks after I had removed them from oVirt UI. I > > mean you can't remove them while they are still on oVirt? > > if the LUN is on target where no other LUN are used by oVirt, multipath > devices should be removed and vdsm should be logged out from the tergat (at > least on recent oVirt release). If you still use other LUNs from the storage > server on the host (as part of other storage domains), there's no point in > removing the LUN as it will be discovered again, as vdsm does rescans of the > storage in various flows. So the flow has to be > > 1. remove storage domain using the LUN > 2. unzone the LUN on storage server > 3. remove corresponding multipath devices from the hosts > > There can be some improvement as proposed by Nir under BZ #1310330 like > blacklisting removed devices, but this makes everything more complex. It may > be considered and implemented in the future, but unfortunately not available > right now. > > > Thanks, > > Juhani > > > > On Fri, Mar 5, 2021 at 11:02 AM Vojtech Juranek wrote: > > > On Friday, 5 March 2021 09:02:51 CET Juhani Rautiainen wrote: > > > > Hi! > > > > > > > > We are running ovirt 4.3.10 and we are migrating from 3PAR to Dell SC. > > > > I've managed to transfer disks from one LUN away and removed it (put > > > > it in maintenanced, detached it and removed it). Now multipath seems > > > > to spam the logs for missing disks. How can I stop this? > > > > > > you can remove multipath device either manually or you can use ansible > > > playbook for it, please try one attached to > > > > > > https://bugzilla.redhat.com/1310330 > > > > > > see > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1310330#c56 > > > > > > how to use it. You also have to change `hosts` to group of hosts you want > > > to test on and remove `connection: local` > > > > > > If it fail, please report back. It can fail as there are stale DM links, > > > see > > > > > > bugzilla.redhat.com/1928041 > > > > > > this was fixed recently and should be in next oVirt relase. > > > > > > Alternatively, you can reboot the host. > > > > > > > Mar 5 09:58:58 ovirt01 multipathd: 360002ac0027257b9: > > > > sdr - tur checker reports path is down > > > > Mar 5 09:58:59 ovirt01 multipathd: 360002ac0027257b9: > > > > sdh - tur checker reports path is down > > > > > > > > And so on. Any idea how I can quiet this? And why didn't oVirt do this > > > > automatically? > > > > > > to be able to remove multipath devices, the LUN has to be unzoned first on > > > the storage server and this cannot be done by oVirt, as oVirt doesn't > > > manage the storage server - this has to be done by administator of > > > storage server which has subsequently remove multipath devices from the > > > hosts e.g. by using ansible script mention above. > > > > > > > Thanks, > > > > Juhani > > > > ___ > > > > Users mailing list -- users@ovirt.org > > > > To unsubscribe send an email to users-le...@ovirt.org > > > > Privacy Statement: https://www.ovirt.org/privacy-policy.html > > > > oVirt Code of Conduct: > > > > https://www.ovirt.org/community/about/community-guidelines/ List > > > > Archives: > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/QLENIZGWGU > > > > U4J > > > > OETXNQCNIK5GTU2EFVZ/ > ___ Users mailing list --
[ovirt-users] Re: Gluster volume engine stuck in healing with 1 unsynched entry & HostedEngine paused
If it's a VM image, just use dd to read the whole file.dd if=VM_imageof=/dev/null bs=10M status=progress Best Regards,Strahil Nikolov On Fri, Mar 5, 2021 at 15:48, Alex K wrote: ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RJO7EVEW2C3P7EYTAIXZVIC7JBSEXM3C/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/7Y6SXCZDIYQH3MST72CX5FCGZW5QQKMR/
[ovirt-users] Re: snapshot solution: Existing snapshots that were taken after this one will be erased.
Commiting a snapshot means that you want to revert to that state, which means that all data afterwards is lost.Even if you keep the latest snapshot, it won't be usefull.For example you got the following: Install -> snap1 -> some data -> snap2 -> some data -> snap3 -> some data -> Current State If you revert to snap2 you will have the following:Install -> snap1 -> some data -> snap2 -> some data -> Current State (you always have some extra data generated - for example system logs) As you can see, you can't use snap3 as you got some data after powering up the VM after the restore to snap2 and you will loose that. Best Regards,Strahil Nikolov On Fri, Mar 5, 2021 at 8:32, dhanaraj.ramesh--- via Users wrote: Hi Team, when I want to commit the older snapshots I'm getting warning stating " Existing snapshots that were taken after this one will be erased.". is there any way we can retain the latest snapshots as is in the chain? I knew cloning and template export options are there to secure that latest snapshot data but these are will consume additional space in storage and take time. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Y5PQGBQXWTJ6O3NI6ZIV2QVEHWML7RVA/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/I47GULR3I5FPMD2NXJ44EI5IRCUXEDPV/
[ovirt-users] Re: Removed FC LUN causes multipath to spam syslog
Hi! I had already booted the first node so I tried this on the second node. After cleaning up with dmsetup I ran ansible script again. It claimed success put multipathd was still checking for paths. I tried to do 'systemctl reload multipathd' but instead did restart (too quick fingers). Anyway it worked. There was some kind of hiccup because of that as the engine seemed to re-activate the node. No hosts went down so in the end it worked. Thanks for the help, Juhani On Fri, Mar 5, 2021 at 1:46 PM Vojtech Juranek wrote: > > On Friday, 5 March 2021 12:16:56 CET Juhani Rautiainen wrote: > > Hi! > > > > Ansible script fails and reason seems to be those stale DM links. We > > are currently still in 4.3.10 as I wanted to do this change before the > > upgrade to 4.4. We have SHE and it is currently on a 3PAR disk. When > > we upgrade we can do the SHE change at the same time as I didn't want > > to do two SHE restores (1st in 4.3 and then in 4.4). As there wasn't > > any hint how you can remove those stale DM links the best solution > > probably is to put nodes in maintenance and reboot them. > > you can remove the stale links by > > dmsetup remove -f /dev/mapper/ > > > > BTW I did dezone those disks after I had removed them from oVirt UI. I > > mean you can't remove them while they are still on oVirt? > > if the LUN is on target where no other LUN are used by oVirt, multipath > devices should be removed and vdsm should be logged out from the tergat (at > least on recent oVirt release). If you still use other LUNs from the storage > server on the host (as part of other storage domains), there's no point in > removing the LUN as it will be discovered again, as vdsm does rescans of the > storage in various flows. So the flow has to be > > 1. remove storage domain using the LUN > 2. unzone the LUN on storage server > 3. remove corresponding multipath devices from the hosts > > There can be some improvement as proposed by Nir under BZ #1310330 like > blacklisting removed devices, but this makes everything more complex. It may > be considered and implemented in the future, but unfortunately not available > right now. > > > Thanks, > > Juhani > > > > On Fri, Mar 5, 2021 at 11:02 AM Vojtech Juranek wrote: > > > On Friday, 5 March 2021 09:02:51 CET Juhani Rautiainen wrote: > > > > Hi! > > > > > > > > We are running ovirt 4.3.10 and we are migrating from 3PAR to Dell SC. > > > > I've managed to transfer disks from one LUN away and removed it (put > > > > it in maintenanced, detached it and removed it). Now multipath seems > > > > to spam the logs for missing disks. How can I stop this? > > > > > > you can remove multipath device either manually or you can use ansible > > > playbook for it, please try one attached to > > > > > > https://bugzilla.redhat.com/1310330 > > > > > > see > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1310330#c56 > > > > > > how to use it. You also have to change `hosts` to group of hosts you want > > > to test on and remove `connection: local` > > > > > > If it fail, please report back. It can fail as there are stale DM links, > > > see > > > > > > bugzilla.redhat.com/1928041 > > > > > > this was fixed recently and should be in next oVirt relase. > > > > > > Alternatively, you can reboot the host. > > > > > > > Mar 5 09:58:58 ovirt01 multipathd: 360002ac0027257b9: > > > > sdr - tur checker reports path is down > > > > Mar 5 09:58:59 ovirt01 multipathd: 360002ac0027257b9: > > > > sdh - tur checker reports path is down > > > > > > > > And so on. Any idea how I can quiet this? And why didn't oVirt do this > > > > automatically? > > > > > > to be able to remove multipath devices, the LUN has to be unzoned first on > > > the storage server and this cannot be done by oVirt, as oVirt doesn't > > > manage the storage server - this has to be done by administator of > > > storage server which has subsequently remove multipath devices from the > > > hosts e.g. by using ansible script mention above. > > > > > > > Thanks, > > > > Juhani > > > > ___ > > > > Users mailing list -- users@ovirt.org > > > > To unsubscribe send an email to users-le...@ovirt.org > > > > Privacy Statement: https://www.ovirt.org/privacy-policy.html > > > > oVirt Code of Conduct: > > > > https://www.ovirt.org/community/about/community-guidelines/ List > > > > Archives: > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/QLENIZGWGU > > > > U4J > > > > OETXNQCNIK5GTU2EFVZ/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZVW6Y7DM2QXNBVZVF7L4MBCD7JL5GV7N/
[ovirt-users] Re: Gluster volume engine stuck in healing with 1 unsynched entry & HostedEngine paused
On Thu, Mar 4, 2021 at 8:59 PM wrote: > Hello again, > I've tried to heal the brick with latest-mtime, but I get the following: > > gluster volume heal engine split-brain latest-mtime > /80f6e393-9718-4738-a14a-64cf43c3d8c2/images/d5de54b6-9f8e-4fba-819b-ebf6780757d2/a48555f4-be23-4467-8a54-400ae7baf9d7 > Healing > /80f6e393-9718-4738-a14a-64cf43c3d8c2/images/d5de54b6-9f8e-4fba-819b-ebf6780757d2/a48555f4-be23-4467-8a54-400ae7baf9d7 > failed: File not in split-brain. > Volume heal failed. > you can try to run ls at the directory where the file which healing is pending resides. This might trigger the healing process of that file. > Should I try the solution described in this question, where we manually > remove the conflicting entry, triggering the heal operations? > > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/RPYIMSQCBYVQ654HYGBN5NCPRVCGRRYB/#H6EBSPL5XRLBUVZBE7DGSY25YFPIR2KY > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/CCRNM7N3FSUYXDHFP2XDMGAMKSHBMJQQ/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RJO7EVEW2C3P7EYTAIXZVIC7JBSEXM3C/
[ovirt-users] Re: Removed FC LUN causes multipath to spam syslog
On Friday, 5 March 2021 12:16:56 CET Juhani Rautiainen wrote: > Hi! > > Ansible script fails and reason seems to be those stale DM links. We > are currently still in 4.3.10 as I wanted to do this change before the > upgrade to 4.4. We have SHE and it is currently on a 3PAR disk. When > we upgrade we can do the SHE change at the same time as I didn't want > to do two SHE restores (1st in 4.3 and then in 4.4). As there wasn't > any hint how you can remove those stale DM links the best solution > probably is to put nodes in maintenance and reboot them. you can remove the stale links by dmsetup remove -f /dev/mapper/ > BTW I did dezone those disks after I had removed them from oVirt UI. I > mean you can't remove them while they are still on oVirt? if the LUN is on target where no other LUN are used by oVirt, multipath devices should be removed and vdsm should be logged out from the tergat (at least on recent oVirt release). If you still use other LUNs from the storage server on the host (as part of other storage domains), there's no point in removing the LUN as it will be discovered again, as vdsm does rescans of the storage in various flows. So the flow has to be 1. remove storage domain using the LUN 2. unzone the LUN on storage server 3. remove corresponding multipath devices from the hosts There can be some improvement as proposed by Nir under BZ #1310330 like blacklisting removed devices, but this makes everything more complex. It may be considered and implemented in the future, but unfortunately not available right now. > Thanks, > Juhani > > On Fri, Mar 5, 2021 at 11:02 AM Vojtech Juranek wrote: > > On Friday, 5 March 2021 09:02:51 CET Juhani Rautiainen wrote: > > > Hi! > > > > > > We are running ovirt 4.3.10 and we are migrating from 3PAR to Dell SC. > > > I've managed to transfer disks from one LUN away and removed it (put > > > it in maintenanced, detached it and removed it). Now multipath seems > > > to spam the logs for missing disks. How can I stop this? > > > > you can remove multipath device either manually or you can use ansible > > playbook for it, please try one attached to > > > > https://bugzilla.redhat.com/1310330 > > > > see > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1310330#c56 > > > > how to use it. You also have to change `hosts` to group of hosts you want > > to test on and remove `connection: local` > > > > If it fail, please report back. It can fail as there are stale DM links, > > see > > > > bugzilla.redhat.com/1928041 > > > > this was fixed recently and should be in next oVirt relase. > > > > Alternatively, you can reboot the host. > > > > > Mar 5 09:58:58 ovirt01 multipathd: 360002ac0027257b9: > > > sdr - tur checker reports path is down > > > Mar 5 09:58:59 ovirt01 multipathd: 360002ac0027257b9: > > > sdh - tur checker reports path is down > > > > > > And so on. Any idea how I can quiet this? And why didn't oVirt do this > > > automatically? > > > > to be able to remove multipath devices, the LUN has to be unzoned first on > > the storage server and this cannot be done by oVirt, as oVirt doesn't > > manage the storage server - this has to be done by administator of > > storage server which has subsequently remove multipath devices from the > > hosts e.g. by using ansible script mention above. > > > > > Thanks, > > > Juhani > > > ___ > > > Users mailing list -- users@ovirt.org > > > To unsubscribe send an email to users-le...@ovirt.org > > > Privacy Statement: https://www.ovirt.org/privacy-policy.html > > > oVirt Code of Conduct: > > > https://www.ovirt.org/community/about/community-guidelines/ List > > > Archives: > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/QLENIZGWGU > > > U4J > > > OETXNQCNIK5GTU2EFVZ/ signature.asc Description: This is a digitally signed message part. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UZLRKGUFWY5QLV5W2XMNZ3LNLPRKV2O5/
[ovirt-users] Re: Removed FC LUN causes multipath to spam syslog
Hi! Ansible script fails and reason seems to be those stale DM links. We are currently still in 4.3.10 as I wanted to do this change before the upgrade to 4.4. We have SHE and it is currently on a 3PAR disk. When we upgrade we can do the SHE change at the same time as I didn't want to do two SHE restores (1st in 4.3 and then in 4.4). As there wasn't any hint how you can remove those stale DM links the best solution probably is to put nodes in maintenance and reboot them. BTW I did dezone those disks after I had removed them from oVirt UI. I mean you can't remove them while they are still on oVirt? Thanks, Juhani On Fri, Mar 5, 2021 at 11:02 AM Vojtech Juranek wrote: > > On Friday, 5 March 2021 09:02:51 CET Juhani Rautiainen wrote: > > Hi! > > > > We are running ovirt 4.3.10 and we are migrating from 3PAR to Dell SC. > > I've managed to transfer disks from one LUN away and removed it (put > > it in maintenanced, detached it and removed it). Now multipath seems > > to spam the logs for missing disks. How can I stop this? > > you can remove multipath device either manually or you can use ansible > playbook for it, please try one attached to > > https://bugzilla.redhat.com/1310330 > > see > > https://bugzilla.redhat.com/show_bug.cgi?id=1310330#c56 > > how to use it. You also have to change `hosts` to group of hosts you want to > test on and remove `connection: local` > > If it fail, please report back. It can fail as there are stale DM links, see > > bugzilla.redhat.com/1928041 > > this was fixed recently and should be in next oVirt relase. > > Alternatively, you can reboot the host. > > > Mar 5 09:58:58 ovirt01 multipathd: 360002ac0027257b9: > > sdr - tur checker reports path is down > > Mar 5 09:58:59 ovirt01 multipathd: 360002ac0027257b9: > > sdh - tur checker reports path is down > > > > And so on. Any idea how I can quiet this? And why didn't oVirt do this > > automatically? > > to be able to remove multipath devices, the LUN has to be unzoned first on the > storage server and this cannot be done by oVirt, as oVirt doesn't manage the > storage server - this has to be done by administator of storage server which > has subsequently remove multipath devices from the hosts e.g. by using ansible > script mention above. > > > Thanks, > > Juhani > > ___ > > Users mailing list -- users@ovirt.org > > To unsubscribe send an email to users-le...@ovirt.org > > Privacy Statement: https://www.ovirt.org/privacy-policy.html > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ List Archives: > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/QLENIZGWGUU4J > > OETXNQCNIK5GTU2EFVZ/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IRGDSYIOBNKDCD3XX32TXLBBNYNH4IFB/
[ovirt-users] Re: Removed FC LUN causes multipath to spam syslog
On Friday, 5 March 2021 09:02:51 CET Juhani Rautiainen wrote: > Hi! > > We are running ovirt 4.3.10 and we are migrating from 3PAR to Dell SC. > I've managed to transfer disks from one LUN away and removed it (put > it in maintenanced, detached it and removed it). Now multipath seems > to spam the logs for missing disks. How can I stop this? you can remove multipath device either manually or you can use ansible playbook for it, please try one attached to https://bugzilla.redhat.com/1310330 see https://bugzilla.redhat.com/show_bug.cgi?id=1310330#c56 how to use it. You also have to change `hosts` to group of hosts you want to test on and remove `connection: local` If it fail, please report back. It can fail as there are stale DM links, see bugzilla.redhat.com/1928041 this was fixed recently and should be in next oVirt relase. Alternatively, you can reboot the host. > Mar 5 09:58:58 ovirt01 multipathd: 360002ac0027257b9: > sdr - tur checker reports path is down > Mar 5 09:58:59 ovirt01 multipathd: 360002ac0027257b9: > sdh - tur checker reports path is down > > And so on. Any idea how I can quiet this? And why didn't oVirt do this > automatically? to be able to remove multipath devices, the LUN has to be unzoned first on the storage server and this cannot be done by oVirt, as oVirt doesn't manage the storage server - this has to be done by administator of storage server which has subsequently remove multipath devices from the hosts e.g. by using ansible script mention above. > Thanks, > Juhani > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/QLENIZGWGUU4J > OETXNQCNIK5GTU2EFVZ/ signature.asc Description: This is a digitally signed message part. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WZ65BOYS47ULYGMNWHB7LDJ2T26L2DOR/
[ovirt-users] user portal
Dear all, I'm using ovirt 4.3.2 with its engine on a virtual machine. The nodes are all Centos 7.7. Both engine and hypervisor systems work on a 10.0.0.0 private network. Now I would like to let users access the ovirt web page (user portal) and for this I must necessarily add a second network interface to the engine by inserting a public ip. I can't use NAT. Can you give me any advice for this operation ? Can I add the network interface and then run engine-setup ? Will oVirt be accessible from both ip addresses at the end of this operation ? Lots of thanks. Enrico -- ___ Enrico BecchettiServizio di Calcolo e Reti Istituto Nazionale di Fisica Nucleare - Sezione di Perugia Via Pascoli,c/o Dipartimento di Fisica 06123 Perugia (ITALY) Phone:+39 075 5852777 Skype:enrico_becchetti Mail: Enrico.Becchettipg.infn.it __ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZW2SGNYGA4MEGUCA2ONQ3RVBRWIYMUJZ/
[ovirt-users] Removed FC LUN causes multipath to spam syslog
Hi! We are running ovirt 4.3.10 and we are migrating from 3PAR to Dell SC. I've managed to transfer disks from one LUN away and removed it (put it in maintenanced, detached it and removed it). Now multipath seems to spam the logs for missing disks. How can I stop this? Mar 5 09:58:58 ovirt01 multipathd: 360002ac0027257b9: sdr - tur checker reports path is down Mar 5 09:58:59 ovirt01 multipathd: 360002ac0027257b9: sdh - tur checker reports path is down And so on. Any idea how I can quiet this? And why didn't oVirt do this automatically? Thanks, Juhani ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/QLENIZGWGUU4JOETXNQCNIK5GTU2EFVZ/
