Re: [RFC] The reflink(2) system call v2.

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

 



Joel Becker wrote:
On Thu, May 07, 2009 at 10:59:04PM -0400, jim owens wrote:
You certainly did not address:

- desire for one single system call to handle both
  owner preservation and create with current owner.

	Nope, and I don't intend to.  reflink() is a snapshotting call,
not a kitchen sink.

I'm not a maintainer but if I was, in that case I would
NAK this since more people wanted the cowfile() definition
than your reflink definition.

If you persist that you are only doing the snapshot
then call it snaplink(2) or something.

The reflink() name makes no sense because all references are
internal to the file system.  There is absolutely no way via
"ls" to determine the reference between the original and new.

With hard links and symlinks you can easily associate them.

jim
--
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