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, Dec 29, 7:57 AM
Unknown Object (File)
Nov 22 2024, 8:30 PM
Unknown Object (File)
Nov 22 2024, 8:30 PM
Unknown Object (File)
Nov 22 2024, 8:29 PM
Unknown Object (File)
Nov 22 2024, 8:06 PM
Unknown Object (File)
Oct 13 2024, 9:13 AM
Unknown Object (File)
Sep 17 2024, 5:05 PM
Unknown Object (File)
Sep 8 2024, 8:09 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 Skipped
Unit
Tests Skipped
Build Status
Buildable 16105