Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
...I mean by cloning it first, since snapshot does not appear as blockdev to the system but the clone does. On Wed, Sep 6, 2017 at 2:58 PM, Yannis Milios <yannis.milios at gmail.com> wrote: > 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 :) > > On Wed, Sep 6, 2017 at 2:56 PM, Gionatan Danti <g.danti at assyoma.it> wrote: > >> On 06/09/2017 15:31, Yannis Milios wrote: >> >>> 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. >>> >> Sure! Directly mounting the DRBD-backing ZVOL would, at the bare minumum, >> ruin the replication with the peer. >> >> I was speaking about mounting ZVOLs *snapshots* to access previous data >> version. >> >> Regards. >> >> >> -- >> Danti Gionatan >> Supporto Tecnico >> Assyoma S.r.l. - www.assyoma.it >> email: g.danti at assyoma.it - info at assyoma.it >> GPG public key ID: FF5F32A8 >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20170906/3d42cdc3/attachment.htm>