tech-kern archive

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

Re: panic due to lost vnode flag



On Fri, Oct 30, 2009 at 04:38:10PM +0100, Matthias Drochner wrote:
> 
> bouyer%antioche.eu.org@localhost said:
> > hopefully 0xcc55ce8c is a pointer to a struct inode, could you try to
> > print it as a struct inode and see what the inode number refers to in
> > the filesystem ?
> 
> liiks like an inode indeed:
> 
> (gdb) print *(struct inode *)(vp->v_data)
> $2 = {i_gnode = {g_op = 0xc062b6d4, g_glock = {rw_owner = 0}, g_dirtygen = 0},
>   i_hash = {le_next = 0x0, le_prev = 0xe7e2ce88}, i_nextsnap = {
>     tqe_next = 0x0, tqe_prev = 0x0}, i_vnode = 0xcc55be64, i_ump = 0xc1c36100,

does i_vnode match vp ?

>   i_devvp = 0xcc2498ac, i_flag = 17, i_dev = 6, i_number = 9429739, inode_u = 
> {
>     fs = 0xc1c40000, lfs = 0xc1c40000, e2fs = 0xc1c40000}, i_unused1 = 0x0,
>   i_dquot = {0x0, 0x0}, i_modrev = 74821745692, i_lockf = 0x0, i_count = 0,
>   i_endoff = 0, i_diroff = 0, i_offset = 0, i_reclen = 0, i_unused = 0,
>   inode_ext = {ffs = {ffs_snapblklist = 0x0, ffs_first_data_blk = 0,
>       ffs_first_indir_blk = 0}, e2fs = {ext2fs_last_lblk = 0,
>       ext2fs_last_blk = 0}, lfs = 0x0}, i_mode = 33133, i_nlink = 1,
>   i_size = 27676, i_flags = 0, i_gen = 1271818416, i_uid = 0, i_gid = 0,
>   i_dirhash = 0x0, i_din = {ffs1_din = 0xcc556e38, ffs2_din = 0xcc556e38,
>     e2fs_din = 0xcc556e38}}
> 
> [i_dev=6 means wd0g, this is ffs with WAPBL]
> 
> $ find /usr -inum 9429739 -print
> /usr/bin/sed
> $ ls -li /usr/bin/sed
> 9429739 -r-xr-xr-x  1 root  wheel  27676 Oct 29 00:30 /usr/bin/sed

This file was not being updated when the panic happened, is it ?

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--


Home | Main Index | Thread Index | Old Index