Mailinglist Archive: opensuse (6210 mails)

[Sid Boyce <sboyce@xxxxxxxxxxxxxxxx>]

Randall R Schulz wrote:
> Rejaine,
>
> On Tuesday 18 October 2005 08:24, Rejaine Monteiro wrote:
> > Hi,
> >
> > about my problems with nfsserver (see message "nfsserver hangs
> > randomly" on this list)  I can see this errors on /proc on all nfsd
> > process:
> >
> > # cat /proc/proc_number/Status | grep -v State
> >
> >           State:  D (disk sleep)
> >
> > What's it?
>
> It's what the parenthetical says: A process sleeps in a D state when 
> it's waiting for disk I/O. In practice, it is not necessarily a disk 
> per se that's being waited for, but what all use of D sleeps have in 
> common is that the event that ends the sleep will come very quickly 
> (well under one second). When this doesn't happen and a process is seen 
> to persist in a D sleep, it's a de facto sign of a problem. D sleeps 
> and all sleeps at internal priority less than 0 cannot be interrupted 
> by signals.
>
>
> > My problems wiht nfsserver is related below:
>
>
> Randall Schulz

What I've wondered about for a long time is why a method to nuke such 
tasks can't be found. There must be a reason or it would have been done 
a long time ago. A reboot is drastic and disruptive, If such an 
occurrence happened on a mainframe running z/OS, they'd be hell to pay 
when some users find they are without service for the hour and some it 
takes to completely feed such a greedy beast and it aint nice to be at 
the inevitable inquest, not nice for anyone.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot
Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support 
Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks