Hi Konstantin, I also believe it's a mechanism that prevents ethernet devices from beeing randomly swapped at reboot, isn't it ? I'm actually willing that devices remain coherently and persistently named, but I admit the fact that MAC address is in there is annoying when we change motherboards..
Regards > -----Message d'origine----- > De : Konstantin Olchanski [mailto:[email protected]] > Envoyé : lundi 28 juillet 2014 21:08 > À : SCHAER Frederic > Cc : [email protected] > Objet : Re: udev persistent net rules erratic inconsistencies > > > > Hi, there - persistent-net.rules is a clever scheme to prevent your computer > from booting after you replace a burned out > motherboard. To disable it, run: > > > touch /etc/udev/rules.d/75-persistent-net-generator.rules > rm /etc/udev/rules.d/70-persistent-net.rules > > > K.O. > > > On Mon, Jul 28, 2014 at 09:35:17AM +0000, SCHAER Frederic wrote: > > Hi, > > > > >From time to time, we get reboot issues with some machines, and each time > > >it looks like there are duplicated persistent > rules for the Ethernet devices : > > > > > cat /etc/udev/rules.d/70-persistent-net.rules > > # This file was automatically generated by the /lib/udev/write_net_rules > > # program, run by the persistent-net-generator.rules rules file. > > # > > # You can modify it, as long as you keep each rule on a single > > # line, and change only the value of the NAME= key. > > > > # PCI device 0x8086:0x1521 (igb) (custom name provided by external tool) > > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > > ATTR{address}=="84:8f:69:fb:c1:2a", ATTR{type}=="1", > KERNEL=="eth*", NAME="em1" > > > > # PCI device 0x8086:0x1521 (igb) (custom name provided by external tool) > > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > > ATTR{address}=="84:8f:69:fb:c1:2b", ATTR{type}=="1", > KERNEL=="eth*", NAME="em2" > > > > > > # PCI device 0x8086:0x1521 (igb) (custom name provided by external tool) > > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > > ATTR{address}=="84:8f:69:fb:c1:2a", ATTR{type}=="1", > KERNEL=="eth*", NAME="eth0" > > > > # PCI device 0x8086:0x1521 (igb) (custom name provided by external tool) > > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > > ATTR{address}=="84:8f:69:fb:c1:2b", ATTR{type}=="1", > KERNEL=="eth*", NAME="eth1" > > > > The second set of rules seem to overwrite the first one, and then we get > > issues with our network config. > > This does not happen on all nodes, just apparently to some random ones, > > sometimes. > > I'm wondering if some of you might have faced and solved that erratic thing > > already ? > > > > We want to keep the emX scheme for nodes which support it... > > > > Thanks > > -- > Konstantin Olchanski > Data Acquisition Systems: The Bytes Must Flow! > Email: olchansk-at-triumf-dot-ca > Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
