[5053] in Athena Bugs
3 ways to panic AFS
daemon@ATHENA.MIT.EDU (John Carr)
Mon Jun 4 10:44:45 1990
To: bugs@ATHENA.MIT.EDU, bug-afs@ATHENA.MIT.EDU
Date: Mon, 04 Jun 90 10:44:28 EDT
From: John Carr <jfc@ATHENA.MIT.EDU>
All these are for 7.0, but the last 2 at least have always been problems.
# cd /afs
# umount /afs
# ls
the kernel responds:
panic: afsglobalvfs
The AFS filesystem is not considered busy no matter how many file
descriptors or texts are using it. The unmount call should check this.
# rm /usr/vice/cache/<random file name>
eventually the kernel will (1) panic because it fails to open the cache file
or (2) clobber the contents of whatever file reused the cache file's inode
number.
# umount /usr/vice/cache (or the filesystem containing this directory)
very quickly the kernel will panic because it failed to open a cache file.
This is a similar problem to the first: there is nothing marking the
filesystem busy. It would be sufficient to hold open the file with the
cache map.
