> On 15.Jan 2018, at 19:26, markus.suva...@gmail.com wrote: > > > On Mon, 2018-01-15 at 10:05 +0100, Harald Barth wrote: >>>> What is the backend filesystem for your AFS cache partition? >>> AFS cache partition is btrfs subvolume, >>> cacheinfo: /afs:/mnt/ssd/openafs_cache:20000000 >> >> Can you put your cache in ext[234] and try again? > I don't have any partitios available but I can give up > swap and format that partition to ext4 and give a try.
Removing all swap space may cause other "interesting" issues. If you have sufficient space left on some filesystem, you could instead create a file with a fileystem on it and loop mount that: dd if=/dev/zero of=/where/space/left/image bs=1M count=2048 mkfs.ext[234] /where/space/left/image mount -oloop /where/space/left/image /mnt/openafs_cache Worst case you can still make that file sparse, as long as the fs has sufficient space to lodge the actually required space. >>> Sorry, systemd has destroyed logs already >> >> So the systemd craze has reached gentoo as well. > Yep, that craze is supported also :) Let's face it, systemd is upon us, and it's not that bad. What is bad is the way it's used (configured) in current distros. _______________________________________________ OpenAFS-devel mailing list OpenAFS-devel@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-devel
