search for: xxxnsby

...> > trust, depending on which wins the race more often? Say if kernel wants a > > ens3npry name while userspace wants it named as ens4. > > > > -Siwei > > With this approach kernel will deny attempts by userspace to rename > slaves. Slaves will always be named XXXnsby and XXnpry. Master renames > will rename both slaves. > > It seems pretty solid to me, the only issue is that in theory userspace > can use a name like XXXnsby for something else. But this seems unlikely. Similar schemes (with kernel providing naming) were also previously rejected ups...

...> How do users know which name to > trust, depending on which wins the race more often? Say if kernel wants a > ens3npry name while userspace wants it named as ens4. > > -Siwei With this approach kernel will deny attempts by userspace to rename slaves. Slaves will always be named XXXnsby and XXnpry. Master renames will rename both slaves. It seems pretty solid to me, the only issue is that in theory userspace can use a name like XXXnsby for something else. But this seems unlikely. > > > > > I don't like the idea to delay exposing failover master > > &gt...

...depending on which wins the race more often? Say if kernel wants a > > > ens3npry name while userspace wants it named as ens4. > > > > > > -Siwei > > With this approach kernel will deny attempts by userspace to rename > > slaves. Slaves will always be named XXXnsby and XXnpry. Master renames > > will rename both slaves. > > > > It seems pretty solid to me, the only issue is that in theory userspace > > can use a name like XXXnsby for something else. But this seems unlikely. > > > > > > > > > I don't li...

Sorry for replying to this ancient thread. There was some remaining issue that I don't think the initial net_failover patch got addressed cleanly, see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268 The renaming of 'eth0' to 'ens4' fails because the udev userspace was not specifically writtten for such kernel automatic enslavement. Specifically, if it is a bond