Rahul,
The log snippets don't tell the complete story. Could you give the full log files may be as a tar file to debug this further.
Pranith
----- Original Message -----
> From: "Rahul51 S" <rahul51.s at tcs.com>
> To: gluster-devel at nongnu.org, gluster-users at gluster.org, gluster-users-bounces at gluster.org
> Sent: Thursday, August 8, 2013 8:12:59 PM
> Subject: [Gluster-devel] not able to restart the brick for distributed volume
>
> Hi All,
>
> I am facing issues restarting the gluster volume. When I start the volume
> after stopping it, the gluster fails to start the volume
>
> Below is the message that I get on CLI
>
> /root> gluster volume start _home
> volume start: _home: failed: Commit failed on localhost. Please check the log
> file for more details.
>
> Logs says that it was unable to start the brick
>
> [2013-08-08 14:19:42.280852] I [glusterd-pmap.c:271:pmap_registry_remove]
> 0-pmap: removing brick (null) on port 49160
> [2013-08-08 14:19:42.283583] E [glusterd-utils.c:4023:glusterd_brick_start]
> 0-management: Unable to start brick 192.168.24.80:/.krfs/_home
> [2013-08-08 14:19:42.283637] E [glusterd-syncop.c:830:gd_sync_task_begin]
> 0-management: Commit of operation 'Volume Start' failed on localhost
>
> and the gluster volume remains as stopped
>
> root at ksc-base-unit0:/.krfs> gluster volume info _home
>
> Volume Name: _home
> Type: Distribute
> Volume ID: e6ab94d8-30ec-469e-830f-4c124e360ca1
> Status: Stopped
> Number of Bricks: 1
> Transport-type: tcp
> Bricks:
> Brick1: 192.168.24.80:/.krfs/_home
> Options Reconfigured:
> nfs.register-with-portmap: on
>
>
> Could you please shed some light on this
>
>
> Regards
> Rahul Shrivastava
>
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> https://lists.nongnu.org/mailman/listinfo/gluster-devel
>
