Skip to content

Comment on Linux kernel cgroups writeback high CPU troubleshootingparent

Comments

Or run `sync` after the copy "finishes" -- less focused, but very easy to do.

sync is not guaranteed to do anything. And sometimes it does way more than it should. Direct I/O semantics are the correct thing here because it bypasses the cache entirely.

I've had a lot of issues writing partition and disk images using DD on modern Linux systems because of caching. And these all kept happening even though I would use `sync` like you describe. But setting oflag=direct resolved all of the issues I was having.

The article states this doesn't change anything.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.