Homelab

371 readers

9 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 1 year ago

MODERATORS

communick@selfhosted.forum

rglullis@communick.news

NTFS seems really sensitive? (alien.top)

submitted 1 year ago by throwaway_t56@alien.top to c/homelab@selfhosted.forum

15 comments fedilink hide all child comments

Hi, I've been running a Ubuntu on Mac Mini homelab for past couple of weeks (Jellyfin, Transmission, SMB), and I keep hitting NTFS issues - some of which were my own fault, but I'm now seeking advice for the future.

I wanted to unmount the drive. Drive was busy (seems it is as long as smbd is running). So I do umount -f, expecting it will kill the process and unmount similar to Unlocker app - it corrupted the entire drive. Didn't work on Windows or Linux, vcn error... After a few days of painful recovery, I set it all back up...
Went to mv a file to a subfolder, got impatient, cancelled it. Tried to remove the partial file - IO error! Couldn't remove it, not after reboot, not as root, no way. And I couldn't access the entire folder because of that one file.

To fix, I had to plug in the drive to the Windows machine, saw the file for a sec, then file disappeared itself (some self-repair system?)

sometimes the drive doesn't appear at all, takes a few repluggings to get it working? On Windows machine it works okay.

Is there any other FS you could recommend? (needs to be Windows compatible as well)

Thank you.

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

[–] johnklos@alien.top 1 points 1 year ago

That's not exactly true. You may be stopping file transactions, but the filesystem handler code should still run until it has flushed its state, and if it doesn't, then that's a huge bug and isn't normal.