This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Clint, I've made the following changes to papagayo to resolve these issues; - modified /etc/vfstab to enable logging on all mounted filesystems This will create a filesystem journal that will likely take care of this problem completely. This will start on next reboot - ran "mount -o remount,logging" to convert all currently mounted feilesystems to logging (except on reoot which requires reboot) This should prevent corruption when the system is shutdown next. - updated /etc/init.d/ldmd and created shutdown links at all runlevels This should solve the problem -- please advise if you find otherwise. mike On Mar 5, 11:30am, Unidata Support wrote: > Subject: 20030305: papagayo not unmounting /home > > ------- Forwarded Message > > >To: address@hidden > >From: Clint Rowe <address@hidden> > >Organization: UCAR/Unidata > >Keywords: 200303042252.h24Mqd316047 > > Mike: > > when I need to reboot papagayo, I run into a problem with (I > think) the ldm's home directory not unmounting properly. I get a > "/home busy" message during shutdown and the shutdown stops. > Eventually, I have to kill the system and always end up needing to > do a manual fsck upon reboot. Have you or anyone else run into > this? Can you suggest a solution? > > Clint