On Wed, 2011-01-05, at 16:39:11 -0800, Russ Allbery wrote: > Anders Lennartsson <d...@lennartsson.se> writes: > > > 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.
Hello Thanks for pointing out this detail with the COLD shutdown. I have not seen that before. > > 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? Yes it was reproducible after a reboot. Crash was as in total crash. No keyboard function, no ssh login etc. But the power button functioned :) The first time I noticed this was when I asked the machine to shutdown, where the afs crash stopped the shutdown sequence. After a forced rebooting I made an attempt to shutdown the OpenAFS service only, something which repeatably (well, three times in a row) crashed the client machine totally and forced a power button induced reboot. This was as long as the OpenAFS server was shutdown. Once new disks to the server arrived and an OS was installed, including OpenAFS db-server and fileserver, and the server machine was up and running, I could start and shutdown OpenAFS client services on the client machine normally. I had not changed or updated any packages in the meantime. All the files I had backuped on the client machine transferred back to the server over afs without problem, I compared checksums after copying into afs. A few more details that may (or may not) be important: The client machine is a Pentium4 running Squeeze i386, (686 kernel). I have a laptop that runs Squeeze amd64 and it is also an OpenAFS client, but the client is not set to start at boot time. But when I start afs services I normally don't shut them down each time I bring the laptop away. Occasionally I reboot and a running afs client has never caused any problems if it cannot contact the server at client shutdown, nor computer shutdown. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
