Can't kill hung remote CP copy

[Alan Cox]

> Amazing.  Not in a good way.
> The corruption would be at the client end, correct?
> Is there a reason that the client could not just report back
> "taking to long to mount" and leave its data uncorrupted?
> 
> Would similar corruption take place if the process had just
> termintated itself without waiting for NFS to succeed?

With properly written apps NFS soft and intr etc are all fine. The
problem is that a lot of apps are badly written and don't check for short
writes to disk or for close() erroring.

Same apps that break on disk full.

Alan