<div dir="auto">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 place.</div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 2 Jun 2021 at 22:50, Eric Robinson <<a href="mailto:eric.robinson@psmnv.com">eric.robinson@psmnv.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="m_8656140715393555189WordSection1">
<p class="MsoNormal">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?
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">-Eric<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
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.
</div>
_______________________________________________<br>
Star us on GITHUB: <a href="https://github.com/LINBIT" rel="noreferrer" target="_blank">https://github.com/LINBIT</a><br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
<a href="https://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">https://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</blockquote></div></div>