On Feb 1, 2008 12:42 AM, Bent Terp <[EMAIL PROTECTED]> wrote:
> On Jan 31, 2008 6:21 PM, Akemi Yagi <[EMAIL PROTECTED]> wrote:
> > This problem does not seem to be associated with specific hardware as
> > implied in the original thread.
>
> I did not intend to imply any such thing, at least not as
Bent Terp wrote:
> Issue remains open, although I'm sligthly embarassed about it now,
> given that linux backends are also affected.
>
> When we built a .6 kernel without the 5 nfs patches, nfsstat output
> reverted, but I don't know about the actual performance, yet. Probably
> we can rerun those
On Feb 1, 2008 10:54 AM, Johnny Hughes <[EMAIL PROTECTED]> wrote:
> Bent Terp wrote:
> > Good point, thanks Johnny! We've verified that here; problem does not
> > occur when mounting a Linux nfs-share, and does occur when mounting a
> > Celerra nfs-share.
Tunrs out that nfsstat wasn't telling us t
Bent Terp wrote:
On Jan 30, 2008 5:25 PM, Johnny Hughes <[EMAIL PROTECTED]> wrote:
In any event, I can not duplicate the problem with an nfs export on c4
or c5 and connecting with a c5 client, regardless of the kernel using i686.
Good point, thanks Johnny! We've verified that here; problem doe
On Jan 31, 2008 6:21 PM, Akemi Yagi <[EMAIL PROTECTED]> wrote:
> This problem does not seem to be associated with specific hardware as
> implied in the original thread.
I did not intend to imply any such thing, at least not as far as the
client is concerned, we've verified this on different hardwa
On Jan 31, 2008 10:28 AM, nate <[EMAIL PROTECTED]> wrote:
> Akemi Yagi wrote:
>
> > This problem does not seem to be associated with specific hardware as
> > implied in the original thread. The person on the SciLinux mail list
> > has Dell machines, and I was able to confirm the issue using custom
Akemi Yagi wrote:
> This problem does not seem to be associated with specific hardware as
> implied in the original thread. The person on the SciLinux mail list
> has Dell machines, and I was able to confirm the issue using custom
> built boxes. I have added a note in the bug tracker at:
>
> htt
On Jan 30, 2008 4:01 PM, Akemi Yagi <[EMAIL PROTECTED]> wrote:
> On Jan 30, 2008 8:25 AM, Johnny Hughes <[EMAIL PROTECTED]> wrote:
> > Joshua Baker-LePain wrote:
> > > On Wed, 30 Jan 2008 at 10:18am, Johnny Hughes wrote
> > >
> > >> Bent Terp wrote:
> > >
> > >>> Has something changed with regard t
On Jan 31, 2008 2:09 PM, Bent Terp <[EMAIL PROTECTED]> wrote:
> On Jan 31, 2008 1:17 PM, William L. Maltby <[EMAIL PROTECTED]> wrote:
> > Still, we can't believe that an option you've never changed, and
> > apparently worked before, and is not specifically (in)excluded as
> > (un)supported is unsup
On Jan 31, 2008 1:17 PM, William L. Maltby <[EMAIL PROTECTED]> wrote:
> Still, we can't believe that an option you've never changed, and
> apparently worked before, and is not specifically (in)excluded as
> (un)supported is unsupported now. :-(
No I suppose not, so we went and rechecked with noati
On Jan 31, 2008 1:17 PM, William L. Maltby <[EMAIL PROTECTED]> wrote:
> Good luck with it.
Thanks mate - "do no believe in miracles - rely on them!"
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
On Thu, 2008-01-31 at 12:12 +0100, Bent Terp wrote:
> On Jan 30, 2008 5:39 PM, William L. Maltby <[EMAIL PROTECTED]> wrote:
> > According to man pages for mount and nfs, *atime is not a supported
> > mount option for NFS. *If* I read correctly.
AA
TG I
On Jan 30, 2008 5:25 PM, Johnny Hughes <[EMAIL PROTECTED]> wrote:
> In any event, I can not duplicate the problem with an nfs export on c4
> or c5 and connecting with a c5 client, regardless of the kernel using i686.
Good point, thanks Johnny! We've verified that here; problem does not
occur when
On Jan 30, 2008 5:39 PM, William L. Maltby <[EMAIL PROTECTED]> wrote:
> According to man pages for mount and nfs, *atime is not a supported
> mount option for NFS. *If* I read correctly.
I don't agree. noatime is listed in the general section of man mount,
and those options should then exist (but
On Jan 30, 2008 8:25 AM, Johnny Hughes <[EMAIL PROTECTED]> wrote:
> Joshua Baker-LePain wrote:
> > On Wed, 30 Jan 2008 at 10:18am, Johnny Hughes wrote
> >
> >> Bent Terp wrote:
> >
> >>> Has something changed with regard to the mount options? We use
> >>> (rw,noatime,rsize=8192,wsize=8192,hard,udp,
On Wed, 2008-01-30 at 10:25 -0600, Johnny Hughes wrote:
> Joshua Baker-LePain wrote:
> > On Wed, 30 Jan 2008 at 10:18am, Johnny Hughes wrote
> >
> >> Bent Terp wrote:
> >
> >>>
> Has something changed with regard to the mount options? We use
> >>> (rw,noatime,rsize=8192,wsize=8192,hard,udp,conte
Joshua Baker-LePain wrote:
On Wed, 30 Jan 2008 at 10:18am, Johnny Hughes wrote
Bent Terp wrote:
Has something changed with regard to the mount options? We use
(rw,noatime,rsize=8192,wsize=8192,hard,udp,context="system_u:object_r:httpd_sys_content_t:s0)
which has worked fine until now.
I
On Wed, 30 Jan 2008 at 10:18am, Johnny Hughes wrote
Bent Terp wrote:
Has something changed with regard to the mount options? We use
(rw,noatime,rsize=8192,wsize=8192,hard,udp,context="system_u:object_r:httpd_sys_content_t:s0)
which has worked fine until now.
I am trying to duplicate your op
Bent Terp wrote:
On 1/24/08, Karanbir Singh <[EMAIL PROTECTED]> wrote:
Bent Terp wrote:
Hi all!
Just a word of warning: after updating a few of our x86_64 based web
frontend boxes to the new kernel, we began to get weird MySQL
timeouts. The problem went away again when we downgraded to the
pre
On 1/24/08, Karanbir Singh <[EMAIL PROTECTED]> wrote:
> Bent Terp wrote:
> > Hi all!
> >
> > Just a word of warning: after updating a few of our x86_64 based web
> > frontend boxes to the new kernel, we began to get weird MySQL
> > timeouts. The problem went away again when we downgraded to the
> >
Bent Terp wrote:
Hi all!
Just a word of warning: after updating a few of our x86_64 based web
frontend boxes to the new kernel, we began to get weird MySQL
timeouts. The problem went away again when we downgraded to the
previous kernel-2.6.18-53.1.6.el5.x86_64.rpm
A bit more info / context wou
Hi all!
Just a word of warning: after updating a few of our x86_64 based web
frontend boxes to the new kernel, we began to get weird MySQL
timeouts. The problem went away again when we downgraded to the
previous kernel-2.6.18-53.1.6.el5.x86_64.rpm
regards,
Bent Terp
22 matches
Mail list logo
