this post was submitted on 12 Oct 2024
30 points (100.0% liked)

technology

23229 readers
301 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

founded 4 years ago
MODERATORS
 

Hello again! Ya'll are my last hope for help! I've posted to both the proxmox forums and r/proxmox and nobody's responding.

Here's the deal, I built this home media server about a year ago. Took some time to work out the bugs, but I got TrueNAS Scale and Jellyfin on it and started filling it up. A few weeks ago TrueNAS started freezing up, but would work for a little while after a restart, but then it stopped working. I poked around and I found that there needed to be some sort of new EFI boot thing established. I followed it and it worked. A few days later, jellyfin freezes, I can't access the pve GUI or anything, so I do a hard reset. Now proxmox can't launch pve, let alone the GUI. So I've been poking around and found that the drives are at 100% usage, and inodes are at 100% usage (see pic, disk usage is the same % as the inode usage). Digging deeper, I try to find the offending folder in /rpool/ROOT/pve-1, but there are no deeper directories listed. So I drill down into the other pig one /subvol-100-disk-0; this lead me to find a jellyfin metadata library folder with a bunch of small files using up <250 inodes each. I've searched all over the place and haven't been able to figure out what I could delete to at least get pve up and running, and work towards... idk, migrating it to a new larger drive? Or setting up something to automatically clear old files?

At any rate, I'm running 2 old 512gb laptop drives for all the OSs on the server. I have it in a ZFS mirror raid.

PS: Come to think of it, I've had to expand the size of the virtual drive for my jellyfin LXC multiple times now to get the container to actually launch. Seems I know just enough to get myself into trouble.

Someone, please help me rite my pirate ship! pirate-jammin

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 3 days ago (2 children)

Are you using zfs snapshots at all? I have seen similar symptoms with automatic snapshotting that fills a disk and then becomes read-only. this command will show all snapshots: zfs list -r -t snapshot

[–] [email protected] 3 points 3 days ago

Just ran that command, it said "no datasets available".

[–] [email protected] 3 points 3 days ago

I... think? Not entirely clear on what snapshots are, but I think I turned them on by following the tutorials.