Find out how much data is waiting to be written to disk

grep ^Dirty /proc/meminfo
Ever ask yourself "How much data would be lost if I pressed the reset button?" Scary, isn't it?
Sample Output
Dirty:            488064 kB

By: h3xx
2011-08-24 08:48:49

What Others Think

davidpgero · 503 weeks and 4 days ago
grep ^Dirty /*/meminfo # works on my system #but ls /*/meminfo or eacho /*/meminfo only show a single file on my system.
Jessehz · 503 weeks and 4 days ago
grep ^Dirt /*/m*i* #may not work on other systems #I'm running Ubuntu 11.04 AMD64
Jessehz · 503 weeks and 4 days ago
RanyAlbeg · 503 weeks and 4 days ago
@RanyAlbeq: You just wish you'd thought of it.
h3xx · 503 weeks and 3 days ago
@h3xx lol. Well said.
DaveQB · 503 weeks and 3 days ago
To salve your conscience use sync to write back data manually...
hons · 502 weeks and 3 days ago
i usually watch grep -e Dirty: -e Writeback: /proc/meminfo (just for the sake of it), should one be aware of any incompatibilities?
x0a · 128 weeks and 5 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: