aces it with code to find
and delete the newdirblk dependency so that the truncation can
succeed. This delta should clear up the recent problems that
folks have been having with soft updates.
Kirk McKusick
=-=-=-=-=
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: worklist_remove pa
> Check your disk label. I got burned a few months back on a fairly old
> install where I created swap first, then root. This causes the swap
> partition to start at sector 0, with root straight after. For some reason,
> sysinstall or the kernel decided to += 64k on the start address of the swa
Peter Wemm <[EMAIL PROTECTED]> wrote:
> For some reason, sysinstall or the kernel decided to += 64k on the
> start address of the swap partition (to avoid swap clobbering the
> fdisk, bootblocks, etc at the start of the disk), but neglected to
> remove 64k from the size.
This could be undone. S
David Malone wrote:
> On Sat, May 26, 2001 at 09:25:32PM +0200, Dag-Erling Smorgrav wrote:
> > No dump (dumps seem to have been broken for about a month now), but a
> > stacktrace from DDB:
>
> Crashdumps have been working for me recently, (apart from the fact
> that they overrun the end of my sw
On Sat, May 26, 2001 at 09:25:32PM +0200, Dag-Erling Smorgrav wrote:
> No dump (dumps seem to have been broken for about a month now), but a
> stacktrace from DDB:
Crashdumps have been working for me recently, (apart from the fact
that they overrun the end of my swap partition by 64k and clobber
No dump (dumps seem to have been broken for about a month now), but a
stacktrace from DDB:
kernel: type 12 trap, code=0
Stopped at worklist_remove+0x1c: cmpw$0,0xa(%ecx)
db> trace
worklist_remove(deadc0de) at worklist_remove+0x1c
free_diradd(deadc0de) at free_diradd+0x26
free_newdirblk
