[DragonFlyBSD - Submit #2988] (Closed) cpdup should ignore UF_ARCHIVE when deciding whether to copy a file

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #2988 has been updated by swildner.

Status changed from New to Closed

Pushed, thanks!


----------------------------------------
Submit #2988: cpdup should ignore UF_ARCHIVE when deciding whether to copy a file
http://bugs.dragonflybsd.org/issues/2988#change-13268

* Author: asomers
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Userland
* Target version: 
----------------------------------------
On operating systems that support it (including Illumos, FreeBSD, and Windows), the UF_ARCHIVE flag means that a file needs to be archived.  Filesystems that support this flag (including msdosfs and ZFS) will set it automatically when the file is created.

When deciding whether to copy a file, cpdup should ignore the UF_ARCHIVE file flag.  If that flag is supported by the destination file system but it's cleared on a source file, then multiple invocations of cpdup would all copy the source file because its flags wouldn't match.  OTOH, if the destination filesystem doesn't support UF_ARCHIVE, then there's no point in cpdup setting it.

Steps to reproduce, using ZFS on FreeBSD:
$ mkdir src dst
$ touch src/foo
$ chflags 0 src/foo
$ cpdup -v src dst
dst/foo                          copy-ok
$ cpdup -v src dst
dst/foo                          copy-ok

---Files--------------------------------
submit_2988.diff (995 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account