From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Used space in bytes
Date: 9 Nov 2000 12:39:14 -0800 [thread overview]
Message-ID: <8uf21i$ro7$1@cesium.transmeta.com> (raw)
In-Reply-To: <20001109191843.B11373@atrey.karlin.mff.cuni.cz>
Followup to: <20001109191843.B11373@atrey.karlin.mff.cuni.cz>
By author: Jan Kara <jack@suse.cz>
In newsgroup: linux.dev.kernel
>
> Hello.
>
> I sent similar email a few weeks ago but discussion ended without
> any useful results if I rememeber well.
>
> Quota in reiserfs is (and needs to be) accounted in bytes not in blocks.
> I modified quota system to allow such thing so in kernel there's no
> problem. But also 'quotacheck' needs to know how many space does given
> file use. Currently it uses st_blocks from stat(2) to compute the space
> used but for reiserfs we need precision in bytes, not in 512 byte blocks...
> My proposal is to alter stat64() syscall to return also number of bytes
> used (I tried to contact Ulrich Drepper <drepper@redhat.com> who should
> be right person to ask about such things (at least I was said so) but go
> no answer...). Does anybody have any better solution?
> I know about two others - really ugly ones:
> 1) fs specific ioctl()
> 2) compute needed number of bytes from st_size and st_blocks, which is
> currently possible but won't be in future
>
Report a block size (really allocation unit size) st_blocks == 1?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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/
next prev parent reply other threads:[~2000-11-09 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 18:18 Used space in bytes Jan Kara
2000-11-09 20:39 ` H. Peter Anvin [this message]
2000-11-09 21:03 ` Miquel van Smoorenburg
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 19:31 Petr Vandrovec
2000-11-14 17:39 ` Jan Kara
2000-11-14 18:55 Petr Vandrovec
2000-11-14 18:25 ` Jan Kara
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='8uf21i$ro7$1@cesium.transmeta.com' \
--to=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox