Hi,
thx Ashish for the clarification. Just another question... so the
commands in case of a hdd (lets say sdd) failure and identical brick
paths (mount: /gluster/bricksdd1) should look like this:
gluster volume reset-brick $volname /gluster/bricksdd1 start
>> change hdd, create partition & filesy
comments inline
- Original Message -
From: "Hu Bert"
To: "Ashish Pandey"
Cc: "Gluster Users"
Sent: Monday, January 7, 2019 12:41:29 PM
Subject: Re: [Gluster-users] Glusterfs 4.1.6
Hi Ashish & all others,
if i may jump in... i have a little question if that's ok?
replace-brick
Hi Ashish & all others,
if i may jump in... i have a little question if that's ok?
replace-brick and reset-brick are different commands for 2 distinct
problems? I once had a faulty disk (=brick), it got replaced
(hot-swap) and received the same identifier (/dev/sdd again); i
followed this guide:
Hi,
i would start doing some checks like: "(Input/output error)" seems returned
by the operating system, this happens for instance trying to access a file
system which is on a device not available so i would check the network
connectivity between the client to servers and server to server during
