On Mon, Mar 18, 2013 at 5:57 PM, Paul Robert Marino <prmari...@gmail.com> wrote: > Its mostly due to the uid and gid name mapping to names instead of numbers > introduced in NFS 4 by default if possible a backup is saved as an extended > attribute and can also compound the atime update speed issue.
You don't disable atime? That's one of the most ritical speed enhancements for busy filesystems that I've ever found, and it has almost no use for most software. OK, it might be handy for expiring lightly used proxied material, but the performance cost and constant shuffling of rarely used data to the filesystem is very expensive. > As for JFS its been a long time since I tested it but I had the reverse > issue. > Oh and I know the issue you ran into with xfs its rare but has been known to > happen I've hit it once my self on a laptop its a journal problem, and fsck > isn't the tool to use. > There is a specific xfs repair tool to fix the journal or can rebuild it > from the backup inodes Then are you agreed that it's too likely to occur for high reliability filesystems, and only more suitable for high flowthrough data whose provenance is not so critical?
