[DRBD-user] The Problem of File System Corruption w/DRBD
gianni.milo22 at gmail.com
Thu Jun 3 21:20:58 CEST 2021
As others already mentioned the job of DRBD is to faithfully and accurately
replicate the data from the layers above it. So if there's a corruption on
the filesystem above the DRBD layer then it will happily do it for you,
same way as RAID1 would do it on a pair of hdds. If you want to reduce the
recovery time from such situation then you could leverage from the
snapshots capability on the layers below DRBD (if ThinLVM or ZFS are used),
to rollback at a previous checkpoint or implement HA at the layers above
DRBD if the application you are using supports it, it really depends on the
use case. That being said a filesystem corruption shouldn't be a common
thing and if it occurs you should investigate why it happened in the first
On Wed, 2 Jun 2021 at 22:50, Eric Robinson <eric.robinson at psmnv.com> wrote:
> Since DRBD lives below the filesystem, if the filesystem gets corrupted,
> then DRBD faithfully replicates the corruption to the other node. Thus the
> filesystem is the SPOF in an otherwise shared-nothing architecture. What is
> the recommended way (if there is one) to avoid the filesystem SPOF problem
> when clusters are based on DRBD?
> Disclaimer : This email and any files transmitted with it are confidential
> and intended solely for intended recipients. If you are not the named
> addressee you should not disseminate, distribute, copy or alter this email.
> Any views or opinions presented in this email are solely those of the
> author and might not represent those of Physician Select Management.
> Warning: Although Physician Select Management has taken reasonable
> precautions to ensure no viruses are present in this email, the company
> cannot accept responsibility for any loss or damage arising from the use of
> this email or attachments.
> Star us on GITHUB: https://github.com/LINBIT
> drbd-user mailing list
> drbd-user at lists.linbit.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the drbd-user