Hi there, Apologies for not confirming on a much more recent kernel, if anyone could please try my test script for me on a newer kernel that would be very much appreciated.
I'm working on reproducible builds, and part of this workflow involves tar archiving parts of read-only btrfs snapshots. Problem is, some of these tar archives are different from run to run when they capture an empty directory that happened to be a subvol parent on the original FS: the atimes on these empty dirs are always returning the current time - which is not the case with an ordinary empty directory created with mkdir; it's also not the same behaviour on the original FS (tar archives are reproducible if we use the original FS rather than the read-only snapshot). This all happens regardless of mounting noatime. Perhaps this verbiage is convoluted, I'm writing this in a hurry with limited internet connectivity - I have a reproducible test case here at https://gist.github.com/csirac2/c2b5b2b9d0193b3c08a8 Again, I understand this is a pretty old kernel and perhaps this is fixed by now, I'll try a more recent kernel with more assertive bug report next week if nobody has time to try out my test case. Cheers -- Paul Harvey -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
