Re: [OpenAFS] Caveats of having AFS cache on a shared ext3 partition in Linux?

[Jason Edgecombe]

Harald Barth wrote:

caveats of having the AFS be on an ext3 filesystem in Linux, which
is shared by the rest of the system?

Slower.

filling the partition that AFS uses for caching

Means normally reboot.

Should the 5% root reserved percentage help with that?

In a student lab you could make the reserved percentage so big that it
is unlikely that root (logs) and AFS (cache) fill the partition (both
root and AFS can write over that limit).

good to know.

The background to this is I'l be deploying a university computer lab
full of Apple 21.5" iMacs running Linux as the sole OS. I need to
set a firmware password, but the Mac will not boot a /boot+LVM
partition layout with a firmware password, but it will boot with a
password when I only have one partition. Things boot fine when no
firmware password is set :(

Hi Jason, you could loopbackmount an ext2. Maybe even tmpfs if you run
a client version that supports tmpfs as a cache file system. Just
don't forget to make a bigger swap in that case.

Does 1.4.11 support tmpfs?

The loopback should be ext2 intead of ext3?

FYI, the swap must be a swapfile, not a dedicated partition...sigh.

Thanks,
Jason
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info