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)
Wed, Sep 16, 2:18 PM
Unknown Object (File)
Tue, Sep 15, 12:15 PM
Unknown Object (File)
Sat, Sep 12, 11:13 PM
Unknown Object (File)
Fri, Sep 11, 12:49 PM
Unknown Object (File)
Sat, Sep 5, 9:04 AM
Unknown Object (File)
Sat, Sep 5, 2:42 AM
Unknown Object (File)
Fri, Sep 4, 8:29 PM
Unknown Object (File)
Fri, Sep 4, 8:11 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