From: John Ripley <jripley@riohome.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Xavier Bestel <xavier.bestel@free.fr>,
VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
Subject: Re: COW fs (Re: Editing-in-place of a large file)
Date: Mon, 10 Sep 2001 02:29:11 +0100 [thread overview]
Message-ID: <3B9C1767.2A35BFD2@riohome.com> (raw)
In-Reply-To: <20010902152137.L23180@draal.physics.wisc.edu> <318476047.20010903002818@port.imtp.ilyichevsk.odessa.ua> <3B9B80E2.C9D5B947@riohome.com> <3B9B9917.DA1CC12F@riohome.com> <1000057292.1867.1.camel@nomade>
Xavier Bestel wrote:
>
> le dim 09-09-2001 at 18:30 John Ripley a _rit :
>
> > /dev/sda6 - /tmp - 210845 blocks, 17697 duplicates, 8.39%
> > /dev/sda7 - /var - 32122 blocks, 5327 duplicates, 16.58%
> > /dev/sdb5 - /home - 220885 blocks, 24541 duplicates, 11.11%
> > /dev/sdc7 - /usr - 1084379 blocks, 122370 duplicates, 11.28%
>
> How many of these blocks actually belong to file data ?
Hmm, good point:
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/sda6 841616 4508 837108 1% /tmp
/dev/sda7 124407 63774 54209 54% /var
/dev/sdb5 855138 677328 177810 79% /home
/dev/sdc7 4191237 3946214 245023 94% /usr
My thinking was that I've managed to run out of space on all of the
partitions in the past and had to prune a lot of stuff... so nearly all
the blocks should contain at least some "likely" data. Still, I guess I
need to verify that this isn't distorting the results. The program needs
to recurse over all files on the filesystem rather than all blocks on a
partition.
--
John Ripley
next prev parent reply other threads:[~2001-09-10 1:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-02 20:21 Editing-in-place of a large file Bob McElrath
2001-09-02 21:28 ` COW fs (Re: Editing-in-place of a large file) VDA
2001-09-09 14:46 ` John Ripley
2001-09-09 16:30 ` John Ripley
2001-09-10 2:43 ` Daniel Phillips
2001-09-10 2:58 ` David Lang
2001-09-09 17:41 ` Xavier Bestel
2001-09-10 1:29 ` John Ripley [this message]
2001-09-10 6:45 ` Ragnar Kjørstad
2001-09-14 10:06 ` Pavel Machek
2001-09-10 11:11 ` Ihar Filipau
2001-09-10 16:10 ` Kari Hurtta
2001-09-14 10:03 ` Pavel Machek
2001-09-10 9:28 ` VDA
2001-09-10 9:35 ` John P. Looney
2001-09-02 21:30 ` Editing-in-place of a large file Ingo Oeser
2001-09-03 0:59 ` Larry McVoy
2001-09-03 1:24 ` Ingo Oeser
2001-09-03 1:31 ` Alan Cox
2001-09-03 1:50 ` Ingo Oeser
2001-09-03 10:48 ` Alan Cox
2001-09-03 14:31 ` Daniel Phillips
2001-09-03 14:46 ` Bob McElrath
2001-09-03 14:54 ` Alan Cox
2001-09-03 15:42 ` Doug McNaught
2001-09-03 15:11 ` Richard Guenther
2001-09-03 21:19 ` Ben Ford
2001-09-03 4:27 ` Bob McElrath
2001-09-03 1:30 ` Daniel Phillips
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=3B9C1767.2A35BFD2@riohome.com \
--to=jripley@riohome.com \
--cc=VDA@port.imtp.ilyichevsk.odessa.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=xavier.bestel@free.fr \
/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).