Hello James,

Tuesday, May 23, 2006, 10:25:10 PM, you wrote:

JD> On 5/23/06, Robert Milkowski <[EMAIL PROTECTED]> wrote:
>> Hello James,
>>
>> Tuesday, May 23, 2006, 6:43:11 PM, you wrote:
>>
>> JD> Hi
>>
>> JD> I think ZFS should add the concept of ownership to a ZFS filesystem,
>> JD> so if i create a filesystem for joe, he should be able to use his
>> JD> space how ever he see's fit, if he wants to turn on compression or
>> JD> take 5000 snapshots its his filesystem, let him. If he wants to
>> JD> destroy snapshots, he created them it should be allowed, but he should
>> JD> not be allowed to do the same with carol's filesystem. The current
>> JD> filesystem management is not fine grained enough to deal with this. Of
>> JD> course if we don't assign an owner the filesystem should perform much
>> JD> like it does today.
>>
>> JD> zfs set owner=joe pool/joe
>>
>>
>> IIRC it's planned - however I'm not sure it a user should be able to
>> turn on compression, especially when it's directly turned off by sys
>> admin.
>>

JD> perhaps if compression turned/forced off by the admin then it
JD> shouldn't be alowed, but enabling compression on a filesystem that
JD> just had it off by default should be allowed but of course this
JD> complicates implementation. They could create a system wide config
JD> file disallowing compression/encryption  etc.

Something like 'zfs set compression=user dataset'

or instead of 'user' -> 'allow'

-- 
Best regards,
 Robert                            mailto:[EMAIL PROTECTED]
                                       http://milek.blogspot.com

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to