|
From: | Joerg Schilling |
Subject: | Re: [Bug-tar] Detection of sparse files is broken on btrfs |
Date: | Mon, 8 Jan 2018 16:28:36 +0100 |
User-agent: | Heirloom mailx 12.5 7/5/10 |
Tim Kientzle <address@hidden> wrote: > I'm not entirely sure I understand the above. > > It sounds like someone is claiming that: > > * Archiving programs should know about the *timing* of filesystem > implementations (60s here for btrfs, something else for <new filesystem > XYZ>?) > > * And specifically request the OS to fsync() files before trusting the > metadata This is exactly the reason, why btrfs (in case it behaves as claimed) seems to be be in conflict with POSIX. POSIX requires that stat() returns cached meta data instead of probably out of date information from the background medium. In other words: It is not allowed to return different data before and after a sync() or fsync() call. Jörg -- EMail:address@hidden (home) Jörg Schilling D-13353 Berlin address@hidden (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
[Prev in Thread] | Current Thread | [Next in Thread] |