Bug 962875 - Entire volume DOSes itself when a node reboots and runs fsck on its bricks while network is up
Entire volume DOSes itself when a node reboots and runs fsck on its bricks wh...
Product: GlusterFS
Classification: Community
Component: core (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: bugs@gluster.org
Depends On:
  Show dependency treegraph
Reported: 2013-05-14 12:34 EDT by hans
Modified: 2015-10-22 11:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-10-22 11:40:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description hans 2013-05-14 12:34:04 EDT
Description of problem:

A node in a distributed-replicate setup went down (reason irrelevant) and came back up, starting fsck on its bricks. During these (long) fsck's the machine's network was up.
The other nodes tried to reconnect to the node with problems so hard that the entire volume was unavailable. They basically DOSed themselves.

Version-Release number of selected component (if applicable):

Comment 1 Kaleb KEITHLEY 2015-10-22 11:40:20 EDT
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.

Note You need to log in before you can comment on or make changes to this bug.