0

I'd like to keep some directories (e.g. /var/cache/apt, /var/lib/apt/lists, user browser caches or even Mozilla profiles) in RAM, but still backed by disk. The files should be copied to RAM when mounting and copied back to disk when umounting.

Short of writing a oneshot systemd unit (I've done this, but I don't like it), what options do I have? Adding a tmpfs entry to /etc/fstab is the simplest, but doesn't copy to/from disk.

Also, for user files (e.g. ~/.cache) can I use a systemd --user unit, so that it applies / can be configured to individual users independently?

usretc
  • 101
  • 1

1 Answers1

2

Do not use tmpfs for persistent storage. If this copy script does not run, such as when the host crashes, it is gone.

Use persistent disk volumes. Perhaps not backed up and less redundant than important data, but durable.

Linux already uses available RAM for caching. So those recently accessed files are in RAM when you check for software updates again, or hit the back button in the browser. Further, as the files already are on durable storage, these caches can be reclaimed immediately if the system needs RAM for other reasons.

John Mahowald
  • 32,050
  • 2
  • 19
  • 34
  • Yeah, thanks. I already *don't* *care* if /var/cache/apt/ or /var/lib/apt/lists or man or the user's browser cache fail to copy back -- possibly not even the .mozilla profile. Not every system lives on a HDD. That memory stick LED tells me everything I need to know. – usretc Nov 18 '20 at 15:40