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?

  • BCsven@lemmy.ca
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 days ago

    I had something similar happen with a DVD iso. It would not copy across network, and cpu would skyrocket if I put it on drive another way. For mine it turned out to be the tracker-miner getting hung up on the content indexing. Specifically it was a DVD with a prank menu option. The menu option was “Break my player” which if you chose it would totally lock the DVD player and only fix was unplugging it for a hard power cycle. Somehow whatever code did that was messing with the content indexer

    • LiveLM@lemmy.zip
      link
      fedilink
      English
      arrow-up
      5
      ·
      8 days ago

      whatever code did that was messing with the content indexer

      Those guys were determined you’d get what was on the tin, no matter what