828
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Apr 2024
828 points (97.4% liked)
Technology
59137 readers
1617 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
A proper journaling filesystem should handle this, but I hardly trust NTFS as it is.
Journaling should make sure that the file system itself doesn't corrupt, but journaling doesn't magically make all writes atomic. If a program is halfway through writing a file and the power is cut, that file will be corrupt.
As a user. When I want the computer to shut down. I've got my programs already closed. I really don't care if there's a half open log file or some telemetry isn't properly recorded. It needs to shut down now.
By default, Linux can take up to 15 seconds to write a file to disk, this is for power saving reasons. You could corrupt the last document/photo you saved, your browser profile, or your nextcloud sync.
Linux usually shuts down immediately if you don't have any unsaved files and nothing glitches out during shut down. But yeah, windows sucks, corrupt files is probably the least of your problems using Windows.
I guess on Linux, if you run
syncto write all cached files to disk, and then pull the cord, you're probably fine.I like to think of it like this. When I tell the computer to power down its a fair warning. Just like when a UPS sends the alarm signal. Power is going off, you better get in a good state now.