From: Rolf Neugebauer <rolf.neugebauer@intel.com>
To: I RATTAN <rattan@cps.cmich.edu>
Cc: rolf.neugebauer@intel.com,
Mark Williamson <Mark.Williamson@cl.cam.ac.uk>,
xen-devel@lists.sourceforge.net
Subject: Re: Re: Need help..
Date: Wed, 21 Apr 2004 18:40:22 +0100 [thread overview]
Message-ID: <1082569222.26374.17.camel@wyvis> (raw)
In-Reply-To: <Pine.GSO.4.58.0404211319400.16194@cps212.cps.cmich.edu>
On Wed, 2004-04-21 at 18:21, I RATTAN wrote:
> I am confused:
>
> dom0 /usr is /dev/hda6
>
> and
>
> dom1 /usr is /dev/sd6 which is mapped to /dev/hda7
>
> does it mean even these are separate physical entities, they
> have to mounted read-only?
if they are separate physical partitions mounting rw should be fine. We
normally just use one /usr partition and mount it ro to all domains.
to things to get closer to the root of your problem:
can you show us the output of 'mount' in dom0?
can you change the LABEL= entries in /etc/fstab to contain the /dev/hda*
partition names.
depending on how you created your partitions you might have multiple
partitions with the same label. I generally avoid using labels and use
the explicit devices.
Thanks
Rolf
> -ishwar
>
>
> On Wed, 21 Apr 2004, Mark Williamson wrote:
>
> > Hi there,
> >
> > > Warning: one or more hard disk extents are
> > > writeable by two or more domains simultaneously.
> >
> > 1) You need to set /usr as read only in both fstabs, i.e.
> > in dom0:
> > LABEL=/usr /usr ext3 defaults,ro 1 2
> >
> > in the other domain:
> > /dev/sda6 /usr ext3 defaults,ro 1 2
> >
> > Reboot dom0 so this change gets noticed.
> >
> > 2) Make sure you don't have /dev/hda8 mounted AT ALL in dom0 and make sure you
> > don't mount it while the other domain is running.
> >
> > That should fix you up.
> >
> > Cheers,
> >
> > Mark
> >
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-04-21 17:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 0:45 Re: Need help Neugebauer, Rolf
2004-04-21 15:29 ` I RATTAN
2004-04-21 16:05 ` Mark Williamson
2004-04-21 17:21 ` I RATTAN
2004-04-21 17:40 ` Rolf Neugebauer [this message]
2004-04-22 2:28 ` I RATTAN
2004-04-22 15:07 ` I RATTAN
2004-04-27 18:56 ` problems with latest unstable Kip Macy
2004-04-28 0:28 ` Ian Pratt
2004-04-28 1:24 ` Kip Macy
2004-04-28 2:15 ` Ian Pratt
2004-04-28 2:22 ` Nuno Silva
2004-04-28 6:52 ` Keir Fraser
2004-05-16 0:24 ` stopping a domain Kip Macy
2004-05-16 7:48 ` Keir Fraser
2004-05-16 18:53 ` Kip Macy
2004-05-31 20:38 ` scheduler panic Kip Macy
2004-05-31 21:27 ` Keir Fraser
2004-05-31 21:46 ` Kip Macy
2004-05-31 22:24 ` Ian Pratt
2004-05-31 22:39 ` Kip Macy
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=1082569222.26374.17.camel@wyvis \
--to=rolf.neugebauer@intel.com \
--cc=Mark.Williamson@cl.cam.ac.uk \
--cc=rattan@cps.cmich.edu \
--cc=xen-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.