Messages in this thread | | | Subject | Re: SV: Lockups with 2.4.14 and 2.4.16 | Date | Wed, 12 Dec 2001 01:22:03 +0000 (GMT) | From | Alan Cox <> |
| |
> BTW, these commands don't work over SSH, ie the '&' doesn't produce a > background job + report-when-finished when running like: > ssh badserver "touch /foo &" > If I run without '&', would that just touch a file somewhere in the > cache-memory, ie not flushed to disk, or would it still detect if a disk is > hung? What's the point of running it in the bg anyway?
I was thinking "from a shell". Doing it with two ssh commands should show which one if either hangs
> Is there any chance the lockup could be with one of the IDE disks running > swap or backups? Could that produce a global lockup of this kind?
I think its a reiserfs/quota/dac960 deadlock though which is open to question at the moment - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |