[Gluster-users] Bad sectors on brick

[Niels de Vos]

On Mon, Oct 24, 2016 at 03:35:06PM +0200, Gandalf Corvotempesta wrote:
> 2016-10-24 11:29 GMT+02:00 Niels de Vos <ndevos at redhat.com>:
> > The filesystem on the brick will detect the problem, and most likely
> > aborts itself. Depending on the configuration (mount options, tune2fs)
> > the kernel will panic or mount the filesystem in read-only mode.
> >
> > When the filesystem becomes read-only, the brick process will log a
> > warning and exit.
> 
> So, gluster is able to handle a single bad sector. Kernel puts the FS
> in readonly and the brick process will exit.
> When the brick process exist, gluster detect the brick as missing and
> so on........

Yes, correct. But note that different filesystems can handle bad sectors
differently, read-only filesystems is the most common default though.

In 'man 8 mount' the option "errors=" describes the different values for
ext2/3/4. Configuring it to "continue" will most likely cause data
corruption or other bad problems and is definitely not advised ;-)

Niels
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20161024/e37bef5c/attachment.sig>