From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: Linux 3.0-rc1 - what Xen components went in. Date: Thu, 16 Jun 2011 14:00:35 -0400 Message-ID: <20110616180035.GA10270@dumpdata.com> References: <20110531161224.GA1340@dumpdata.com> <20110616T113336.GA.bd449.stse@fsing.rootsland.net> <20110616150706.GA6275@dumpdata.com> <20110616T190614.GA.1ac46.stse@fsing.rootsland.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20110616T190614.GA.1ac46.stse@fsing.rootsland.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, Jun 16, 2011 at 07:31:43PM +0200, Stephan Seitz wrote: > On Thu, Jun 16, 2011 at 11:07:06AM -0400, Konrad Rzeszutek Wilk wrote: > >On Thu, Jun 16, 2011 at 11:48:20AM +0200, Stephan Seitz wrote: > >>The 3.0-rc2 compiled and started without problems, even the DomU > >>started. But when I looked at the DomU console I noticed that the > >>system had problems with the filesystems. ext3 and ext4 partitions > >>produced journal errors and got mounted read only. > >Hmm, are barriers somehow being turned on? (They shouldn't). It would > >be helpfull if you included the error logs. >=20 > At least with 2.6.36.4-DomU barriers seems to be enabled: > blkfront: xvda1: barriers enabled (tag) > blkfront: xvda2: barriers enabled (tag) > blkfront: xvda5: barriers enabled (tag) > blkfront: xvda6: barriers enabled (tag) > blkfront: xvda7: barriers enabled (tag) > blkfront: xvda8: barriers enabled (tag) That is wrong. It should not have turned them on. The 3.0 version does not export the feature-barrier at all. Looks like a bug in xen-blkfront in 2.6.36 .. >=20 > xvda1 is ext3 (root fs) with the mount option barrier=3D1, but this > doesn=E2=80=99t seem to work (EXT3-fs: barriers not enabled). The other > filesystems are ext4 without explicit barrier options and don=E2=80=99t= have > log output concerning barriers. Uh, what? Do you see the errors if the barriers are turned off. As in -o barrier=3D0 or -o writeback=3D1 >=20 > For now I can=E2=80=99t make tests since I=E2=80=99m not at home for th= e next days. > Then I will try to get logs as well. Since the filesystems are > changed to read only, the logs are not written to disk, so I have to > use other methods. Uh, you can log the output from the kernel using the 'xl crreate -c'. You might need to edit the Linux command line options.. >=20 > >I don't try to put disks as partitions. Let me try that. Are the sizes > >that xne-blkfront report the same? >=20 > xen-blkfront? Is this a program or kernel output? Dom0 or DomU? kernel output. >=20 > >Ah, hadn't tried LUKS. What happens if they are _not_ on LUKS? >=20 > For now I can=E2=80=99t try it. Besides /boot in Dom0 all my partitions= are > LUKS encrypted. OK? Can you try in a week or so? I am going to try to reproduce LUKS here= . You could just create new partition. >=20 > >>The DomU kernel is a 2.6.36.4 vanilla kernel. I noticed that I can=E2= =80=99t > >>use a newer kernel. Every kernel > 2.6.36 crashes the DomU > >>immediatley (I don=E2=80=99t even get a console). The log said that D= omU was > >>crashing too fast, so it was disabled to avoid loops. This happens > >>with 2.6.34.8 as Dom0 kernel and with 3.0-rc2. > >Can you boot it with 'earlyprintk=3Dxenboot debug loglevel=3D10' pleas= e? >=20 > Is this a boot option I pass to the DomU kernel? I will do the test > next week. Yes. >=20 > >Are you using a special version of .config? Is it available somewhere? >=20 > http://fsing.rootsland.net/~stse/config-2.6.38.3-DomU (not working) > http://fsing.rootsland.net/~stse/config-2.6.36.4-DomU (working) >=20 > Thanks for your help. >=20 > Shade and sweet water! >=20 > Stephan >=20 > --=20 > | Stephan Seitz E-Mail: stse@fsing.rootsland.net | > | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel