Bug 11803 - nfs mounting kills / halts machines
nfs mounting kills / halts machines
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils (Show other bugs)
7.0
i386 Linux
high Severity high
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-05-31 13:55 EDT by raz
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-14 18:46:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description raz 2000-05-31 13:55:08 EDT
all updated packages, 6.2 system.  This has been reproduced on a 266mmx,
pIII 500''s, p2 450''s.. bla bla bla.. none of the machines are smp.

having a remote machine mount a NFS export HALTS the machine.  Machine
will respond to pings... but nothing else... console dies.

Been using linux for almost 5 years now... and I hate to be a whiner.. but
ever since 6.0 on redhat, nfs has been a joke.  Come on guys.. you are
acting as the defacto standard for the linux community and you cant produce
a working nfs?  How does it look when people buy their brand new ''linux''
and install it, and have it crash with simple file sharing.  Use userspace
if knfs isn''t stable... I think we has established that.  Don''t even say
"well the other distros are using it" .. debian ''allows you to'' but warns 
the dickens out of ya first.  The simple fact that 6.2 is advertised as 
stable ... and it is not.  I currently use userspace on my laptop 6.2, my
server is debian.. as with my desktop... when I updated to 6.2, aparently
it _forced_ me to use knfs without even asking.  Alot of server admins are
going to be furious with redhat.
Comment 1 Cristian Gafton 2000-08-08 22:35:27 EDT
assigned to johnsonm

Note You need to log in before you can comment on or make changes to this bug.