[Gluster-users] Bad sectors on brick

Ravishankar N ravishankar at redhat.com
Mon Oct 24 09:57:42 UTC 2016

On 10/24/2016 02:59 PM, Niels de Vos wrote:
> On Mon, Oct 24, 2016 at 02:24:48PM +0530, Ravishankar N wrote:
>> On 10/24/2016 02:02 PM, Gandalf Corvotempesta wrote:
>>> Hi,
>>> how gluster manage a single bad sector on a disk/brick? It will kick
>>> out the whole brick?
>> Gluster does not manage sectors, it will just  propagate the error
>> returned by the on-disk file system for that syscall to the application.
>>> What if the single bad sector makes a single file partially corrupted?
>> Ditto.
> 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.
Ah, I see that the health-checker thread kills the brick process if I/O
on the health_check file fails. Thanks for correcting me.
> Niels

More information about the Gluster-users mailing list