The AFS Cache has never been fully tested with ext3, but it should still die on system shutdown. What version of the OpenAFS are you using? Recent 1.2.x releases shouldn't have this shutdown problem (which _did_ exist in earlier versions).
Note that this assumes that you "shutdown" the machine, not just AFS. -derek Helge Bahmann <[EMAIL PROTECTED]> writes: > Hello list! > > Is there some wicked interaction with the afs cache manager and ext3, or > is this "normal" for unclean shutdown? > > Today I had to reboot the afs fileserver (Debian Woody, afs-client and > -server 1.2.3), though for reasons external to afs. > > During shutdown "something" kept /afs busy, I don't know what; as a result > the afs client could not be stopped, kernel module could not be unloaded > and afsd could not be terminated, also keeping /var busy (where the afs > cache is located). > > At system startup /var was garbled so badly that journal recovery could > not bring the filesystem back into a consistent state, only manually > fscking the thing brought it back to life. > > What I have learned is to put the cache into its own partition but I am > dismayed that openafs-client appears to be unable to handle this situation > sanely -- is this true or am I having just bad luck? > > Regards > -- > Helge Bahmann <[EMAIL PROTECTED]> /| \__ > The past: Smart users in front of dumb terminals /_|____\ > _/\ | __) > $ ./configure \\ \|__/__| > checking whether build environment is sane... yes \\/___/ | > checking for AIX... no (we already did this) | > > _______________________________________________ > OpenAFS-info mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-info -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH [EMAIL PROTECTED] PGP key available _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
