mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jeff Shanab <jshanab@earthlink.net>
Cc: Rik van Riel <riel@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Starting a grad project that may change kernel VFS. Early 	research Re: Starting a grad project that may change kernel VFS. Early 	research
Date: Wed, 26 Aug 2009 14:18:50 +0200	[thread overview]
Message-ID: <4A95282A.3020209@s5r6.in-berlin.de> (raw)
In-Reply-To: <4A9427C7.8020009@earthlink.net>

Jeff Shanab wrote:
> Rik van Riel wrote:
>> Hard links have been done like this in pretty much every
>> Unix filesystem since the 1970's.
[...]
> There is no real way to handle this becasue the two files look the same
> to the filesystem.

See above; it has been state of the art since the 70's.  With hardlinks
or symlinks, a graph which represents the FS happens to contain loops.
No rocket science involved.

[...]
> How would I display this information usefully to the user.

Certain file managers display the overall size and the size on disk.
The latter differs from the former due to
  - on-disk format overhead,
  - on-disk compression,
  - hardlinks and symlinks.
If the user copies the directory to another filesystem, the size on disk
will generally change.
-- 
Stefan Richter
-=====-==--= =--- ==-=-
http://arcgraph.de/sr/

      parent reply	other threads:[~2009-08-26 12:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25  1:46 Jeff Shanab
2009-08-25 17:28 ` Rik van Riel
2009-08-25 18:04   ` Jeff Shanab
2009-08-26  1:30     ` Theodore Tso
     [not found]       ` <4A94BF9E.2010101@earthlink.net>
     [not found]         ` <20090826130513.GM32712@mit.edu>
2009-08-26 14:42           ` Jeff Shanab
2009-08-26 15:09             ` Bryan Donlan
2009-08-26 12:18     ` Stefan Richter [this message]

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=4A95282A.3020209@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=jshanab@earthlink.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    /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®