Yes, I agree it's a bug. -u should not leave anything mounted. --matt
On Thu, Oct 22, 2015 at 11:20 PM, Andriy Gapon <[email protected]> wrote: > > So, should I open a bug report about this? > > On 21/10/2015 16:25, Andriy Gapon wrote: > > On 21/10/2015 16:08, Andriy Gapon wrote: > >> > >> It seems that zfs receive -F -u would mount a received filesystem after > >> receiving a full stream if a destination filesystem already existed > (and, thus, > >> got destroyed and re-created) and was mounted. > >> Is this a bug? > >> Or is this behavior actually preferable and only needs to be > documented? [*] > >> > >> [*] As it is now, the interaction of -F and receiving a full stream is > not > >> documented at all. > >> > > > > How to reproduce: > > $ zfs create rpool/sandbox > > $ zfs create rpool/sandbox/from > > $ zfs create rpool/sandbox/to > > $ zfs snap rpool/sandbox/from@snap > > $ zfs send rpool/sandbox/from@snap | zfs recv -v -F -u rpool/sandbox/to > > receiving full stream of rpool/sandbox/from@snap into > rpool/sandbox/to@snap > > received 41.7KB stream in 1 seconds (41.7KB/sec) > > $ zfs get mounted rpool/sandbox/to > > NAME PROPERTY VALUE SOURCE > > rpool/tmp/sandbox/to mounted yes - > > > > This behavior can be more problematic if the mountpoint property changes > either > > because it had a non-inherited value or the stream contains properties > because > > it has been generated with either -R or -p. > > > > > -- > Andriy Gapon > _______________________________________________ > developer mailing list > [email protected] > http://lists.open-zfs.org/mailman/listinfo/developer >
_______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
