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
> WARNING: / was not properly unmounted
> Automatic boot in progress: starting file system checks.
> /dev/rsd0a: INCORRECT BLOCK COUNT I=21267992 (448 should be 384) (CORRECTED)
> PARTIALLY TRUNCATED INODE I=21267993
> /dev/rsd0a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY.
> Automatic file system check failed; help!
> Enter pathname of shell or RETURN for sh:
> Terminal type? vt100
> # ulimit -dH unlimited
> # fsck_ffs -y /dev/rsd0a
> ** /dev/rsd0a
> cannot alloc 30231937 bytes for typemap
> # ulimit -a
> time(cpu-seconds) unlimited
> file(blocks) unlimited
> coredump(blocks) unlimited
> data(kbytes) 65536
> stack(kbytes) 4096
> lockedmem(kbytes) 236424
> memory(kbytes) 705612
> nofiles(descriptors) 64
> processes 80
> #
>
> however just ulimit -d unlimited worked
Yep, my advise was not completely correct,
-Otto
>
> # ulimit -d unlimited
> # ulimit -d
> 1048576
> # fsck_ffs -y /dev/rsd0a
> ** /dev/rsd0a
> ** Last Mounted on /
> ** Root file system
> ** Phase 1 - Check Blocks and Sizes
> INCORRECT BLOCK COUNT I=21267992 (448 should be 384)
> CORRECT? yes
>
> PARTIALLY TRUNCATED INODE I=21267993
> SALVAGE? yes
>
> INCORRECT BLOCK COUNT I=21267996 (8864 should be 8832)
> CORRECT? yes
>
> INCORRECT BLOCK COUNT I=21267997 (1152 should be 1120)
> CORRECT? yes
> [..]
>
> thanks!!
>
> nate
