SUMMARY: fsck allocation error

From: Ann Cantelow <cantelow_at_athena.csdco.com>
Date: Sat, 04 Mar 2000 15:32:07 -0700 (MST)

Hi.

My problem was this error, when trying to fsck a file system after a power
failure:

   /sbin/ufs_fsck /dev/rrz0c
   ** /dev/rrz0c
   cannot alloc 200256002 bytes for lncntp

Many thanks to Steve Hancock, who sent the below solution, saying that
there is likely a shortage of per-process memory for fsck to work with.
I increased that to some 350 Mbytes and rebooted, but still got the same
error. The disk set just had a few days of news binaries on it, so I ran
newfs on it, to avoid interrupting other processes going on on the machine
with further reboots. There were no problems to fsck the disk set after
that, so we're ok for now.

Best,

Ann Cantelow


From: Steve Hancock <shancock_at_zk3.dec.com>
-----------------------------------------------
The lncntp is a structure used by fsck to internally perform some
bookkeeping while it is doing its job. It looks like it could not
allocate enough memory for it to begin the fsck process. I can think
of two reasons why this could happen:

1) You have eager mode swapping enabled and you don't have enough
virtual memory (physical memory+swap) to allocate it.

2) Your process limit is too small. The default process data size limit
is 128MB, so I would say this is your problem. You can work around this
by upping this limit in your shell, or in sysconfitab. The latter
would require a reboot. For example:

# sysconfig -q proc per_proc_data_size
proc:
per_proc_data_size = 134217728

So, edit sysconfitab to alter it and reboot.
-------------------------------------------------
Received on Sat Mar 04 2000 - 22:32:59 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:40 NZDT