grep ^Dirty /proc/meminfo

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

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

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

These Might Interest You

What Others Think

good!
davidpgero · 352 weeks and 1 day ago
grep ^Dirty /*/meminfo # works on my system #but ls /*/meminfo or eacho /*/meminfo only show a single file on my system.
Jessehz · 352 weeks and 1 day ago
grep ^Dirt /*/m*i* #may not work on other systems #I'm running Ubuntu 11.04 AMD64
Jessehz · 352 weeks and 1 day ago
Stupid.
RanyAlbeg · 352 weeks and 1 day ago
@RanyAlbeq: You just wish you'd thought of it.
h3xx · 352 weeks and 1 day ago
@h3xx lol. Well said.
DaveQB · 352 weeks ago
To salve your conscience use sync to write back data manually...
hons · 351 weeks 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?

commandlinefu.com 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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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: