/17312
Am Mittwoch, dem 06.10.2021 um 09:49 +0200 schrieb Michael Laß:
> [reposting from correct mail address and with small change]
>
> Hi,
>
> it looks like people using Arch Linux get this error as well after
> updating to 5.14 [previously I wrote 5.14.9 but the reporter upgra
[reposting from correct mail address and with small change]
Hi,
it looks like people using Arch Linux get this error as well after
updating to 5.14 [previously I wrote 5.14.9 but the reporter upgraded
from 5.13 so it could be any subversion]. Here is a bug report:
I always forget which variant of my email address is registered here.
My first mail was filtered out, so I'm quoting myself here:
Weitergeleitete Nachricht
Von: Michael Laß
An: openafs-info@openafs.org
Betreff: Re: [OpenAFS-announce] OpenAFS 1.8.6 beta 2 available
Datum: Tue
Am Montag, den 14.03.2016, 10:51 +0100 schrieb mdrslmr:
> On Sun, 13 Mar 2016, Michael Laß wrote:
> > Now here's the interesting part: If the OpenAFS cache is large enough
> What is large enough? Or rather how small must the cache be to produce
> the error?
Big enough to entirel
Hi,
while trying to stress test the proposed patches for Linux 4.4 I
encountered an issue using git inside AFS that is not connected to the
Linux 4.4 issue:
I cloned the Linux kernel repo inside AFS. On this freshly cloned repo,
all data is stored in a single .pack file (.git/objects/pack/pack-
Am Dienstag, den 08.03.2016, 16:47 +0100 schrieb mdrslmr:
> I created a patch from what you suggested above.
>
> [...]
>
> I did all of that on top of AUR-openafs-linux-4.4 which was provided by
> Bevan, the openafs archlinux packager.
>
> The patch I actually used is attached below.
That
Hi!
Am 23.01.2016 um 18:22 schrieb Benjamin Kaduk :
>
> Though the patches linked there are sufficient to permit the build to
> complete, there are some more subtle behavior changes in the kernel in
> that some of the splice functions will now return ERESTARTSYS if there is
> any
Hi,
I heard from a user about an inconsistency between documentation and the
actual behavior of the openafs client (1.6.5):
The manpage for fs setcrypt states: The default encryption status is
enabled. But in fact this seems to be not the case.
Start scripts for Debian and FreeBSD enable it