Anders Lennartsson <d...@lennartsson.se> writes: > When shutting down a freshly installed openafs-client machine the > openafs module crashed. Details from the syslog are below. The > particular circumstances were as follows:
> 1) Client machine was freshly installed with squeeze. > Only basic packages were installed, no desktop, fileserver etc. > Afs services configured to start at boot time. > 2) Some files were copied from a afs server which acts both as > dbserver and fileserver. The file server runs lenny with openafs > packages from backports. > 3) Afs server was shutdown (hardware problems). > 4) Afs client was shutdown without problem. > 5) Afs client was started, afs server was not. > 6) Afs client machine works normally. > 7) Afs client machine shutdown. Afs module crashed: > Dec 27 12:10:04 tv init: Switching to runlevel: 0 > Dec 27 12:10:05 tv kernel: [ 8287.213136] COLD shutting down of: CB... afs... > BkG... CTrunc... AFSDB... RxEvent... md: md2 still in use. Hi Anders, I'm going to forward this bug upstream. It's been my past experience that whenever the shutdown message says "COLD", trouble is ahead and the shutdown often crashes. I don't know what causes cold shutdowns instead of the normal warm shutdowns; hopefully upstream can figure out what's going on. > The problem seems to be repeatable. After this crash I started > the afs client and tried to stop afs services with > /etc/init.d/openafs-client stop > and the machine frooze with a message on the screen wich was similar to > the one above. It was not in the logs but I photographed it and can provide > it if deemed useful. Once AFS shutdown has crashed once, you're generally hosed until you do a clean reboot. Have you rebooted this system since? Can you reproduce the problem again after a reboot? -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
