From: Jan Kara <jack@atrey.karlin.mff.cuni.cz>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Used space in bytes
Date: Tue, 14 Nov 2000 19:25:22 +0100 [thread overview]
Message-ID: <20001114192522.A18870@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <CD940355CE7@vcnet.vc.cvut.cz>
In-Reply-To: <CD940355CE7@vcnet.vc.cvut.cz>; from VANDROVE@vc.cvut.cz on Tue, Nov 14, 2000 at 06:55:13PM +0000
> On 14 Nov 00 at 18:39, Jan Kara wrote:
> > Hello.
> >
> > > On 9 Nov 00 at 19:18, Jan Kara wrote:
> > > > 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
> > >
> > > If I may, please do not add it into stat/stat64 structure. On Netware,
> > > computing really used space can take eons because of it has to read
> > > allocation tables to memory to find size. It is usually about 500%
> > > slower than retrieving all other file informations.
> > And how do you fill in st_blocks field?
>
> Currently as st_size / st_blksize. If I'll want to report real used size,
> so that quotas could be built on the top of Netware space restrictions,
> Netware is willing to return size in its allocation blocks after holes
> and compression takes place, but while computation time is afforable for
> open(), it is not for stat()ing thousands of entries in directories.
Hmm.. But that's problem as 'quotacheck' uses stat to get space used by
file... So it won't work on Netware anyway.
Honza
-
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-14 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 18:55 Petr Vandrovec
2000-11-14 18:25 ` Jan Kara [this message]
-- 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-09 18:18 Jan Kara
2000-11-09 20:39 ` H. Peter Anvin
2000-11-09 21:03 ` Miquel van Smoorenburg
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=20001114192522.A18870@atrey.karlin.mff.cuni.cz \
--to=jack@atrey.karlin.mff.cuni.cz \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-fsdevel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®