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)
Sat, Dec 20, 7:20 AM
Unknown Object (File)
Thu, Dec 11, 6:30 PM
Unknown Object (File)
Thu, Dec 11, 12:46 AM
Unknown Object (File)
Wed, Dec 10, 9:59 PM
Unknown Object (File)
Fri, Nov 28, 2:16 PM
Unknown Object (File)
Nov 20 2025, 9:39 PM
Unknown Object (File)
Nov 20 2025, 9:38 PM
Unknown Object (File)
Nov 20 2025, 9:38 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