When messing around with zfs trying to break it, I creating a new pool using
files on an existing zfs filesystem. It seem to work fine until I created a
snapshot of the original filesystem and then tried to destroy the pool using
the files. The system appeared to deadlock and had to be reboote
After importing some pools after a re-install of the OS, i hit that "..:
Permission denied" problem. I figured out I could unmount, chmod, and mount to
fix it but that wouldn't be a good situation on a production box. Is there
anyway to fix this problem without unmounting?
This message pos
I should clarify. Say I have a zfs with the mount point /u00 that I import on
the system. When it creates the /u00 directory on the UFS root, it's created
with 700, and then the zfs is mounted and it appears to have the permissions of
the root of the zfs. 755 in this case.
But, if a non-ro
Which part is the bug? The crash or allowing pools of files that are on a zfs?
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
A bit off the subject but what would be the advantage in virtualization using a
pool of files verse just creating another zfs on an existing pool. My purpose
for using the file pools was to experiment and learn about any quirks before I
go production. It let me do things like set up a large ra
