Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ffs:valloc: dup alloc (in 5.0RC3)



On Mon, Mar 23, 2009 at 09:53:05PM +0900, Izumi Tsutsui wrote:

> I get the similar panic on RC3 landisk on extracting pkgsrc:
> 
> ---
> pkgsrc/audio/gmpc/CVS/Repository
> pkgsrc/audio/gmpc/CVS/Entries
> pkgsrdmode 1 mode 1 dgen 0 gen 0
> size 0 blocks 0
> ino 2043508 ipref 2043501
> panic: ffs_valloc: dup alloc
> Stopped in pid 659.1 (tar) at   netbsd:cpu_Debugger+0x6:        mov     r14, 
> r15
> 
> db> tr
> cpu_Debugger() at netbsd:panic+0x104
> panic() at netbsd:ffs_valloc+0x6d6
> ffs_valloc() at netbsd:ufs_makeinode+0x4c
> ufs_makeinode() at netbsd:ufs_create+0x36
> ufs_create() at netbsd:VOP_CREATE+0x22
> VOP_CREATE() at netbsd:vn_open+0x18c
> vn_open() at netbsd:sys_open+0x9e
> sys_open() at netbsd:sy_call+0x1c
> sy_call() at netbsd:syscall_plain+0xa4
> syscall_plain() at netbsd:general_exception+0x12a
> general_exception() at 0x8c0001a6
> <EXPEVT 160; SSR=00000000> at 0x204b84e8
> db> 
> 
> ---
> 
> I wonder if this could happen on damaged disk..
> (the disk got the same panic several times on 5.0_BETA days)

Your file system could have been damaged by an older kernel. Is that what
you mean? Have you run fsck after a clean unmount?


Home | Main Index | Thread Index | Old Index