From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: stian@nixia.no
Subject: Re: [uml-devel] df -h and hostfs
Date: Wed, 12 Jan 2005 18:33:03 +0100 [thread overview]
Message-ID: <200501121833.03286.blaisorblade@yahoo.it> (raw)
In-Reply-To: <50806.80.203.0.208.1105530488.squirrel@80.203.0.208>
On Wednesday 12 January 2005 12:48, stian@nixia.no wrote:
> (ops, forgot reply-all)
>
> df -h inside UML: (/etc/mtab is symlinked to /proc/mounts)
> Filesystems Size Used Avail Use% Mounted on
> rootfs 496M 11M 460M 3% /
> /dev/root 496M 11M 460M 3% /
> /dev/ubd/disc1/part1 187G 146G 33G 82% /a
> a 7.3G 6.2G 717M 90% /a/lost+found
> /root/UML/a 7.3G 6.2G 717M 90% /a/lost+found
What has happened here? Why there are two entries on the same mount point? One
mount over the other?
> mount inside UML:
> rootfs on / type rootfs (rw)
> /dev/root on / tyoe ext3 (ro)
> none on /dev/ type devfs (rw)
> /dev/ubd/disc1/part1 on /a type ext2 (rw)
> a on /a/lost+found type hostfs (rw)
> noen on poroc type proc (rw,nodiratime)
How did you mount that folder on /a/lost+found? You wanted, probably, to do:
mount <whatever> > /a/lost+found -t hostfs -o /root/UML/a (or "-o /a", if UML
is chrooted inside /root/UML).
But it seems that you forgot the -o /root/UML/a part and assumed that could be
given on the first part... even /proc/mounts contains most mount options.
I've had just re-checked that even when the root is passed with -o, that is
used even for the mount-point. And now I've actually ran the test...
> df -h on host:
>
> Filesystems Size Used Avail Use% Mounted on
> /dev/hda2 7.3G 6.2G 717M 90% /
> none 126M 0 126M 0% /dev/shm
> 192.168.1.1:/var/home/stian
> 147G 104G 37G 75% /root/UML/a
> mount on host
> /dev/hda2 on / type xfs (rw,noatime)
> none on /dev type devfs (rw)
> none on /proc type proc (rw)
> noen on /dev/shm type tmpfs (rw)
> 192.l68.1.1:/var/home/stian on /root/UML/a type nfs (rw,addr=192.168.1.1)
> The problem is the nfs partition you can see, that is mounted inside UML
> again as hostfs. (This setup is a recovery of a broken disk where I wanted
> the cow layer when testing recoverytools and dumping out files they
> found). The UML-kernel itself is 2.6.10-rc3-mm1 with the patch-set from
> the web-pages dated back 1-2 weeks ago.
> Stian
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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:[~2005-01-12 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 11:48 [uml-devel] df -h and hostfs stian
2005-01-12 17:33 ` Blaisorblade [this message]
2005-01-12 18:22 ` stian
2005-01-12 18:36 ` Blaisorblade
2005-01-13 9:23 ` stian
-- strict thread matches above, loose matches on Subject: below --
2005-01-11 10:11 stian
2005-01-12 0:10 ` Blaisorblade
2005-01-12 14:56 ` Henrik Nordstrom
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=200501121833.03286.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=stian@nixia.no \
--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