Original Message :
------------------------------------------------------------------------
----------------------------------------
One of our developers here was testing a new program. The program
crashed and seems to have somehow locked out the file system that it was
writing some files to. All attempts to access the file system, even just
running an 'ls', end up with the processes becoming 'uninterruptible
sleeping processes' according to 'ps'. Has anybody come across similar
problems and has anybody got any ideas on how to cure this problem
without rebooting? I realise from previous postings that we probably
can't kill the processes, but is there any way that we can free up the
file system? We're running DU4.0B on an AlphaServer 4100. All help
greatly appreciated.
------------------------------------------------------------------------
----------------------------------------
Many thanks to the following for replying:-
Ana Pedraz; Scott B Skeate; John F Marten and Susan Rodriguez.
The original process that failed still seems to be the most likely
culprit for the problem. Initial talks with Digital suggest that it may
be a bug in mmap(), but this has not been verified in any way yet. In
the end, the knock-on effects of the file system lockout meant that we
had to reboot the system. We could find no other way to 'unlock' the
file system and 'free' the uninterruptible processes.
Thanks again to those who replied.
Regards,
Sean
Sean McGlynn (TMIAU)
email smcgly_at_acxiom.co.uk
phone +44 (0)171 378 7244 x.3118
fax +44 (0)171 378 6525
Received on Mon Mar 09 1998 - 14:36:51 NZDT