Bug 762544 (GLUSTER-812) - volumes are not started upon reboot after one of the interfaces are unselected from bonding
Summary: volumes are not started upon reboot after one of the interfaces are unselecte...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-812
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: 3.0.4
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-08 10:35 UTC by Raghavendra Bhat
Modified: 2010-04-10 07:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Raghavendra Bhat 2010-04-08 10:32:44 UTC 
Sometimes it says none of the volumes have been started except one. But the actual situation is vice-versa. i.e. all but one volumes have been started.
Comment 1 Raghavendra Bhat 2010-04-08 10:35:49 UTC 
There are 2 network interfaces(eth0 and eth1) in the first server. I unselected
one of the interfaces(tried both eth0 as wel as eth1) and configured it with a
separate IP address, and rebooted after updating the changes.But when the
server reboots the volumes are not started. Selecting all the volumes and giving start volume immedietly says none of the volumes are started. But most of the volumed are actually started except 2-3. Now selecting those non-started volumes and clicking start volume will also says that none of them have been started, whereas we can find that they have been started.
Note You need to log in before you can comment on or make changes to this bug.