Search results

Udo, many thanks for your time, after conversion to full mesh cabling scheme, multipath seems now to be working fine! we've broadcom + e1000 nics on these nodes (some onboard and some on additional nic) btw we've never had any issue from nics prior to this kernel update.... actually we...

Hi, find attached logs extracted for 18.06 as you can see, we were working on fc cables, changing schema from direct attach to full mesh through dual fc switches really don't remember time of issue... waiting your suggestions... regards, Francesco

@trystan, we've checked... MTU is set to std 1500 bytes an all nics (phisycal or bridge / bonds) nics are mixed, 4 broadcom BCM5709 + 2 intel 82571EB any other suggestion?!? waiting.... regards, Francesco

@Kaya, actually no other suggestions to give! i still think multipath on shared storage is a good idea (for redundancy accessing lvm....) i need some time to check config of lvm filters on other installations.... i'll provide other info when availbale! bye francesco

@Kaya, from your config, i suppose you've named mpath devices in a non-std way (GRUPPOxx....) for lvm configuration.... PS: pls check your filter directive.... it seems me strange filter = [ "a|/dev/disk/by-id/.*|","a|mapper/*|", "r|.*|" ] may be the correct way is: filter = [...

ok, i'll keep this contact in mind! bye francesco

yes, the customer has an active subscription (basic but active!!) if you remember, in one of my first posts.... i was just pointing out that an update, released on payment subscription repositry was generating this issue.... bye francesco

rickygm, not my ability!! to be extremely sincere, Matteo solved this issue updating all the nodes and testing the configurations!! hoping all this to be helpful in the future!! best regards, francesco

Guys, latest updates, i confirm... after updating proxmox nodes (latest updates as i said in my previous post...) all seems running fine, Matteo (he's my customer's IT Manager) has applied all updates from the subscription repo.... then made an old kernels clean-up.... he used the attached...

@manu ... i've received notification from my customer that latest updates (done yesterday afternoon...) seems to solve this issue, i'll be on-site on next week so may be i can be more precise about versions of packages!! if you've requests about versions, tell me which infos may be helpful...

guys.... no one answering?? no one has suggestions?!? it seems me really strange!! where are developers?!? sure they reads the forums... i'm going to remember them that all was running fine prior to kernel updates!! that kernel updates were released on subscription repos!! not the public or...

@rickygm attached to this post you'll find the result of the commands you've suggested.... waiting, regards, francesco

guys, googling around i've found this article: https://access.redhat.com/discussions/1307143 it refers to another page with a solution (this page is covered under redhat subscription section of the KB) i'm unable to access this because i've not this kind of access on redhat site. so, if...

@rickygm on-site just now, for operative needings, unable to operate on node1 of the cluster (the original presenting issue!) btw, we've total four nodes, node3 has been updated at the same s/w level of node1.... so... before touching node3 the situation was the same as node1 (same s/w...

@rickygm first of all, many thanks again for your time!! extracted from the apening post of this thread: we've a 3 nodes cluster running on v.4.x using a shared storage base on HP MSA2040FC... our issue have started after update of 1 node.... we've done upgrades to packages using the...

@rickygm on-site just now!! as you requested me, going to retrieve infos..... --------------------------------------------------------- dpkg -s multipath-tools | grep Version returns: Version: 0.5.0-6+deb8u2 --------------------------------------------------------- multipath -ll...

still no solution on our side.... i'll be on-site tomorrow, i'll try some actions i'm minding on.... keep you all updated! regards, francesco

@rickygm, actually unable to give you this info... may be Matteo (he's the it manager at customer site) will be able to post this info next monday! many thanks again for your attention, regards, francesco

version 0.1.113 has worked for me also, other versions like 0.1.102 stalls or gets the VM into BSOD... regards, francesco

@rickygm, as i promise... i've tested your fix against one of the servers... no changes... just after reboot, if you run: multipath -ll nothing is reported as active multipath the only way to see something reported is to run multipath -d but this only confirms config file...