[Gluster-users] Glusterfs 4.1.6

[Amudhan P]

Thank you, it works as expected.

On Thu, Jan 3, 2019 at 5:08 PM Ashish Pandey <aspandey at redhat.com> wrote:

> Hi,
>
> Some of the the steps provided by you are not correct.
> You should have used reset-brick command which was introduced for the same
> task you wanted to do.
>
> <https://docs.gluster.org/en/v3/release-notes/3.9.0/>
> https://docs.gluster.org/en/v3/release-notes/3.9.0/
>
> Although your thinking was correct but replacing a faulty disk requires
> some of the additional task which this command
> will do automatically.
>
> Step 1 :- kill pid of the faulty brick in node  >>>>>> This should be done
> using "reset-brick start" command. follow the steps provided in link.
> Step 2 :- running volume status, shows "N/A" under 'pid' & 'TCP port'
> Step 3 :- replace disk and mount new disk in same mount point where the
> old disk was mounted
> Step 4 :- run command "gluster v start volname force" >>>>>>>>>>>> This
> should be done using "reset-brick commit force" command. This will trigger
> the heal.  Follow the link.
> Step 5 :- running volume status,  shows "N/A" under 'pid' & 'TCP port'
>
> ---
> Ashish
>
> ------------------------------
> *From: *"Amudhan P" <amudhan83 at gmail.com>
> *To: *"Gluster Users" <gluster-users at gluster.org>
> *Sent: *Thursday, January 3, 2019 4:25:58 PM
> *Subject: *[Gluster-users] Glusterfs 4.1.6
>
> Hi,
>
> I am working on Glusterfs 4.1.6 on a test machine. I am trying to replace
> a faulty disk and below are the steps I did but wasn't successful with that.
>
> 3 Nodes, 2 disks per node, Disperse Volume 4+2 :-
> Step 1 :- kill pid of the faulty brick in node
> Step 2 :- running volume status, shows "N/A" under 'pid' & 'TCP port'
> Step 3 :- replace disk and mount new disk in same mount point where the
> old disk was mounted
> Step 4 :- run command "gluster v start volname force"
> Step 5 :- running volume status,  shows "N/A" under 'pid' & 'TCP port'
>
> expected behavior was a new brick process & heal should have started.
>
> following above said steps 3.10.1 works perfectly, starting a new brick
> process and heal begins.
> But the same step not working in 4.1.6, Did I miss any steps? what should
> be done?
>
> Amudhan
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190103/2a5b9439/attachment.html>