Andreas Dilger wrote:
> So, what you're saying is that filesystem resizing is forbidden by POSIX,
> background data compression and data deduplication is forbidden by POSIX,
> migration across storage tiers is forbidden by POSIX? All modifications
> to the filesystem need to be synchronous becau
Mark H Weaver wrote:
> Yes, on Btrfs I reliably see (st_blocks == 0) on a recently written,
> mostly sparse file with size > 8G, using linux-libre-4.14.14. More
> specifically, the "storing sparse files > 8G" test in tar's test suite
> reliably fails on my system:
Now many bytes have been writt
On 01/22/2018 02:28 AM, Joerg Schilling wrote:
Since you need to reserve space on the background storage before you can even
write to the cached data for a file, you need to make stat() return the related
state that includes the reserved space.
The implementation that you suggest requires the f
Paul Eggert wrote:
> The implementation that you suggest requires the file system to remember
> how much reserved space that it initially allocated to the file, even if
> that number changes as a result of file system reorganization. This can
> place an undue burden on more-advanced implementa
On 01/22/2018 09:47 AM, Joerg Schilling wrote:
we are talking about files that do not change while something like TAR
is reading them.
It's reasonable for a file system to reorganize itself while 'tar' is
reading files. Even if a file's contents do not change, its space
utilization might chan
On Jan 22, 2018, at 10:47 AM, Joerg Schilling
wrote:
>
>> On Jan 22, 2018, at 3:28 AM, Joerg Schilling
>> wrote:
>>> If you still don't understand this, I recommend you to try to write an in
>>> kernel filesystem implementation I did this 30 years ago.
>
> Well, I tought that you realise
On Jan 20, 2018, at 5:06 PM, Mark H Weaver wrote:
>
> Andreas Dilger writes:
>
>> On Jan 10, 2018, at 4:50 AM, Pavel Raiskup wrote:
>>>
>>> On Wednesday, January 10, 2018 3:42:52 AM CET Mark H Weaver wrote:
From da922703282b0d3b8837a99a9c7fdd32f1d20d49 Mon Sep 17 00:00:00 2001
From:
Joerg Schilling writes:
> Mark H Weaver wrote:
>
>> Yes, on Btrfs I reliably see (st_blocks == 0) on a recently written,
>> mostly sparse file with size > 8G, using linux-libre-4.14.14. More
>> specifically, the "storing sparse files > 8G" test in tar's test suite
>> reliably fails on my system
