Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Jun 2016 21:52:40 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-doc@FreeBSD.org
Subject:   [Bug 210222] 19.4.7.2. -- Add warning about ZFS silently masking datasets with the same mountpoints when recursively sending/receiving the root dataset
Message-ID:  <bug-210222-9@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210222

            Bug ID: 210222
           Summary: 19.4.7.2. -- Add warning about ZFS silently masking
                    datasets with the same mountpoints when recursively
                    sending/receiving the root dataset
           Product: Documentation
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Documentation
          Assignee: freebsd-doc@FreeBSD.org
          Reporter: b.manas.88@gmail.com

I was following the handbook in trying to create a backup of the whole
filesystem of a system that I had installed & configured. I ran into an iss=
ue
when trying to send/receive the snapshot of the datasets.

**

If a user takes a recursive snapshot of an entire pool, such as with

test-system1# zfs snapshot -r zroot@TEST

and then sends that to a second ZFS system, such as with

test-system1# zfs send -vR zroot@TEST | ssh test-system2 zfs recv -Fdvu
zroot/TEST/test-system1_zroot


the resulting datasets on the receiving side will have mountpoints that are
exactly the same as some of the datasets that already exist. ZFS does not w=
arn
about this and upon a reboot, important datasets will be masked. This requi=
res
booting into a livecd and manually changing the mountpoints so that they ar=
e no
duplicates. This has happened to me before and I think there should be at l=
east
a warning in the handbook so that users who are not familiar with ZFS are a=
ware
of this danger.

I spoke to Allan Jude about this at BSDCan 2016 and he responded positively=
 to
making this change. I am happy to submit a patch, I have attended 2 of the =
Doc
Sprints at BSDCan 2016 and I will be familiarizing myself with the process =
of
submitting a patch for documentation.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210222-9>