All,
Apologies in advance if this forward is viewed as
uncouth; I wanted to ask the folks here if they have
had any experience, or have seen the NFS problem
described below (well, linked to below may be a better
explanation...)
The showTasks output lists multiple deadlocked tasks
with a Call Trace in the following condition:
(from the sif029.strings included on the Bugzilla
page)
Call Trace:
[<ffffffffa00c6024>]{:nfs:nfs_complete_unlink+308}
Call Trace: [<ffffffffa00d39c0>]{:nfs:nfs_sops+0}
[<ffffffffa00d3d00>]{:nfs:nfs_fs_type+0}
Ideas? Suggestions? I've also opened a ticket with
internal Redhat support to see if they have any
hypothesis.
Thanks,
--Greg
>
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145550
>
> Summary: NFS lockups/hangs on RHEL3
> x86_64 U4
> Product: Red Hat Enterprise Linux
> Version: 3
> Platform: x86_64
> OS/Version: Linux
>
>
> Description of problem:
>
> We have a group of 10 systems to distribute builds
> (gcc). When these
> systems are under heavy load, the builds (make
> process) hang in a
> blocked, deadlocked state.
>
> The NFS servers do not show excessive load or any
> problems.
>
> NFS gcc source: NetApp Release 6.4.5P2
> NFS build source: NetApp Release 6.5.2R1P9:
>
> The 10 build clients are exactly the same hardware
> and configuration.
> I'll be attaching the following from a system that
> is exhibiting this
> behavior:
>
> # lspci -vv
> # lsmod
> # cat /proc/meminfo
> # cat /proc/cpuinfo
> # uname -a
>
> And as much as I can capture from the console as
> possible.
>
> Unfortunately, we cannot recreate the hang
> on-demand.
>
> Please let me know if there is any other information
> I can provide
> that would be helpful.
>
> Version-Release number of selected component (if
> applicable):
>
> Redhat Enterprise Linux 3 Update 4 x86_64
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
greg-
your mail just got through the nfs exploder.
this is a known issue on RHEL 3.0, RH bugzilla 138182.
> -----Original Message-----
> From: gb [mailto:[email protected]]=20
> Sent: Monday, January 24, 2005 5:35 PM
> To: [email protected]
> Subject: [NFS] NFS lockups/hangs on RHEL64 U4 ?
>=20
>=20
>=20
> All,
>=20
> Apologies in advance if this forward is viewed as
> uncouth; I wanted to ask the folks here if they have
> had any experience, or have seen the NFS problem
> described below (well, linked to below may be a better
> explanation...)
>=20
> The showTasks output lists multiple deadlocked tasks
> with a Call Trace in the following condition:
>=20
> (from the sif029.strings included on the Bugzilla
> page)
>=20
> Call Trace:
> [<ffffffffa00c6024>]{:nfs:nfs_complete_unlink+308}=20
>=20
> Call Trace: [<ffffffffa00d39c0>]{:nfs:nfs_sops+0}
> [<ffffffffa00d3d00>]{:nfs:nfs_fs_type+0}=20
>=20
> Ideas? Suggestions? I've also opened a ticket with
> internal Redhat support to see if they have any
> hypothesis.
>=20
> Thanks,
>=20
> --Greg=20
>=20
> >
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D145550
> >=20
> > Summary: NFS lockups/hangs on RHEL3
> > x86_64 U4
> > Product: Red Hat Enterprise Linux
> > Version: 3
> > Platform: x86_64
> > OS/Version: Linux
> >=20
> >=20
> > Description of problem:
> >=20
> > We have a group of 10 systems to distribute builds
> > (gcc). When these
> > systems are under heavy load, the builds (make
> > process) hang in a
> > blocked, deadlocked state.
> >=20
> > The NFS servers do not show excessive load or any
> > problems.
> >=20
> > NFS gcc source: NetApp Release 6.4.5P2
> > NFS build source: NetApp Release 6.5.2R1P9:
> >=20
> > The 10 build clients are exactly the same hardware
> > and configuration.
> > I'll be attaching the following from a system that
> > is exhibiting this
> > behavior:
> >=20
> > # lspci -vv
> > # lsmod
> > # cat /proc/meminfo
> > # cat /proc/cpuinfo
> > # uname -a
> >=20
> > And as much as I can capture from the console as
> > possible.
> >=20
> > Unfortunately, we cannot recreate the hang
> > on-demand.
> >=20
> > Please let me know if there is any other information
> > I can provide
> > that would be helpful.=20
> >=20
> > Version-Release number of selected component (if
> > applicable):
> >=20
> > Redhat Enterprise Linux 3 Update 4 x86_64
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from=20
> real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> NFS maillist - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
>=20
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs