you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 2 years ago (5 children)

It is very easy to corrupt files doing this.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 9 points 2 years ago (4 children)

    A proper journaling filesystem should handle this, but I hardly trust NTFS as it is.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 2 years ago* (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 2 years ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 2 years ago* (1 child)

    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 sync to write all cached files to disk, and then pull the cord, you're probably fine.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 2 years ago

    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.

  • source
  • parent