Bug 962875 - Entire volume DOSes itself when a node reboots and runs fsck on its bricks while network is up
Summary: Entire volume DOSes itself when a node reboots and runs fsck on its bricks wh...
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: pre-release
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-14 16:34 UTC by hans
Modified: 2015-10-22 15:40 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-10-22 15:40:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description hans 2013-05-14 16:34:04 UTC 
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):

3.3git-v3.3.2qa2-3-g3490689
Comment 1 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC 
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.