Edit - Unix & Linux Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

That sounds like what I learned... but was it just voodoo or was there really any reason? Some of the other answers give good suggestions as to ways this habit may have formed among us sysadmins

Josh
– Josh

2018-01-11 22:12:38 +00:00
Commented Jan 11, 2018 at 22:12
@Josh the reason was given. "When the sync command exited, the kernel had scheduled the sync, but not all the buffers (including the all-important filesystem superblock) had necessarily made it to the disk." See also: "According to the standard specification (e.g., POSIX.1-2001), sync() schedules the writes, but may return before the actual writing is done." man7.org/linux/man-pages/man2/sync.2.html

sourcejedi
– sourcejedi

2019-03-03 17:50:04 +00:00
Commented Mar 3, 2019 at 17:50

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »