[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 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?
Yes, several times.
Now I newfs the file system again and restore files from tar
(without log or softdep), but now I get:
/usr: bad dir ino 2432640 at offset 7136: mangled entry
panic: bad dir
Stopped in pid 50.1 (tar) at netbsd:cpu_Debugger+0x6: mov r14, r15
cpu_Debugger() at netbsd:panic+0x104
panic() at netbsd:ufs_dirbad+0x46
ufs_dirbad() at netbsd:ufs_lookup+0x320
ufs_lookup() at netbsd:VOP_LOOKUP+0x20
VOP_LOOKUP() at netbsd:lookup+0x22a
lookup() at netbsd:namei+0xd0
namei() at netbsd:do_sys_stat+0x2a
do_sys_stat() at netbsd:sys___lstat30+0x18
sys___lstat30() 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 0x20548c20
Not sure if sh3 specific problem or MI ffs one.
Main Index |
Thread Index |