Page MenuHomeFreeBSD

Make lagg creation more fault tolerant
ClosedPublic

Authored by gallatin on Apr 11 2018, 5:49 PM.
Tags
None
Referenced Files
F169777662: D15046.id41567.diff
Wed, Sep 2, 1:11 PM
F169704209: D15046.id41567.diff
Wed, Sep 2, 8:23 AM
Unknown Object (File)
Tue, Sep 1, 12:14 PM
Unknown Object (File)
Mon, Aug 31, 12:42 PM
Unknown Object (File)
Mon, Aug 31, 9:38 AM
Unknown Object (File)
Mon, Aug 31, 3:00 AM
Unknown Object (File)
Sun, Aug 30, 11:16 AM
Unknown Object (File)
Thu, Aug 27, 1:51 PM
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