Folks,

I am getting the following panic on NetBSD-4.0_BETA2:

panic: lfs_updatemeta: fragment is not last block

db> bt
cpu_Debugger() at netbsd:cpu_Debugger+0x5
panic() at netbsd:panic+0x1fc
lfs_updatemeta() at netbsd:lfs_updatemeta+0x1ab
lfs_gather() at netbsd:lfs_gather+0xa2
lfs_putpages() at netbsd:lfs_putpages+0x57b
VOP_PUTPAGES() at netbsd:VOP_PUTPAGES+0x2d
uvm_map_clean() at netbsd:uvm_map_clean+0x240
sys___msync13() at netbsd:sys___msync13+0xb0
syscall_plain() at netbsd:syscall_plain+0x112

dmesg:
cpu0: AMD Opteron(tm) Processor 244, 1791.77 MHz
wd0 at atabus0 drive 0: <Maxtor 6L160M0>
wd0: drive supports 16-sector PIO transfers, LBA48
addressing
wd0: 152 GB, 317632 cyl, 16 head, 63 sec, 512
bytes/sect x 320173056 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA
mode 6 (Ultra/133)
wd0(satalink0:0:0): using PIO mode 4, Ultra-DMA mode 6
(Ultra/133) (using DMA)

The panic is at:

void    
lfs_updatemeta(struct segment *sp)
{
<snip>
                /*
                 * If we write a frag in the wrong
place, the cleaner won't
                 * be able to correctly identify its
size later, and the
                 * segment will be uncleanable.  (Even
worse, it will assume
                 * that the indirect block that
actually ends the list
                 * is of a smaller size!)
                 */
                if ((sbp->b_bcount & fs->lfs_bmask) &&
i != 0)
                        panic("lfs_updatemeta:
fragment is not last block");


thanks,
Anil


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com