From: Joe Marzot <gmarzot@nortelnetworks.com>
To: Henrik Nordstrom <uml@hno.marasystems.com>
Cc: Joe Marzot <gmarzot@nortelnetworks.com>,
Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] 2.4.24-2 UML problems with hostfs ClearCase mounts
Date: Tue, 18 May 2004 11:43:02 -0400 [thread overview]
Message-ID: <40AA2F06.6020607@nortelnetworks.com> (raw)
In-Reply-To: Pine.LNX.4.44.0405180141460.28239-100000@filer.marasystems.com
Thank you so much for the reply - For the most part existing hostfs
support has been fine for me (I need the sync behaviour).
However with 2.4.24-1 I am still getting kernel panic crashes and it
looked like some crashes were handled in 2.4.24-2. I will try to pick
through the 2.4.24-2 patch and take just the not hostfs parts.
I do have loads of cores if anyone is interested since I hacked the
panic code to abort() as I was not catching these intermittent crashes
very often.
regards, Giovanni
Henrik Nordstrom wrote:
> On Mon, 17 May 2004, Joe Marzot wrote:
>
>
>>A little more data on this one - the behaviour I see with these mounts
>>is that
>>
>>mount -t hostfs none /mnt/mybob -o /view/myview/vob/myvob
>>
>>succeeds but mounts the hosts / dir instead of the desired view extended
>>pathname of the ClearCase vob.
>
>
> This is a known bug in 2.4.24-2. A patch can be found in the archives or
> from http://marasystems.com/download/uml/
>
> If you need hostfs then you should probably stick to 2.4.24-1 for the time
> being. Jeff is doing some heavy restructuring of the uml host file access
> methods while adding the humfs and as a result of this the hostfs support
> has become very unstable while the combined supporting framework for humfs
> and hostfs is taking shape. Hopefully this will soon result in a much
> better hostfs than before, but at the moment things is a bit shaky..
>
> Regards
> Henrik
>
>
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&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-05-18 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 22:08 [uml-devel] uml-patch-2.4.24-3 Jeff Dike
2004-05-12 23:09 ` roland
2004-05-13 0:14 ` Sven 'Darkman' Michels
2004-05-13 0:33 ` roland
2004-05-13 21:01 ` Joe Marzot
2004-05-14 1:43 ` Jeff Dike
2004-05-14 11:50 ` Joe Marzot
2004-05-17 15:37 ` [uml-devel] 2.4.24-2 UML problems with hostfs ClearCase mounts [ was Re: [uml-devel] uml-patch-2.4.24-3] Joe Marzot
2004-05-17 23:50 ` [uml-devel] 2.4.24-2 UML problems with hostfs ClearCase mounts Henrik Nordstrom
2004-05-18 4:54 ` [uml-devel] how to do programming in UML pronoy debnath
2004-05-18 8:07 ` roland
2004-05-18 15:43 ` Joe Marzot [this message]
2004-05-18 16:26 ` [uml-devel] 2.4.24-2 UML problems with hostfs ClearCase mounts Henrik Nordstrom
2004-05-18 17:54 ` Jeff Dike
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=40AA2F06.6020607@nortelnetworks.com \
--to=gmarzot@nortelnetworks.com \
--cc=jdike@addtoit.com \
--cc=uml@hno.marasystems.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