From: stian@nixia.no
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: stian@nixia.no, user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] df -h and hostfs
Date: Thu, 13 Jan 2005 10:23:00 +0100 (CET) [thread overview]
Message-ID: <54814.80.203.0.208.1105608180.squirrel@80.203.0.208> (raw)
In-Reply-To: <200501121936.16890.blaisorblade@yahoo.it>
After I got away the double mounts it seems to be correct. So probably me
that made a mess somewhere that night. I'm done dumping files now so I
could reboot it and recheck the stuff. And the double mounts probably made
the result from df appear wrong, since the kernel walks the mount list
forward when trying to locate the affected filesytems, while all other
file-operations walks it backwards. So it seems to be general
kernel-problem when you have mounted a mount-point two times (Either with
intension or accident)
Stian
-------------------------------------------------------
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-13 9:23 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
2005-01-12 18:22 ` stian
2005-01-12 18:36 ` Blaisorblade
2005-01-13 9:23 ` stian [this message]
-- 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=54814.80.203.0.208.1105608180.squirrel@80.203.0.208 \
--to=stian@nixia.no \
--cc=blaisorblade@yahoo.it \
--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