I think I just got a panic
Eirik Nygaard
eirikn at dragonflybsd.org
Thu Oct 21 09:21:58 PDT 2004
On Wed, Oct 20, 2004 at 04:07:55PM -0700, Matthew Dillon wrote:
>
> :But I was running X at the time :( X froze and stayed there for about 10
> :seconds or something, then the computer rebooted. Probably a panic?
> :
> :For whatever it's worth I was just doing a buildworld, X with a couple
> :of xterms open (icewm) and I had a samba share mounted. I was ssh'd into
> :another machine in one of the xterms and was about to vi /etc/gettytab
> :locally when it locked up and rebooted.
> :
> :I've now set dumpdev in rc.conf. Is that enough to atleast save a dump,
> :so I can tell for sure if it was a panic or not, incase it happens again?
> :--
>
> Note that the system will attempt to store the crash dump in /var/crash.
> If /var/crash does not have sufficient space, the system will not be
> able to save a crash dump. What most people do is:
>
> cpdup /var/crash /usr/var.crash
> rm -rf /var/crash
> ln -s /usr/var.crash /var/crash
>
> or
>
> cpdup /var/crash /home/var.crash
> rm -rf /var/crash
> ln -s /home/var.crash /var/crash
>
> So /var/crash has enough space.
>
> That's actually something we should fix in the installer... to make sure
> that /var has enough space to hold crash dumps (a nominal ~2-3x the space
> would be good if it doesn't eat too much from other partitions. i.e. if
> the disk is big enough).
>
> -Matt
> Matthew Dillon
> <dillon at xxxxxxxxxxxxx>
How about we just set the new deault to end up in /usr/crash ? I don't see any
particular reason for the crashdumps to end up in /var (which often is too small).
--
Eirik Nygaard
More information about the Users
mailing list