linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ihar Filipau <philips@iph.to>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: COW fs (Re: Editing-in-place of a large file)
Date: Mon, 10 Sep 2001 14:11:47 +0300	[thread overview]
Message-ID: <3B9C9FF3.7E2770AB@iph.to> (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>

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]


	Is there any FS that have dynamic allocation?

	On one partition can reside a number of FSs and using only needed space? this
would be really cute - HD behaves just like RAM.

	Some FSs on partition just like number files on FS.
	In other words "File Systems' System".

	google and altavista both show nothing...

PS Interesting like academic task. Hm. Will invistigate.

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 ?
>

[-- Attachment #2: Card for Ihar Filipau --]
[-- Type: text/x-vcard, Size: 407 bytes --]

begin:vcard 
n:Filiapau;Ihar
tel;pager:+375 (0) 17 2850000#6683
tel;fax:+375 (0) 17 2841537
tel;home:+375 (0) 17 2118441
tel;work:+375 (0) 17 2841371
x-mozilla-html:TRUE
url:www.iph.to
org:Enformatica Ltd.;Linux Developement Department
adr:;;Kalinine str. 19-18;Minsk;BY;220012;Belarus
version:2.1
email;internet:philips@iph.to
title:Software Developer
note:(none)
x-mozilla-cpt:;18368
fn:Philips
end:vcard

  parent reply	other threads:[~2001-09-10 11:18 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
2001-09-10  6:45         ` Ragnar Kjørstad
2001-09-14 10:06         ` Pavel Machek
2001-09-10 11:11       ` Ihar Filipau [this message]
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=3B9C9FF3.7E2770AB@iph.to \
    --to=philips@iph.to \
    --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;
as well as URLs for NNTP newsgroup(s).