linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Miranda Hamburger <fabmirha@ns.isi.ulatina.ac.cr>
To: linux-c-programming@vger.kernel.org
Subject: du and ls
Date: Sat, 2 Jun 2007 01:58:04 +0000 (UTC)
Date: Tue, 5 Jun 2007 00:57:38 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706050051290.29079@ns.isi.ulatina.ac.cr> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed, Size: 405 bytes --]

Hello,

I am curious about the mismatch between du and ls. Apparently, du reports 
amount of 512 or 1024-K blocks, and ls lists the absolute value.

But, why in some cases, a 1100 bytes file is reported by du as 4 x 512 
bytes instead of 3 x 512bytes

I note both use fstat().

Thanks for advice,

---
Fabio Andrés Miranda
Ingeniería en sistemas informáticos
Universidad Latina - Costa Rica

             reply	other threads:[~2007-06-02  1:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02  1:58 Fabio Miranda Hamburger [this message]
2007-06-02 11:06 ` du and ls Glynn Clements
2007-06-02 23:09   ` Fabio Miranda Hamburger
2007-06-04  7:12     ` Glynn Clements

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0706050051290.29079@ns.isi.ulatina.ac.cr \
    --to=fabmirha@ns.isi.ulatina.ac.cr \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).