Re: [PATCH 5/5] btrfs: add no_mtime flag to btrfs-extent-same

Austin S Hemmelgarn
2015-06-25T13:10:42Z

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

On 2015-06-25 08:52, David Sterba wrote:
> On Wed, Jun 24, 2015 at 04:17:32PM -0400, Zygo Blaxell wrote:
>> Is there any sane use case where we would _want_ EXTENT_SAME to change
>> the mtime? We do a lot of work to make sure that none of the files
>> involved have any sort of content change. Why do we need the flag at all?
>
> Good point, I don't see the usecase for updating MTIME.
Was the original intent possibly to make certain the CTIME got updated?
Because EXTENT_SAME _does_ update the metadata, and by logical
extension that means that the CTIME should change.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]