Kyle McDonald wrote:
On 4/12/2010 3:01 PM, Lori Alt wrote:
On 04/12/10 11:50 AM, Darren J Moffat wrote:
On 12/04/2010 18:38, Tim Haley wrote:
4.1. Proposal
A new temporary mount property will be defined for the "zfs mount"
command.
Currently, the -o option to "zfs mount" can be used to set temporary
values for the following properties: devices, exec, readonly, setuid,
and xattr. It will now be possible to assign a temporary "mountpoint"
property. The file system will be mounted at the temporary mountpoint
and the persistent "mountpoint" property for the dataset will not
change.
Does this also allow the following to work without changing to legacy
mountpoint:
# mount -F zfs tank/a /mnt
I was sticking to the notion that legacy mounts work with the "legacy"
mountpoint only. So this would not be supported. This was an attempt
to be conservative about temporary mount support in an attempt to
limit its use to narrow circumstances, where the mechanism and its
constraints are well-understood.
For example, ZFS legacy mounts can be performed on non-empty
directories. ZFS native mounts (and I consider a temporary mount to
be a native ZFS mount) cannot be performed on non-empty directories.
I didn't want to mix up the code paths between the legacy mount path
and the ZFS mount path and I didn't want the two types of mounts to
get confused, since they have different constraints.
I'd really like this to work.
For me currently 'legacy' really means "mounted through /etc/vfstab". I
prefer if this was even more true, in that any ZFS filesystem could be
mounted manually wherever you like using this traditional syntax (should
the user even need to know that a filesystem is ZFS?) with out jumping
through aditional hoops.
I take your point, but I think "legacy" means more than "mounted through
/etc/vfstab". Also, a change that makes temporary zfs mounts easier to
use and more commonly used isn't necessarily a feature in my mind. We
really don't WANT temporary mounts to be used casually and commonly.
The zfs mount mechanism that already exists should continue to be the
normal and most commonly-used way to mount zfs file systems. Temporary
mounts really should be used for short-term, focused purposes, like
updating a BE other than the active one.
That, plus the fact that I still think we want to avoid blurring the
line between ZFS mounts and temporary mounts, makes me we should stick
with the clear distinction that temporary mounts are NOT legacy mounts
and so the legacy mounting mechanism will not be supported.
Lori
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
