Re: Bad sectors on brick

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx>:
> > 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

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux