Hi,
I'm running a recent current (a few days old) on a sparc64, with a LFSv2
for sources + build dirs. From time to time lfs_cleanerd start complaining:
add_segment failed segment xxxx: Cannot allocate memory
The segment number isn't always the same:
tail /var/log/messages
Apr  2 18:47:38 java lfs_cleanerd[129]: add_segment failed segment 804: Cannot allocate memory
Apr  2 18:47:38 java lfs_cleanerd[129]: add_segment: lfs_segmapv failed for segment 888
Apr  2 18:47:38 java lfs_cleanerd[129]: add_segment failed segment 888: Cannot allocate memory
Apr  2 18:47:38 java lfs_cleanerd[129]: add_segment: lfs_segmapv failed for segment 1067
Apr  2 18:47:38 java lfs_cleanerd[129]: add_segment failed segment 1067: Cannot allocate memory
Apr  2 18:47:38 java lfs_cleanerd[129]: add_segment: lfs_segmapv failed for segment 1128
Apr  2 18:47:38 java lfs_cleanerd[129]: add_segment failed segment 1128: Cannot allocate memory
Apr  2 18:47:38 java lfs_cleanerd[129]: add_segment: lfs_segmapv failed for segment 1200
Apr  2 18:47:38 java lfs_cleanerd[129]: add_segment failed segment 1200: Cannot allocate memory
Apr  2 18:47:39 java lfs_cleanerd[129]: add_segment: lfs_segmapv failed for segment 1193

When it started complaining this way the VSZ of 129 was around 85MB (limit
is at 128, hard at 1G). umounting the FS, killing cleanerd and remounting
fix the problem for a short time (it only seems to happen when there's some
activity though) ...

Any idea ?

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--