From: Joe Marzot <gmarzot@nortelnetworks.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] 2.4.24-2 UML problems with hostfs ClearCase mounts [ was Re: [uml-devel] uml-patch-2.4.24-3]
Date: Mon, 17 May 2004 11:37:39 -0400 [thread overview]
Message-ID: <40A8DC43.5060001@nortelnetworks.com> (raw)
In-Reply-To: 40A4B26F.8080507@nortelnetworks.com
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.
very strange - 2.4.24-1 patch seems to work fine with these Clearcase
host filesystems.
I tries with 2.4.24-3 but did not even get it too boot but this is
likely some other issue.
regards, GSM
Joe Marzot wrote:
> Jeff Dike wrote:
>
>> gmarzot@nortelnetworks.com said:
>>
>>> I wonder based on what you say here if two UMLs that hostfs mount the
>>> same directory and access the same file...one for reading, and the
>>> other for writing, if the first will see the updates written by the
>>> second....or maybe I am misinterpretting.
>>
>>
>>
>> You are correct, the writer will cache the new data, and the reader
>> won't see
>> it until it's flushed out somehow. If you can arrange to have the
>> writer sync the filesystem before the reader reads the files, then it
>> will get up-to-date information.
>>
>> Otherwise, if this is a problem, we need to make hostfs optionally
>> synchronous.
>
>
> Yes - I think there is value in that.
>
> On a different but related topic. I am trying the 2.4.24-2 patch to see
> if it helps with the kernel panics I posted about in a previous thread
> but I am now seeing some odd failures with hostfs. Granted my seetup is
> a bit odd (i.e., atypical).
>
> I am mounting Clearcase vobs using view extended pathnames. I have a
> little script that mounts a whole series of Clearcase vobs...after the
> script some are mounted and some are not...Clearcase implements these
> view extended pathnames as a virtual filsystem (mvfs) and there must be
> something about that which makes the mounting fail
> occasionally...mouinting other host filesystems works as before. note:
> mounting the CC mvfs vobs worked in 2.4.24-1 with no problem.
>
> I will try again with 2.4.24-3 (w/ fsync - hopefully I can find the
> right place(s)) and report on that...
>
> regards, GSM
>
>>
>> Jeff
>>
>>
>
>
>
-------------------------------------------------------
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-17 15:37 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 ` Joe Marzot [this message]
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 ` [uml-devel] 2.4.24-2 UML problems with hostfs ClearCase mounts Joe Marzot
2004-05-18 16:26 ` 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=40A8DC43.5060001@nortelnetworks.com \
--to=gmarzot@nortelnetworks.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.