Eric Worden <[EMAIL PROTECTED]> wrote:
>'kill -9' (or 'kill -s KILL' for the mnemonic-dependent) does not work.
>
>I have a UNIX book that says in a footnote, "...kill may not always
>work...for instance, if the process invoked a device driver that is stuck
>waiting for a response from the device
'kill -9' (or 'kill -s KILL' for the mnemonic-dependent) does not work.
I have a UNIX book that says in a footnote, "...kill may not always
work...for instance, if the process invoked a device driver that is stuck
waiting for a response from the device. In that case the signal will wait
indefin
Eric Worden ([EMAIL PROTECTED]) wrote:
> Now the program responds to nothing, not even KILL. To make things more
> interesting, I got the bright idea to mount the floppy again, so now two
> processes are in limbo. Is there a graceful way to solve this problem??
First: thou shelt not remove mou
Eric Worden wrote:
> I was using git, and while things seemed to be idle I snuck the floppy out
> to peak at the label. I put it back in. Then after the next operation I
> got:
>
> kernel panic: msdos_write_inode: unable to read i-node block
> floppy0: disk absent or changed during operation
> e
00 (PDT)
To: debian-user@lists.debian.org
Subject: Dumb; help! I removed a mounted floppy
I was using git, and while things seemed to be idle I snuck the floppy out
to peak at the label. I put it back in. Then after the next operation I
got:
kernel panic: msdos_write_inode: unable to read i-node bl
I was using git, and while things seemed to be idle I snuck the floppy out
to peak at the label. I put it back in. Then after the next operation I
got:
kernel panic: msdos_write_inode: unable to read i-node block
floppy0: disk absent or changed during operation
end_request: I/O error, dev 02:00,
6 matches
Mail list logo
