From: Oleg Drokin <green@ixcelerator.com>
To: linux-kernel@vger.kernel.org
Subject: ramfs always reports filesize in blocks to be 0
Date: Thu, 16 Nov 2000 20:29:26 +0300 [thread overview]
Message-ID: <20001116202926.A18336@iXcelerator.com> (raw)
Hello!
Subject says it all, inode->i_blocks always 0, in ramfs, and never updated
(the only updated thing is inode->i_size).
This breaks at least du(1). Ain't it should count blocks too, so that one
can find how much ramfs is consuming in terms of memory by simply issuing
du -ks ramfs_mount_point
Bye,
Oleg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-11-16 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20001116202926.A18336@iXcelerator.com \
--to=green@ixcelerator.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.