In my testing, vmware doesn't see the vm1 and vm2 filesystems. Vmware
doesn't have an automounter, and doesn't traverse NFS4 sub-mounts
(whatever the formal name for them is). Actually, it doesn't support
NFS4 at all!
Regards,
Tristan.
-Original Message-
From:
Are tools necessary to ensure that deleted ZFS pools can not be recovered or
that deleted filesystems are really deleted?
If the current delete commands do offer some level of data recovery, is worth
offering a destroy command which deletes and ensures no means of recovery other
than a backup?
Haudy Kazemi wrote:
Hello,
I recently asked myself this question: Is it possible to unset ZFS
properties? Or reset one to its default state without looking up what
that default state is?
I believe the answer is yes, via the zfs inherit command (I haven't
verified yet, but I think a case
russell aspinwall wrote:
Are tools necessary to ensure that deleted ZFS pools can not be recovered or
that deleted filesystems are really deleted?
dd if=/dev/zero over the disks, or use format(1M) analyze - purge.
For just a single filesystem you can get some comfort level by doing:
zfs
Darren J Moffat wrote:
Haudy Kazemi wrote:
You run:
zfs set compression=off tank/home/smith
but that doesn't unset the compression setting for filesystem
'smith', it just overrides the inheritance of compression=on (as
expected).
So how to unset/reset?
zfs inherit compression
Haudy Kazemi wrote:
I recently asked myself this question: Is it possible to unset ZFS
properties? Or reset one to its default state without looking up what
that default state is?
I have another question: is it possible to set ZFS properties without
inheritance to all descendant datasets?
Thanks for clearing up the issue
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On Thu, Aug 13, 2009 at 12:23 PM, Darren J
Moffatdarr...@opensolaris.org wrote:
russell aspinwall wrote:
Are tools necessary to ensure that deleted ZFS pools can not be recovered
or that deleted filesystems are really deleted?
dd if=/dev/zero over the disks, or use format(1M) analyze -
Hi Darren,
took me a while what device is meant by zdb -l...
Original size was 20GB
After resizing in EVA format -e showed the new correct size:
17. c6t6001438002A5435A0001006Dd0 HP-HSV210-6200-30.00GB
/scsi_vhci/s...@g6001438002a5435a0001006d
Here is the output of
On Aug 13, 2009, at 1:37 AM, James Hess no-re...@opensolaris.org
wrote:
The real benefit of the of using a
separate zvol for each vm is the instantaneous
cloning of a machine, and the clone will take almost
no additional space initially. In our case we build a
You don't have to use ZVOL
Hi,
One thing I miss in zfs is the ability to override an attribute value
in zfs receive - something like the -o option in zfs create. This
option would be particularly useful with zfs send -R to make a backup
and be sure that the destination won't be mounted
zfs send -R f...@snap |
Cyril,
Can you please post the code, I will try to update it and get it to compile as
I have a customer with the requirement.
Thanks,
JK
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
On 13.08.09 13:44, Andrey V. Elsukov wrote:
Haudy Kazemi wrote:
I recently asked myself this question: Is it possible to unset ZFS
properties? Or reset one to its default state without looking up what
that default state is?
I have another question: is it possible to set ZFS properties
Is it possible to use the zfs copies property and put the disks individually
into a pool? That would give you 3TB (1.5 + 1 + .5) usable.
http://blogs.sun.com/relling/entry/zfs_copies_and_data_protection
States that copies will be spread across disks. But what I don't know (and
don't have a
On Wed, Aug 12 at 17:30, Adam Sherman wrote:
I believe you will get .5 TB in this example, no?
1.5T, 1.0T and 0.5T in a single RAID-Z is equivalent to three 0.5T
drives in a RAID-Z, which gets you two units worth of capacity and one
unit of parity, summing to 1.0T usable.
--
Eric D. Mudama
In short, I think an alias for 'zfs inherit' could be added to 'zfs
set' to make it more clear to those of us still new to ZFS. Either
that, or add some additional pointers in the Properties
documentation that the set command can't unset/reset properties.
That would to me be confusing it
Nicolas Williams wrote:
On Wed, Aug 12, 2009 at 06:17:44PM -0500, Haudy Kazemi wrote:
I'm wondering what are some use cases for ZFS's utf8only and
normalization properties. They are off/none by default, and can only be
set when the filesystem is created. When should they specifically be
I saw this question on another mailing list, and I too would like to
know. And I have a couple questions of my own.
== Paraphrased from other list ==
Does anyone have any recommendations for books on File Systems and/or
File Systems Programming?
== end ==
I have some texts listed below, but are
On Thu, Aug 13, 2009 at 05:57:57PM -0500, Haudy Kazemi wrote:
Therefore, if you need to interoperate with MacOS X then you should
enable the normalization feature.
Thank you for the reply. My goal is to configure the filesystem for the
lowest common denominator without knowing up front
Eric Schrock wrote:
On 08/11/09 06:03, Darren J Moffat wrote:
I thought so too initially, then I changed my mind and I like it the
way it is. The reason being is that describing the intent allows
changing the implementation and keeping the meaning. It is the
intent that matters to the
Prabahar Jeyaram wrote:
You seem to be hitting :
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6586537
The fix is available in OpenSolaris build 115 and later not for Solaris 10 yet.
Have you got more information on how was it fixed?
--
Robert Milkowski
Going back a fair way the basics of FS design are in books like the
following
Chapter 7 and 8 of The Design and Implementation of the 4.4BSD
Operating System, Leffler, McKusick, Karels and Quarterman covers the
FFS
Chapter 6 of The Magic Garden Explained, Goodheart and Cox addresses
22 matches
Mail list logo
