Page MenuHomeFreeBSD

Make lagg creation more fault tolerant
ClosedPublic

Authored by gallatin on Apr 11 2018, 5:49 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Apr 12, 5:32 AM
Unknown Object (File)
Sat, Apr 11, 10:42 PM
Unknown Object (File)
Wed, Apr 8, 3:51 AM
Unknown Object (File)
Tue, Apr 7, 9:18 PM
Unknown Object (File)
Thu, Apr 2, 9:39 PM
Unknown Object (File)
Thu, Mar 26, 8:24 AM
Unknown Object (File)
Thu, Mar 26, 1:32 AM
Unknown Object (File)
Wed, Mar 25, 9:55 AM
Subscribers

Details

Summary
  • Warn, don't exit, when SIOCSLAGGPORT returns an error.

When we exit with an error during lagg creation, a single failed NIC (which no longer attaches) can prevent lagg creation and other configuration, such as adding an IPv4 address, and thus leave a machine unreachable.

  • Preserve non-EEXISTS errors for exit status from SIOCSLAGGPORT, in case scripts are looking for it. Hopefully this can be extended if other parts of ifconfig can allow a "soft" failure.
  • Improve the warning message to mention what lagg and what member are problematic.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable