From: Paul Eggert <eggert@cs.ucla.edu>
To: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>, antonio@gnu.org
Cc: linux-btrfs@vger.kernel.org, bug-tar@gnu.org,
ahferroin7@gmail.com, adilger@dilger.ca
Subject: Re: [Bug-tar] stat() on btrfs reports the st_blocks with delay (data loss in archivers)
Date: Wed, 6 Jul 2016 17:11:47 +0200 [thread overview]
Message-ID: <577D1FB3.3030708@cs.ucla.edu> (raw)
In-Reply-To: <577d1f11.ECLAA6oU6lhcCjFc%Joerg.Schilling@fokus.fraunhofer.de>
On 07/06/2016 05:09 PM, Joerg Schilling wrote:
> you concur that a delayed assignment of the "correct" value for
> st_blocks while the contend of the file does not change is not permitted.
I'm not sure I agree even with that. A file system may undergo garbage
collection and compaction, for instance, in which a file's data do not
change but its internal representation does.
next prev parent reply other threads:[~2016-07-06 15:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 7:18 stat() on btrfs reports the st_blocks with delay (data loss in archivers) Pavel Raiskup
2016-07-04 19:35 ` [Bug-tar] " Andreas Dilger
2016-07-05 9:28 ` Joerg Schilling
2016-07-06 11:37 ` Austin S. Hemmelgarn
2016-07-06 11:49 ` Joerg Schilling
2016-07-06 14:43 ` Antonio Diaz Diaz
2016-07-06 14:53 ` Joerg Schilling
2016-07-06 15:01 ` Paul Eggert
2016-07-06 15:09 ` Joerg Schilling
2016-07-06 15:11 ` Paul Eggert [this message]
2016-07-06 15:12 ` Austin S. Hemmelgarn
2016-07-06 15:22 ` Joerg Schilling
2016-07-06 16:05 ` Austin S. Hemmelgarn
2016-07-06 16:11 ` Austin S. Hemmelgarn
2016-07-06 16:33 ` Joerg Schilling
2016-07-06 17:35 ` Andreas Dilger
2016-07-07 8:08 ` Pavel Raiskup
2016-07-11 14:41 ` David Sterba
2016-07-11 15:00 ` Chris Mason
2016-07-11 15:16 ` David Sterba
2016-07-11 17:30 ` Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=577D1FB3.3030708@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=Joerg.Schilling@fokus.fraunhofer.de \
--cc=adilger@dilger.ca \
--cc=ahferroin7@gmail.com \
--cc=antonio@gnu.org \
--cc=bug-tar@gnu.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.