bugmail-sender at Sun.COM
2009-Apr-15 10:51 UTC
CR 6647661 Updated, P2 kernel/zfs "set once" / "create time only" properties can''t be set for pool level dataset
*Synopsis*: "set once" / "create time only" properties
can''t be set for pool level dataset
CR 6647661 changed on Apr 15 2009 by <User 1-ERV-6>
=== Field ============ === New Value ============= === Old Value ============
See Also 6828754
====================== =========================== ==========================
*Change Request ID*: 6647661
*Synopsis*: "set once" / "create time only" properties
can''t be set for pool level dataset
Product: solaris
Category: kernel
Subcategory: zfs
Type: Defect
Subtype: Usability
Status: 10-Fix Delivered
Substatus:
Priority: 2-High
Introduced In Release: solaris_nevada
Introduced In Build: snv_27
Responsible Engineer: <User 1-5Q-12446>
Keywords: zfs-crypto
=== *Description* ===========================================================The
toplevel initial dataset in a pool can''t currently have any of the
create time only properties set:
The examples below use the normalization property but this applies to all
properties that
are create time only.
Attempt to set a create time only dataset property at pool creation time:
# zpool create -o normalization=formC mypool /tmp/f
property ''normalization'' is not a valid pool property
This isn''t unexpected though because we can''t set dataset
properties with zpool(1M), however:
Create the pool and then attempt to set the property on the top level dataset:
# zpool create mypool /tmp/f
# zfs set normalization=formC mypool
cannot set property for ''mypool'':
''normalization'' is readonly
So now we are stuck with a dataset who''s create time only property we
can''t change.
Compare this to creating a non top level dataset, where the create time only
property can be set:
# zfs create -o normalization=formC mypool/data
*** (#1 of 1): 2008-01-07 11:18:02 GMT+00:00 <User 1-5Q-14842>
=== *Public Comments* =======================================================
=== *Workaround*
============================================================Change the top level
dataset to ''canmount=false'' so that no data is stored in it.
*** (#1 of 1): 2008-01-07 11:18:02 GMT+00:00 <User 1-5Q-14842>
=== *Additional Details* ====================================================
Targeted Release: solaris_nevada
Commit To Fix In Build: snv_96
Fixed In Build: snv_96
Integrated In Build: snv_96
Verified In Build:
See Also: 6661335, 6729464, 6744666, 6828754
Duplicate of:
Hooks:
Hook1: ar1.x
Hook2: fishworks_verified
Hook3: NAS
Hook4:
Hook5:
Hook6:
Program Management:
Root Cause: Interface Issue
Fix Affects Documentation: Yes
Fix Affects Localization: No
=== *History* ===============================================================
Date Submitted: 2008-01-07 11:18:02 GMT+00:00
Submitted By: <User 1-5Q-14842>
Status Changed Date Updated Updated By
3-Accepted 2008-01-07 16:07:13 GMT+00:00 <User 1-5Q-12446>
6-Fix Understood 2008-03-04 22:54:58 GMT+00:00 <User 1-5Q-12446>
7-Fix in Progress 2008-07-24 19:04:00 GMT+00:00 <User 1-5Q-12446>
8-Fix Available 2008-07-24 22:04:55 GMT+00:00 <User 1-5HNZ8F>
10-Fix Delivered 2008-08-13 17:38:38 GMT+00:00 <User 1-5Q-3253>
=== *Service Request* =======================================================
Impact: Significant
Functionality: Primary
Severity: 2
Product Name: solaris
Product Release: solaris_nevada
Product Build:
Operating System: solaris
Hardware: generic
Submitted Date: 2008-01-07 11:18:03 GMT+00:00
=== *Multiple Release (MR) Cluster* - 0 ======================================
Seemingly Similar Threads
- CR 6647661 <User 1-5Q-12446>, Now responsible engineer P2 kernel/zfs "set once" / "create time only" properties can''t be set for pool level dataset
- Function sort.data.frame
- General means of matching a color specification to an official R color name
- zfs permanent errors in a clone
- zfs snaps and removing some files
