Re: [PATCH 1/3] fs: Document the reflink(2) system call.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 04, 2009 at 09:44:32AM +0800, Tao Ma wrote:
> Theodore Tso wrote:
>> On Sat, May 02, 2009 at 11:15:01PM -0700, Joel Becker wrote:
>> How should quota handle reflinks?  Since there are separate inodes,
>> the two files could be owned by different user ID's.  Since the data
>> blocks exist only once, I can imagine a number of different ways of
>> handling it:
<snip>
> yeah, agree. So I will pick #3 in my ocfs2 reflink implementation.

	While at first I was all "sure, this makes sense," now I'm
thinking otherwise.  Because reflink() means the file attributes are
unmodified.  So the original owner owns the new file, and thus the quota
charge doesn't matter.  If and when the new file is changed to another
owner, then the normal quota code will adjust the quotas.

Joel

-- 

"If you are ever in doubt as to whether or not to kiss a pretty girl, 
 give her the benefit of the doubt"
                                        -Thomas Carlyle

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@xxxxxxxxxx
Phone: (650) 506-8127
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux