Timeline for Are file edits in Linux directly saved into disk?
Current License: CC BY-SA 4.0
33 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 14, 2024 at 7:18 | answer | added | U. Windl | timeline score: 0 | |
| Aug 25, 2018 at 3:58 | comment | added | Sergiy Kolodyazhnyy |
If I may add so, some files may be memory mapped ( with mmap() syscall), which I think is often used on large files for improved performance, and edits may occur there in memory.
|
|
| Aug 24, 2018 at 14:21 | answer | added | Peter Cordes | timeline score: 6 | |
| Aug 24, 2018 at 11:23 | history | edited | Jeff Schaller♦ | CC BY-SA 4.0 |
spelling fixes; phrasing simplification
|
| Aug 24, 2018 at 9:00 | history | tweeted | twitter.com/StackUnix/status/1032915512647401472 | ||
| Aug 24, 2018 at 6:00 | comment | added | phuclv | this applies to any modern OS and would be better posted on superuser.com | |
| Aug 23, 2018 at 14:31 | vote | accept | JuanRocamonde | ||
| Aug 23, 2018 at 13:29 | history | edited | JuanRocamonde | CC BY-SA 4.0 |
added 23 characters in body
|
| Aug 23, 2018 at 13:27 | history | reopened |
Stephen Kitt ilkkachu Kiwy dr_ Stephen Rauch |
||
| Aug 23, 2018 at 13:24 | history | edited | JuanRocamonde | CC BY-SA 4.0 |
added 23 characters in body
|
| Aug 23, 2018 at 13:22 | comment | added | JuanRocamonde | Also, judging by the great interest of users on it, my impression is that they do see it as a rather beneficial question, if that is the way to put it. | |
| Aug 23, 2018 at 13:20 | comment | added | JuanRocamonde | It is true that as it is it may be a bit broad, @JeffSchaller; I'm going to try to edit it a bit; however, honestly if the site is not for this type of questions, that directly address Linux functioning, then what is it for? | |
| Aug 23, 2018 at 13:19 | comment | added | JuanRocamonde | As @AnthonyGeoghegan pointed out, I don't consider this question a request for learning materials. I think it's rather specific; I did not ask for a long and deep explanation or a manual about Linux filesystems; only about a brief idea that I wanted to clear out. | |
| Aug 23, 2018 at 13:17 | history | edited | JuanRocamonde | CC BY-SA 4.0 |
added 23 characters in body
|
| Aug 23, 2018 at 12:21 | comment | added | Jeff Schaller♦ | While I don't agree that it's a request for learning materials, I do think the question is a little Broad in its current form. Limit the scope to Linux distributions (or whatever specific OS) and possibly limit it to certain storage technologies and filesystems. | |
| Aug 23, 2018 at 12:05 | review | Reopen votes | |||
| Aug 23, 2018 at 13:27 | |||||
| Aug 23, 2018 at 11:17 | history | closed |
Kusalananda♦ schily muru Siva Dmitry Grigoryev |
Not suitable for this site | |
| Aug 23, 2018 at 10:12 | answer | added | sourcejedi | timeline score: 9 | |
| Aug 23, 2018 at 5:32 | comment | added | Peter - Reinstate Monica | A last issue concerns what you mean by "turning off" the computer. Exactly for the reasons discussed, modern machines' power button triggers an orderly operating system shutdown both on Linux and Windows, which includes syncing the disks. (The "real" power button of the transformer is on the back side and normally not used.) If you "turn off" your computer the official way -- as opposed to pulling the plug --, all changes to file systems are physically written to disk; this means that all drives, including USB sticks, are synced and can be safely removed. | |
| Aug 23, 2018 at 4:26 | comment | added | Peter - Reinstate Monica | As an aside, Joerg Mittag below is correctly pointing out that modern disks have their own cache which is opaque (transparent? whatever) to the operating system. Just pulling the plug from a disk during a write can corrupt its contents, and the OS can do nothing. | |
| Aug 23, 2018 at 4:23 | comment | added | Peter - Reinstate Monica | All you say is true, and more. Just pulling the power plug on your computer has always been a BAD IDEA in capitals on *nix machines and even on PCs. What's much worse than simply losing edits to a file is that pulling the rug from under your operating system that way may corrupt the whole file system. Administrative information like allocated blocks and directory contents is scattered throughout the disk; if it is only partly updated, resulting in an inconsistent before/after mix, it's "corrupt" and may stop working altogether, worst case. | |
| Aug 23, 2018 at 2:41 | comment | added | crasic |
The cache is opaque to the user, in the best case you must sync, and applications must flush to guarantee caches are written back, but even a sucessfull sync does not guarantee write back to physical disk only that kernel caches are flushed to disk, which may have latency in the driver or disk hardware (e.g. on-drive cache that you lose)
|
|
| Aug 22, 2018 at 21:25 | answer | added | Jörg W Mittag | timeline score: 18 | |
| S Aug 22, 2018 at 21:11 | history | edited | ilkkachu | CC BY-SA 4.0 |
Copy edited (e.g. ref. <http://en.wikipedia.org/wiki/Operating_system> and <https://en.wikipedia.org/wiki/Solid-state_drive>).
|
| S Aug 22, 2018 at 21:11 | history | suggested | Peter Mortensen | CC BY-SA 4.0 |
Copy edited (e.g. ref. <http://en.wikipedia.org/wiki/Operating_system> and <https://en.wikipedia.org/wiki/Solid-state_drive>).
|
| Aug 22, 2018 at 21:06 | comment | added | Anthony Geoghegan | FAO: Close Vote queue reviewers. This is not a request for learning materials. See unix.meta.stackexchange.com/q/3892/22812 | |
| Aug 22, 2018 at 21:03 | review | Suggested edits | |||
| S Aug 22, 2018 at 21:11 | |||||
| Aug 22, 2018 at 17:46 | history | edited | Kusalananda♦ | CC BY-SA 4.0 |
Spelling
|
| Aug 22, 2018 at 17:32 | answer | added | ilkkachu | timeline score: 74 | |
| Aug 22, 2018 at 17:15 | review | Close votes | |||
| Aug 23, 2018 at 11:20 | |||||
| Aug 22, 2018 at 16:54 | answer | added | RalfFriedl | timeline score: 14 | |
| Aug 22, 2018 at 16:35 | review | First posts | |||
| Aug 22, 2018 at 16:50 | |||||
| Aug 22, 2018 at 16:34 | history | asked | JuanRocamonde | CC BY-SA 4.0 |