[Solved] Possible to lock a folder? To prevent it from being deleted.
Hi there, I'm on Bazzite KDE and recently somehow lost a my "gaming" folder..? No idea how but must gave been user faulty, e.g me. Therefore wondering if it's possible to lock certain folders so that this cannot accidentally happen?
Thanks I might try this! However does this allow for reads/writes from the system? Considering this is a folder for games, the files are constantly changing, such as the game save files etc..
If you'd like to look into it further. the +i flag in chattr is setting an attribute making the file (everything in Linux is a file, so yes this even means directories) immutable. When a file is immutable, it isn't possible to change the ownership, group, name, or permissions of the file, nor will you be able to write, append, or truncate the file.
It's been a while since I've used it, but I don't believe it's possible to have an immutable directory where you can still modify the contents therein, but I may be misremembering that. It would seem unlikely since adding content to the directory should require that you modify the links for the directory, which shouldn't be allowable with an immutable object?
It's possible that the +a chattr attribute may achieve what you'd prefer. I believe that flag will make it so that files (and again, everything in Linux is a file) can be created and modified, but never deleted. I've actually never used this one, but I can foresee how this still may not be ideal for your wishes since updates to games may expect to be able to delete old content which would be thwarted here. 🤷
Others have answered your question - but it may be worth pointing out the obvious - backups. Annoyances such as you describe are much less of a stress if you know you're protected - not just against accidental erasure, but malicious damage and technical failure.
Some people think it's a lot of bother to do backups, but it is very easily automated with any of the very good free tools around (backup-manager, someone's mentioned timeshift, and about a million others). A little time spent planning decent backups now will pay you back one day in spades, it's a genuine investment of time. And once set up, with some basic monitoring to ensure they're working and the odd manual check once in a blue moon, you'll never be in this position again. Linux comes ahead here in that the performance impact from automated backups can be prioritised not to impact your main usage, if the machine isn't on all the time.
It's easy to set up, it takes literally 10 minutes, and if you decide later you want to use something else, you can just uninstall Timeshift and delete its backups. But in the meantime you'll be protected with backups.
It's literally the first thing I install on a new system and it's saved me multiple times from having to do a complete reinstall.
You can reduce likelihood of any known risk with a preventative measure, in this case the permissions and ownership structure. That is good.
Backup does not reduce likelihood of risk.
It does something more wide-reaching, it mitigates against the bad outcome of loss (from most causes).So it defends from many unknown risks as well as known ones, and unexpected failure of preventative measures. It sort of protects you from your own ignorance and complacency.
Not really afaik, you can make file immutable with chattr +i /path/to/something but that means you cannot write to it either, which will probably cause problems.
If you have the space (on a different drive, preferably) you could use Timeshift to create regular snapshots of (parts of) your system. You can restore deleted files like this from even months ago, if you configure it like that.
The first snapshot takes up as much space as all the files you want to save, but every following one only uses as much disk space as the new/changed files since the last snapshot.
Yeah actually this was more simple thanI had imagined, I simply changed it so that the owner(me) can only view the folder and not edit. Which totally works in my use case. Thought it would have been more difficult than just changing this tbh, thanks!
People have already given direct answers, and the indirect answer of 'set up regular automated backups' (which everyone should set up right now if they haven't already), but for the sake of throwing another option out there, people could take a look at 'trash-cli': https://github.com/andreafrancia/trash-cli
(P.S. I know OP might not have actually deleted the files with 'rm', but this addresses a broadly similar issue.)