--_0157c6ed-d429-4d08-9e8b-87cf4e23dd00_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon=2C 27 Aug 2012 09:46:18 +0200 From: wdh@dds.nl To: users@ovirt.org Subject: [Users] ovirt node & NFS =0A= =0A= =0A= =0A= =0A= =0A= Hi all=2C =0A= =20 =0A= NOTE: Due to an=0A= issue affecting NFS storage domains and the current Linux=0A= 3.5-based Fedora kernel=2C we recommend testing with a Fedora=0A= host running a pre-3.5 version of the Linux kernel.=20 =0A= =20 =0A= Any progress on this issue yet? =0A= =20 =0A= Winfried =0A= =0A= =0A= =0A= _______________________________________________=0A= Users mailing list=0A= Users@ovirt.org=0A= http://lists.ovirt.org/mailman/listinfo/users There is an open Bugzilla about the issue (will try to find the number)=2C = but AFAIK there has not been a kernel update that has been pushed that reso= lves the issue=2C and thus no rebuild ovirt-node. It's at the mercy of ups= tream and testing for now. = --_0157c6ed-d429-4d08-9e8b-87cf4e23dd00_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style><!-- .hmmessage P { margin:0px=3B padding:0px } body.hmmessage { font-size: 12pt=3B font-family:Calibri } --></style></head> <body class=3D'hmmessage'><div dir=3D'ltr'><br><div><div id=3D"SkyDrivePlac= eholder"></div><hr id=3D"stopSpelling">Date: Mon=2C 27 Aug 2012 09:46:18 +0= 200<br>From: wdh@dds.nl<br>To: users@ovirt.org<br>Subject: [Users] ovirt no= de &=3B NFS<br><br>=0A= =0A= =0A= =0A= =0A= =0A= Hi all=2C<br>=0A= <br>=0A= <em>NOTE: Due to <a href=3D"https://bugzilla.redhat.com/show_bug.cgi?id= =3D845660" target=3D"_blank">an=0A= issue</a> affecting NFS =3Bstorage domains and the current Lin= ux=0A= 3.5-based Fedora kernel=2C we recommend testing with a <a href=3D"htt= p://wiki.ovirt.org/wiki/OVirt_3.1_release_notes#Fedora_Host" target=3D"_bla= nk">Fedora=0A= host</a> running a pre-3.5 version of the Linux kernel. <br>=0A= <br>=0A= Any progress on this issue yet?<br>=0A= <br>=0A= Winfried<br>=0A= </em>=0A= =0A= =0A= <br>_______________________________________________=0A= Users mailing list=0A= Users@ovirt.org=0A= http://lists.ovirt.org/mailman/listinfo/users<br><br>There is an open Bugzi= lla about the issue (will try to find the number)=2C but AFAIK there has no= t been a kernel update that has been pushed that resolves the issue=2C and = thus no rebuild ovirt-node. =3B It's at the mercy of upstream and testi= ng for now.<br></div> </div></body> </html>= --_0157c6ed-d429-4d08-9e8b-87cf4e23dd00_--
Hi, On 08/28/2012 08:17 AM, Nicholas Kesick wrote:
There is an open Bugzilla about the issue (will try to find the number), but AFAIK there has not been a kernel update that has been pushed that resolves the issue, and thus no rebuild ovirt-node. It's at the mercy of upstream and testing for now.
My reading of that Bugzilla entry (which, I admit, could be wrong) mentions commits to the trunk of Node which fix the issue. See https://bugzilla.redhat.com/show_bug.cgi?id=845660#c11 Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
On 08/28/2012 01:30 PM, Dave Neary wrote:
Hi,
On 08/28/2012 08:17 AM, Nicholas Kesick wrote:
There is an open Bugzilla about the issue (will try to find the number), but AFAIK there has not been a kernel update that has been pushed that resolves the issue, and thus no rebuild ovirt-node. It's at the mercy of upstream and testing for now.
My reading of that Bugzilla entry (which, I admit, could be wrong) mentions commits to the trunk of Node which fix the issue. See https://bugzilla.redhat.com/show_bug.cgi?id=845660#c11
I thought comment 12 contradicted that -- if not, I'd be happy to test with the master branch.
Cheers, Dave.
-- @jasonbrooks
----- Original Message -----
From: "Jason Brooks" <jbrooks@redhat.com> To: "Dave Neary" <dneary@redhat.com> Cc: "oVirt Mailing List" <users@ovirt.org> Sent: Tuesday, August 28, 2012 11:37:57 PM Subject: Re: [Users] ovirt node & NFS
On 08/28/2012 01:30 PM, Dave Neary wrote:
Hi,
On 08/28/2012 08:17 AM, Nicholas Kesick wrote:
There is an open Bugzilla about the issue (will try to find the number), but AFAIK there has not been a kernel update that has been pushed that resolves the issue, and thus no rebuild ovirt-node. It's at the mercy of upstream and testing for now.
My reading of that Bugzilla entry (which, I admit, could be wrong) mentions commits to the trunk of Node which fix the issue. See https://bugzilla.redhat.com/show_bug.cgi?id=845660#c11
I thought comment 12 contradicted that -- if not, I'd be happy to test with the master branch.
Not fixed yet. Please CC your-self, at least you be updated on that one as well. Alon.
On Tue, 2012-08-28 at 13:30 -0700, Dave Neary wrote:
Hi,
On 08/28/2012 08:17 AM, Nicholas Kesick wrote:
There is an open Bugzilla about the issue (will try to find the number), but AFAIK there has not been a kernel update that has been pushed that resolves the issue, and thus no rebuild ovirt-node. It's at the mercy of upstream and testing for now.
My reading of that Bugzilla entry (which, I admit, could be wrong) mentions commits to the trunk of Node which fix the issue. See https://bugzilla.redhat.com/show_bug.cgi?id=845660#c11
those are vdsm patches, not ovirt-node.
Cheers, Dave.
participants (6)
-
Alon Bar-Lev -
Dave Neary -
Jason Brooks -
Mike Burns -
Nicholas Kesick -
Winfried de Heiden