Seriously fuck thumbs.db anywhere it can be found.
THIS IS WHY NTFS HAS ALTERNATE DATA STREAMS, USE THEM YOU FUCKERS YOU CREATED IT.
Alternate data streams look like normal files but with an appended identifier.
For example test.txt:stream1 is an alternate data stream of test.txt. Move or copy the file and the ADS goes with it.
They can be created like other files (“echo > test.txt:stream1”)
You can see them with “dir /r” at the command line.
You can even have an alternate data stream with no corresponding file. In my opinion this is what thumbs.db should have been.
We use Btrfs not NTFS here
Easiest fix, change the folder view to another, like "list", then back and it won't be locked anymore. Might take a second or two, but will unlock.
You mean list? Click these icons and change the folder view from icons to something else, like "list" or "details", then thumbs.db can be deleted without windows bitching.

You can also change under View menu at the top.
Nothing.
If you run fsck (filesystem check), it will look for blocks of data that look like files, but have no actual filename attached. Simplified, that can happen as a result of unexpected shutdowns (like kernel panic) or IO conflicts (where one process deletes the file but the other writes data to where the file used to be). If fsck finds such "lost files", it will put them in lost+found on the respective volume.
If you have trouble with missing files after a crash, it might be worth looking for them there. Otherwise, it probably doesn't matter.
What drives me batty about thumbs.db is that on a modern high end machine with an nvme drive it's not meaningfully faster then just regenerating thumbnails on demand every time, and in fact can be slower under some circumstances. Yet there's no "I don't need this turn it off" option.
What about remote drves though?
For whatever insane windows-y reason, having a thumbs.db file on a network share is one of those slower scenarios for me. Which is odd because you'd expect that to be the kind of situation where it's actually useful.
Meh, that's nothing - just look at the multitude of directories forced upon any storage device you plug into something running Android.
Isn't it just SD cards it automatically prepares to use as an extension of the main filesystem by automatically mirroring the default filestructure onto it?
I usually only plug in SD cards, so I finally just grabbed my SSD to check - same thing happened. What kind of storage devices were you thinking it wouldn't happen to?
Well, I thought it only did it to inserted micro-SD cards, not external storage, but then, I never did plug external storage into a phone, so I guess I was wrong.
Don’t come anywhere near us
What's that? It rings a bell and I've been wondering all thread whether I misremembered the correct name.
The most reliable fingerprint.
It’s a good thing I never created OS file systems because I would have balls.chin files everywhere. Well, the truth is that someone would have forked it just to change that, then I would have raged and abandoned the project, then a competent maintainer would have grabbed it. What a world.
I’m such a Mac user that I don’t even get it. I am simultaneously laughing at myself and embarrassed.
MacOS create these directories to store metadata. But because it starts with a dot, you don’t normally see it.
Right, so anything that might be used with other machines.
ZIP files created with macOS‘ file manager Finder can also contain DS_Store files.
Yes, the idea is to support macOS features on non native file systems.
If you want to look it up, some of this goes back to HFS, a file system with a resource fork and data fork. It allows you to do pretty cool stuff.
Depending on how you interact with your computer, and when you started being a Mac user, I’m not surprised.
Starting at macOS 10.12 16A238m, Finder will not display
.DS_Storefiles (even if you randefaults write com.apple.finder AppleShowAllFiles YESin Terminal to show hidden system files).
It's a file that is never visible on Mac systems, it stands for Desktop Service. It just saves stuff like your zoom settings for the specific folder, metadata for the files in the folder etc
It is automatically generated in every single folder you access on a Mac system that isn't a native Apple file system. So for example a Windows formatted USB stick, or a network share.
It is however visible on non-mac systems as a file called ".DS_Store"
On Unix and Unix-like systems when a file or directory name starts with a . its hidden by default.
This convention is maintained in the UI for MacOS so you don't see the .DS_Store directory unless you ask to show hidden files.
Apparently not even then, in the case of .DS_Store. Another comment quoted from Wikipedia:
Starting at macOS 10.12 16A238m, Finder will not display
.DS_Storefiles (even if you randefaults write com.apple.finder AppleShowAllFiles YESin Terminal to show hidden system files).
On any non Mac native filesystem I think. Anything that MacOS can read but isn't the original filesystem (it used to be HFS, a long time ago, I have no idea what it is nowadays) will be peppered with those metadata files, disk, floppy, thumb drive, whatever.
.Spotlight-V100 says hello!
@lemmy.ca
Memes about IT and computer related things, funny screenshots, or things you see out in the wild.
go to feed...
@lemmy.ca
Memes about IT and computer related things, funny screenshots, or things you see out in the wild.
go to feed...
Fuckin
thumbs.dbandlost+foundhiding on every USB stick.save