<div dir="ltr">Even in that case I would prefer to assemble a new DRBD device ontop of the ZVOL snapshot and then mount the DRBD device instead :)</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 6, 2017 at 2:56 PM, Gionatan Danti <span dir="ltr"><<a href="mailto:g.danti@assyoma.it" target="_blank">g.danti@assyoma.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 06/09/2017 15:31, Yannis Milios wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If your topology is like the following: HDD -> ZFS (ZVOL) -> DRBD -> XFS then I believe it should make sense to always mount at the DRBD level and not at the ZVOL level which happens to be the underlying blockdev for DRBD.<br>
</blockquote></span>
Sure! Directly mounting the DRBD-backing ZVOL would, at the bare minumum, ruin the replication with the peer.<br>
<br>
I was speaking about mounting ZVOLs *snapshots* to access previous data version.<br>
<br>
Regards.<div class="HOEnZb"><div class="h5"><br>
<br>
-- <br>
Danti Gionatan<br>
Supporto Tecnico<br>
Assyoma S.r.l. - <a href="http://www.assyoma.it" rel="noreferrer" target="_blank">www.assyoma.it</a><br>
email: <a href="mailto:g.danti@assyoma.it" target="_blank">g.danti@assyoma.it</a> - <a href="mailto:info@assyoma.it" target="_blank">info@assyoma.it</a><br>
GPG public key ID: FF5F32A8<br>
</div></div></blockquote></div><br></div>