On Wed, Mar 22, 2023 at 10:30 AM wrote:
> OpenAFS implements its own CoW and using CoW below that again has no benefits
> and disturbs the fileservers "free-space" assumptions. It knows when it makes
> in-place updates and does not expect to run out of space in that situation.
At what level
On Wed, Mar 22, 2023 at 3:11 PM Dirk Heinrichs wrote:
> > it's not in-kernel; which means sooner or later one would encounter
> > problems.
>
> Can you please elaborate? I run two ZFS systems @home where one is an
> OpenAFS fileserver and client, the other one a client only. They both
> started
On Tue, Mar 21, 2023 at 9:32 PM wrote:
> The main ingredient on BTRFS is to disable Copy-on-Write for the respective.
> This also somewhat mitigates surprising out-of-space issues.
What is the reason behind disabling copy-on-write for BTRFS? Does it
break OpenAFS in some way, or is it only
Hello all!
I've searched the mailing archive (and the internet) about this topic,
but came a bit empty-handed, as the last proper mention of BTRFS on
this mailing list was 10 years ago.
So, given so much time has passed, I would like to ask the OpenAFS
community if anyone has any experience on
