Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.


If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

find files larger than 1 GB, everywhere

Terminal - find files larger than 1 GB, everywhere
find / -type f -size +1000000000c
2009-07-05 08:16:16
User: folengo
Functions: find
4
find files larger than 1 GB, everywhere

Alternatives

There are 6 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

In computer science, we measure in units of "powers of two":

one kilobyte is 1024 bytes

one megabyte is 1024*1024 = 1048576 bytes

one gigabyte is 1024*1024*1024 = 1073741824 bytes

Ergo, to find files larger than 1 gigabyte:

find / -type f -size +1073741824c # find files > 1gb

Reference: http://en.wikipedia.org/wiki/Gigabyte

Comment by mpb 273 weeks and 3 days ago

You have one too many -'s:

find / -type -f -size +1000000000c

should be

find / -type f -size +1000000000c

Comment by radarlistener 273 weeks and 2 days ago

@folengo, I think most people assume that "1 GB" means 2^30 bytes rather than 10^9 bytes. Although there's nothing wrong with 10^9 for 1GB (maybe you make hard drives) Maybe you know that since you used the 'c' unit on the size.

I like to think of it this way:

1K = 2^10 bytes (i.e. 10 bits needed to byte-address 1K),

1M = 2^20 bytes,

1G = 2^30 bytes, etc.

As it should, 'find' allows you to specify any size, but the -size option lets you specify units of base-2 sizes so the command

find / -type f -size +1G

will find files larger than 1,073,741,824 bytes rather than 1,000,000,000 bytes.

Comment by bwoodacre 273 weeks and 1 day ago

You can pipe this to ls to find out how big each file actually is:

find / -type f -size +1G | xargs ls -lh
Comment by chrispix 237 weeks ago

Great command, but this xargs won't handle spaces in file names.

Comment by bela83 68 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts