From: Nick Craig-Wood <ncw1@axis.demon.co.uk>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] A quick humfs HOWTO
Date: Thu, 8 Apr 2004 10:54:32 +0100 [thread overview]
Message-ID: <20040408095432.GA10043@axis.demon.co.uk> (raw)
In-Reply-To: <200404080207.i3827rbe009294@ccure.user-mode-linux.org>
On Wed, Apr 07, 2004 at 10:07:52PM -0400, Jeff Dike wrote:
> As the readers of uml-devel are aware by now, there is a new virtual UML
> filesystem called humfs.
Sounds like a good solution to lots of problems to me ;-)
Do you think it is easy / possible to make UML boot off a loop mounted
filesystem which is stored in humfs? This would be an easy migration
path...
> The superblock file has the format
> "version <number>\nused <number>\ntotal <number>\n"
>
> The version is currently 1. used is set to the disk space consumed by
> everything in the data directory. total is set arbitrarily when you set
> up the filesystem. It is the size of the filesystem as seen within
> UML.
Does uml actually obey this total in the superblock? Ie does this
setting act as a quota?
And an idea...
Why not make each of the files in the metadata directory a symlink and
store the metadata in the symlink itself? I believe that there is room in
the inode for short symlinks so you'll save inodes there. Lots of
dangling symlinks might look a bit untidy, but its a technique thats
been used before (eg emacs session files).
See http://www.charmed.com/txt/ext2.txt and in particular
Symbolic links are also filesystem objects with inodes. They
deserve special mention because the data for them is stored within
the inode itself if the symlink is less than 60 bytes long. It uses
the fields which would normally be used to store the pointers to
data blocks. This is a worthwhile optimisation as it we avoid
allocating a full block for the symlink, and most symlinks are less
than 60 characters long.
--
Nick Craig-Wood
ncw1@axis.demon.co.uk
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-04-08 9:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 2:07 [uml-devel] A quick humfs HOWTO Jeff Dike
2004-04-08 6:25 ` Nuno Silva
2004-04-08 8:43 ` Henrik Nordstrom
2004-04-09 18:49 ` BlaisorBlade
2004-04-12 15:06 ` Michael Richardson
2004-04-13 6:51 ` Henrik Nordstrom
2004-04-12 15:05 ` Michael Richardson
2004-04-08 7:58 ` [uml-devel] Re: [uml-user] " Rus Foster
2004-04-08 11:23 ` Jeff Dike
2004-04-08 8:35 ` [uml-devel] " Henrik Nordstrom
2004-04-08 11:34 ` Jeff Dike
2004-04-08 12:09 ` Henrik Nordstrom
2004-04-08 9:54 ` Nick Craig-Wood [this message]
2004-04-08 10:07 ` Henrik Nordstrom
2004-04-08 11:41 ` Jeff Dike
2004-04-08 10:26 ` stian
2004-04-08 11:41 ` Jeff Dike
2004-04-08 12:52 ` Jeff Dike
2004-04-08 12:03 ` [uml-devel] " Gerd Knorr
2004-04-08 12:49 ` Jeff Dike
2004-04-08 13:01 ` Gerd Knorr
2004-04-08 13:49 ` Robin Green
2004-04-12 15:11 ` Michael Richardson
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=20040408095432.GA10043@axis.demon.co.uk \
--to=ncw1@axis.demon.co.uk \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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