Re: Unable to fsck after crash - cannot alloc 30231937 bytes for typemap

2007-06-05 Thread Otto Moerbeek
On Tue, 5 Jun 2007, nate wrote: > Otto Moerbeek wrote: > > > go to single user mode, and type > > > > ulimit -dH unlimited > > > > and then run fsck > > > > thanks for the quick reply! but that particular command had no effect: > > [..] > root on sd0a > rootdev=0x400 rrootdev=0xd00 rawdev=0xd02

Re: Unable to fsck after crash - cannot alloc 30231937 bytes for typemap

2007-06-05 Thread nate
Otto Moerbeek wrote: > go to single user mode, and type > > ulimit -dH unlimited > > and then run fsck > thanks for the quick reply! but that particular command had no effect: [..] root on sd0a rootdev=0x400 rrootdev=0xd00 rawdev=0xd02 WARNING: / was not properly unmounted Automatic boot in prog

Re: Unable to fsck after crash - cannot alloc 30231937 bytes for typemap

2007-06-05 Thread Otto Moerbeek
On Tue, 5 Jun 2007, nate wrote: > Hello folks - > > My OpenBSD 4.1/i386 firewall crashed last week(seems to be on the 31st), > fortunately it did not stop passing packets. There is no log and > the console didn't show anything(serial console). I rebooted it > today, and it came up in single user

Unable to fsck after crash - cannot alloc 30231937 bytes for typemap

2007-06-05 Thread nate
Hello folks - My OpenBSD 4.1/i386 firewall crashed last week(seems to be on the 31st), fortunately it did not stop passing packets. There is no log and the console didn't show anything(serial console). I rebooted it today, and it came up in single user mode telling me to run fsck manually, which I