On Friday 09 March 2007 23:52, Modulok wrote:
How do I work-around a situation where cp, hangs forever?
You can try several things:
1) mount read-only and try to copy the data.
dd(1) might be a better choice than cp(1),
read more bellow.
2) unmount and dump(8) the filesystem.
3) use
On Thursday 08 March 2007 13:49, Modulok wrote:
To the best of my knowledge, most processes can be killed explicitly
by kill -s KILL; There are a few which cannot, such as disk i/o
processes. The idea here is data integrity.
A process might be in cannot-be-killed condition while
in kernel e.g.
Thank you for your reply, it was quite informative and very much
appreciated, but the underlying question remains un-answered:
How do you kill a hanged process that (seemingly) cannot be killed because
of the two conditions below?
-It's hanged, so it's not ever going to self terminate.
-It's a
On Friday 09 March 2007 15:28, Modulok wrote:
Thank you for your reply, it was quite informative and very much
appreciated, but the underlying question remains un-answered:
How do you kill a hanged process that (seemingly) cannot be killed because
of the two conditions below?
-It's
...alright then...
How do I work-around a situation where cp, hangs forever?
-Modulok-
On 3/9/07, Nikos Vassiliadis [EMAIL PROTECTED] wrote:
On Friday 09 March 2007 15:28, Modulok wrote:
Thank you for your reply, it was quite informative and very much
appreciated, but the underlying
To the best of my knowledge, most processes can be killed explicitly
by kill -s KILL; There are a few which cannot, such as disk i/o
processes. The idea here is data integrity.
On the rare occasion however, (when attempting to recover data from
corrupt disks for example), I've had a process
