[lkml]   [2001]   [Dec]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: SV: Lockups with 2.4.14 and 2.4.16
> 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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:14    [W:0.154 / U:0.868 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site