[zfs-code] Read-only (forensic) mounts of ZFS

2007-07-27 Thread Darren J Moffat
Mark Furner wrote: > PREPARE LOOPBACK DEVICE > note need full path for file > > root at sol10 /export/home# lofiadm -a /export/home/t1_fs1.COPY.dd /dev/lofi/1 > root at sol10 /export/home# lofiadm > Block Device File > /dev/lofi/1 /export/home/t1_fs1.COPY.dd > root at sol1

[zfs-code] Read-only (forensic) mounts of ZFS

2007-07-27 Thread Mark Furner
Thanks for the clarification, Darren, and sorry for cross-posting. OK, physical device -> pool -> file-system(s) Some questions: 1) zpool import allows options similar to zfs. Can I set the same or similar read-only (RO) options for the whole pool (noexec,nosuid,noatime,nodevices,ro)? 2) Wha

[zfs-code] Read-only (forensic) mounts of ZFS

2007-07-27 Thread Darren J Moffat
Mark Furner wrote: > Thanks for the clarification, Darren, and sorry for cross-posting. > > OK, physical device -> pool -> file-system(s) > > Some questions: > > 1) zpool import allows options similar to zfs. Can I set the same or similar > read-only (RO) options for the whole pool > (noexec,n

[zfs-code] Read-only (forensic) mounts of ZFS

2007-07-27 Thread Mark Furner
Thanks Darren I found Example 10 and 11 in man zfs as a quick how-to: Example 10: Remotely Replicating ZFS Data Example 11: Using the zfs receive -d Option As to Q2 about the changes to the pool data and zpool.cache I can find this out by testing. Regards Mark On Friday 27 July 2007 15:06,

[zfs-code] Read-only (forensic) mounts of ZFS

2007-07-27 Thread Matthew Ahrens
Mark Furner wrote: > Thanks for the clarification, Darren, and sorry for cross-posting. > > OK, physical device -> pool -> file-system(s) > > Some questions: > > 1) zpool import allows options similar to zfs. Can I set the same or similar > read-only (RO) options for the whole pool > (noexec,n