Re: An nfs/automount Oops

From: Trond Myklebust (trond.myklebust@fys.uio.no)
Date: Wed Apr 19 2000 - 05:51:46 EST


>>>>> " " == Olaf Titz <olaf@bigred.inka.de> writes:

> Just had one that looks somewhat similar. Trigger was an NFS
> mount called by automount. NFS was in use at that point
> already. The system locked hard on trying to shut down after
> that.

> Linux 2.3.99-pre3, K6, autofs4.

> [lockd:__insmod_lockd_S.bss_L1480+162638/52537609]
> [do_umount+233/336] [umount_dev+126/252] [sys_umount+185/196]
> [sys_oldumount+11/16] [system_call+52/64] Apr 19 11:00:13
> bigred kernel: Code: c7 40 1c f4 ff ff ff ff 73 1c e8 c7 bc fb
> ff 83 c4 04 8d 43

All reports I've seen on this particular problem seem to involve
autofs passing a corrupted superblock to umount.

Just in case though: is anybody seeing this particular type of Oops
using ordinary mount/umount (no autofs, no amd, ...)?

Cheers,
  Trond

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:14 EST