Atime and btrfs: a bad combination?

Posted Jun 3, 2012 11:00 UTC (Sun) by liljencrantz (guest, #28458)
In reply to: Atime and btrfs: a bad combination? by ballombe
Parent article: Atime and btrfs: a bad combination?

I'm suggesting that the usefulness of popcon is smaller than the damage of atime, so even if there is no alternative implementation strategy for popcon, it would still be better to drop atime.

Atime and btrfs: a bad combination?

Posted Jun 3, 2012 14:57 UTC (Sun) by Yorick (guest, #19241) [Link]

Quite right—for every odd feature there will always be someone having found a use for it and object to it being taken away. But the cost of its existence is often carried by everyone: in performance, code complexity, security, ease of use, conceptual simplicity, and so on. For atime, it should stand clear that the occasional benefits stand in no proportion to those costs.

We see this every time a sensible proposal comes forth to dump an old misfeature that causes way more grief than enjoyment. Control characters in file names, for example...