16
submitted 1 day ago* (last edited 1 day ago) by ___@lemm.ee to c/selfhosted@lemmy.world

So I recently muxed a bluray with mkvmerge, and proceeded to copy it to my nas with proxmox and cockpit smb server with a mount bind passed through from my host zraid.

I have 500 files on here, and have had a similar issue once before with a different movie mux file (ignored back then). I’m on Ublue Aurora fedora. Shares are smb mounted locally.

What happens is this: I copy the file, it gets to 100% and hangs. The proxmox smbd spawns a ton of PIDs and the unprivileged LXC wont shutdown or stop until the host is rebooted (which takes 5 mines of slow waiting). All 4 cores mapped to the lxc get pegged to 100% and adding 2 more for a total of 6 pegs those too.

After rebooting, copying the file again will cause the issue every time. I have another cockpit smb NAS on a privileged container on entirely different hardware, different setup that does the same exact thing when I copy this remux file. The file copies over fine to an SMB QNAP share. Copies over fine from a windows box to the Proxmox NAS, so isolated to the dolphin file copy or mkvmerge mux copy on Fedora to Proxmox LXC smb share.

I assume it’s something with Fedora and this file, but don’t know what it is. The machine froze afterwards once, so I’m wondering if it’s bad ram potentially. 128GB off brand ECC.

Anyone experienced something similar before?

you are viewing a single comment's thread
view the rest of the comments

You've probably got a filesystem flag off somewhere in this chain of mounts. It sounds like the handoff from smb to filesystem has an issue.

Possibly similar: https://github.com/openzfs/zfs/issues/14391

[-] ___@lemm.ee 3 points 23 hours ago

This is what I’m thinking. The file originally overwrote an older one, I muxed in and synced truehd audio into the original and ended up copying it back after forgetting a subtitle track. It definitely went back and forth with the same name a few times. It’s probably something with the Unix ACLs. Still concerning that it crashes the SMB daemon.

[-] just_another_person@lemmy.world 0 points 23 hours ago

I would honestly run network services closest to the OS to avoid any issues. If it goes away, there ya go. If not, start digging at Samba+Docker+ZFS config options.

this post was submitted on 25 Oct 2024
16 points (94.4% liked)

Selfhosted

39772 readers
373 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS