SV: Lockups with 2.4.14 and 2.4.16

["Johan Ekenberg" <johan@ekenberg.se>]

> Another thing to try is
>
> touch /foo &
> hit return
> (should report it finished)
> touch /var/spool/foo &
> (if this never returns you know you /var/spool choked for some reason)

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?

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?

## /etc/fstab:
/dev/rd/c0d0   /           reiserfs   defaults,usrquota,noatime,notail 1 1
/dev/rd/c0d1   /var/spool  reiserfs   defaults,usrquota,noatime,notail 1 1
/dev/hdb1      /backup     reiserfs   defaults,noatime,notail 0 0
/dev/hda1      /boot       ext2       defaults  1  1
/dev/hda2      swap        swap       defaults  0  0
/dev/hda3      swap        swap       defaults  0  0
none           /dev/pts    devpts     gid=5,mode=620  0   0
none           /proc       proc       defaults   0   0

Best regards,
/Johan Ekenberg