hooanon05@xxxxxxxxxxx writes:
> Goswin von Brederlow:
>> The problem is that /delta-fs/path/file would suddenly be a composite
>> of the new file /union/read-only/path/file and any stored delta
>> information in /union/read-write/path/file of the old file.
>
> Yes.
> And I am afraid stat.st_blocks will be incorrect too. But it may be a
> smaller problem for who think there is another bigger advantage. It
> might be just a trade off.
>
>
> J. R. Okajima
I could think of three possible values:
1) the sum of the st_blocks of both branches (total space used)
2) min(size/blocksize, sum of st_blocks) (appox. what the file would use)
3) st_bocks of read-write branch (read-write space used only)
I could think of a use for any one of them. Although the 3rd can be
done by "du /union/read-write" if there is an identity mapping between
filenames.
MfG
Goswin
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
