Project

General

Profile

Bug #5984

zfs clone should not mount the clone if canmount == noauto

Added by Andriy Gapon over 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
zfs - Zettabyte File System
Start date:
2015-06-05
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

Since canmount property is not inherited and its default value is on the only scenario where this matters is zfs clone -o canmount=noauto ....
zfs create -o canmount=noauto ... does not mount the new filesystem. Creation of a new filesystem does not imply an intent to mount it.

ZoL has the following change already:
https://github.com/FransUrbo/zfs/commit/dd0e0e69f5b1c83bf2895ac00a0b83af77473175
https://github.com/zfsonlinux/zfs/issues/2241

History

#2

Updated by Electric Monk almost 4 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

git commit 780828c8aa1df2dc6f2066107a4aa8d045297972

commit  780828c8aa1df2dc6f2066107a4aa8d045297972
Author: Andriy Gapon <avg@FreeBSD.org>
Date:   2015-10-20T15:10:19.000Z

    5984 zfs clone should not mount the clone if canmount == noauto
    Reviewed by: Matthew Ahrens <mahrens@delphix.com>
    Reviewed by: Justin Gibbs <gibbs@scsiguy.com>
    Reviewed by: Richard Elling <Richard.Elling@richardelling.com>
    Approved by: Matthew Ahrens <mahrens@delphix.com>

Also available in: Atom PDF