Article View: comp.unix.shell
Article #4568Re: du How does du work?
From: Paul Russell
Date: Tue, 12 Nov 1996 00:00
Date: Tue, 12 Nov 1996 00:00
19 lines
1712 bytes
1712 bytes
oka@eesun1.tamu.edu (Oka Setiawan) writes: > I have another intriguing fact/question about du. > Why in one of my machine, du will show twice the disk usage than it should? > In another machine (different file server and everything) du works fine. > both running solaris. > That really freak me out. Traditionally, du gives its answers in 512 byte blocks. It is more intuitive for most people to use 1k blocks, thus most `du' variants offer a `-k' option, to use 1k blocks. Many people alias `du' to `du -k'; that may be happening here. Hope that helps, Paul. -- Paul.Russell@RustCorp.com.au "Engineer? So you drive trains?" Lies, damned lies, and out-of-date documentation. Currently contracted to Telstra, Sydney.
Technical Details
Message-ID:
<uyiv7cur4y.fsf@wink.sydney.trl.telstra.com.au>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<55u79a$n5o@gap.cco.caltech.edu> <567lav$sl5@news.tamu.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f8c9b,8c44339d2a70be4e X-Google-Attributes: gidf8c9b,public X-Google-Thread: fc89c,8c44339d2a70be4e X-Google-Attributes: gidfc89c,public X-Google-Thread: f72b0,8c44339d2a70be4e X-Google-Attributes: gidf72b0,public X-Google-Thread: 1012a6,8c44339d2a70be4e X-Google-Attributes: gid1012a6,public X-Google-Thread: 1025b4,8c44339d2a70be4e X-Google-Attributes: gid1025b4,public From: Paul Russell <Paul.Russell@rustcorp.com.au> Subject: Re: du How does du work? Date: 1996/11/12 Message-ID: <uyiv7cur4y.fsf@wink.sydney.trl.telstra.com.au> X-Deja-AN: 195867322 sender: prussell@wink.sydney.trl.telstra.com.au references: <55u79a$n5o@gap.cco.caltech.edu> <567lav$sl5@news.tamu.edu> followup-to: comp.unix.questions organization: Telecom Research Laboratories, Melbourne, Australia. newsgroups: comp.unix.shell,comp.unix.programmer,comp.unix.questions,comp.unix.misc,gnu.misc.discuss