We are grasping at straws here. A production system crashed this a.m.,
nothing in any log anywhere except the fact that at around 4:00 a.m.
/usr/sbin/defragcron failed due to a filesystem being full. Has anyone *EVER*
had an instance where defragcron failed and subsequent problems were traced
back to this failure? How does defragcron do its work - can it leave a
filesystem in an unstable state?
This is on a DU 4.0D system with fairly recent patches.
TIA!
--
Judith Reed
jreed_at_appliedtheory.com
(315) 453-2912 x335
Received on Mon Aug 03 1998 - 15:09:42 NZST