From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: James Harper <james.harper@bendigoit.com.au>,
xen-devel@lists.xensource.com
Subject: Re: -xen config...
Date: Sun, 18 Dec 2005 22:59:46 -0600 [thread overview]
Message-ID: <43A63E42.5050608@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D409DBF@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>>Is there any reason that ext2 is set as 'y' while ext3 is set
>>as 'm'? It seems to me that they (and the other 'common'
>>filesystems) should be the same...
>>
>>
>
>I agree this is pretty odd. The -xen config was based on one for a
>distro kernel, so I think it's standard practice.
>
>Can anyone put forward a good reason not to compile ext3 in?
>
>
I don't know that it matters, but for what it's worth, this shouldn't
create problems.
ext3 is (almost) backwards compatible with ext2. ext2 is suffient to
mount the root device such that modules can be loaded (and then the root
filesystem is actually mounted).
If you watch an Ubuntu boot-up, you'll notice that modules are loaded
before the root file system is mounted as ext2.
This is not likely to be the reason you're seeing filesystem corruption
as if there are any problems with the ext3 filesystem, the ext2 driver
will refuse to mount it (complaining that it contains "unsupported
features").
Can you ellaborate on the filesystem corruption problems you have been
seeing? xm destroy (as opposed to xm shutdown) is an easy way to
corrupt yourself.
Regards,
Anthony
>Ian
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
>
next prev parent reply other threads:[~2005-12-19 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 3:03 -xen config Ian Pratt
2005-12-19 4:59 ` Anthony Liguori [this message]
2005-12-19 8:58 ` Gerd Knorr
-- strict thread matches above, loose matches on Subject: below --
2005-12-19 5:34 James Harper
2005-12-19 5:05 Ian Pratt
2005-12-19 3:14 James Harper
2005-12-18 23:58 James Harper
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=43A63E42.5050608@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=james.harper@bendigoit.com.au \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.