VFS_CACHEPRIME(8)
π
VFS_CACHEPRIME(8) β like, the cacheprime one from the samba(7) suite, bestie
okay so picture this: a samba(7) man page, section 8, system administration tools energy, and its whole personality is priming the kernel file data cache. yes ma'am. let's get into it β¨
β¨ NAME β¨
vfs_cacheprime β prime the kernel file data cache π§
(that's it. that's the whole name section. she's concise. we respect her.)
πΈ SYNOPSIS πΈ
vfs objects = cacheprime
literally one line and it's already iconic π
π¦ DESCRIPTION π¦
okay so first things first: this VFS module is part of the samba(7) suite. family reunion, etc etc π«Ά
so what does vfs_cacheprime actually do? bestie. it reads chunks of file data near the range requested by clients β like, around the part they asked for β so that the data is already chilling in the kernel file data cache at the exact moment the clients actually request it. it's the "pre-gaming the data" module. main character energy, honestly. π₯
the size of the disk read operations it performs is decided by the cacheprime:rsize option (more on her in a sec π). and here's the cute structural detail: all disk read operations are aligned on boundaries that are a multiple of this size. clean lines. no chaos. we love to see it. π
also! each range of the file data is primed at most once during the time the client has the file open. not twice. not three times. once. she said "i'm not doing extra work for free." π
and yes β this module is stackable. pile her on top of your other VFS modules, she's flexible like that. π
π OPTIONS π
cacheprime:rsize = BYTESβ the number of bytes with which to prime the kernel data cache. this is the whole size dial, okay? this is the one that matters.
the following suffixes may be applied to BYTES:
KβBYTESis a number of kilobytesMβBYTESis a number of megabytesGβBYTESis a number of gigabytes
so like, 1M, 512K, 2G β pick your fighter β
π EXAMPLES π
okay so hypothetically (and I do mean hypothetically, it's literally in the config block) β imagine a disk array where you absolutely need every single read operation to be 1 megabyte (1048576 bytes), and aligned on 1 megabyte boundaries. the way you'd set that up is:
[hypothetical]
vfs objects = cacheprime
cacheprime:rsize = 1M
ate. no crumbs. π
π CAVEATS π
real talk time, bestie, because I love you: cacheprime is not a substitute for a general-purpose readahead mechanism. not even close. she is not out here doing general purpose anything. π
she's intended for use only in very specific environments where disk operations must be aligned and sized to known values β "(as much as that is possible)". yeah. that last part. that's the fine print and it's there for a reason, so don't come for her when the disk array has opinions. π
no cap: if you're reaching for cacheprime as your general readahead solution, that's not the vibe check you think it is. it's a specialised tool for a specialised setup. periodt. π
π VERSION π
this man page is part of version 4.22.11-git.560.f0322ab554160000.1.1SUSE-oS16.0-ppc64le of the Samba suite. yes that entire string. she's long, she's specific, she's real. π§
π AUTHOR π
the original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. legends only, fr fr. πΈ
and that's the whole page, bestie!! π hope you're thriving and your cache is primed. mwah π«Ά
Samba 4.22.11-git.560.f0322ab55 Β· 08/21/2026 Β· VFS_CACHEPRIME(8) β ok so that's literally the source/version and date from the footer, consider them mentioned with love πβ¨
π¦ where this page comes from
- opensuse-leap 16.0: samba 4.22.11+git.560.f0322ab554-160000.1.1 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms