bugmail-sender at Sun.COM
2008-Jan-07 16:10 UTC
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
*Synopsis*: "set once" / "create time only" properties can''t be set for pool level dataset Due to a change requested by <User 1-5Q-12446>, <User 1-5Q-12446> is now the responsible engineer for: CR 6647661 changed on Jan 7 2008 by <User 1-5Q-12446> === Field ============ === New Value ============= === Old Value ============ Responsible Engineer <User 1-5Q-12446> Status 3-Accepted 1-Dispatched ====================== =========================== ========================== *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: 3-Accepted Substatus: Priority: 2-High Introduced In Release: Introduced In Build: 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> === *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: Commit To Fix In Build: Fixed In Build: Integrated In Build: Verified In Build: See Also: Duplicate of: Hooks: Hook1: Hook2: Hook3: Hook4: Hook5: Hook6: Program Management: Root Cause: Fix Affects Documentation: No 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> === *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 ======================================
Maybe Matching Threads
- CR 6647661 Updated, 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