TIL you can't resize dm-cache's underlying volume >.<
Maybe using lvmcache wasn't the best idea...
Can we have overlayfs but copy-up is triggered by reads too, not just writes?
hmm actually that wouldn't do the trick either, I need write-through.
Or even an invalidating write-around.
I tend to dump a bunch of stuff on my NAS only to never look at it again.
hmm ok apparently this was an lvm2 limitiation that was removed in a later version?
https://gitlab.com/lvmteam/lvm2/-/commit/5ec24dfb0bb0c9e48d59d6fbb83262a7087964e1
Of course LVM 2.03.11 that's in Debian 11 is the last one that had the limitation.
So it looks like if I upgraded to Debian 12 I could resize cached LVs without any issues.
But I vaguely remember Debian 12 drops one of the packages I need... argh...
Right, cadvisor.
There's no cadvisor in Debian 12.
@wolf480pl You can't install it separately?
$ ldd /bin/cadvisor
linux-vdso.so.1
libpthread.so.0
libdl.so.2
libzstd.so.1
libc.so.6
/lib64/ld-linux-x86-64.so.2
I guess I could just grab or build any cadvisor binary out there, put it in an otherwise empty .deb, and it'd work, it's not like these libs have backwards-incompatible changes often...
@sjb oh, I forgot I'm actually using different cadvisor in /usr/local/bin which I built from source becaues the one in debian had a bug... duh...