xfs
[Top] [All Lists]

Re: assertion failure in xfs_vnode.c:890

To: "Macy, Kip" <Kip_Macy@xxxxxxxxxx>
Subject: Re: assertion failure in xfs_vnode.c:890
From: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Tue, 25 Apr 2000 01:31:46 -0500
Cc: "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx>
References: <09D1E9BD9C30D311919200A0C9DD5C2C016226F3@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
"Macy, Kip" wrote:

>
>
> The following just occurred when trying to mount an XFS partition over
> NFS (on the local
> machine). This is the most recent source.
>
> XFS assertion failed:vp->v_count > 0, file: xfs_vnode.c:890

Yup this is know problem.
The problem occurs when ever the linux inode reference count gets
bumped,
iget does not  communicate down to the xfs vnode if the count it already
1 or greater
that the count has been incremented
iput  on the other hand will always communicate down  to decrement the
count thus giving us a v_count of 0 when it should be at least one.

We are currently talking about how to fix this problem; which involves
trying to merge the linux inode and the xfs vnode... which should prove
to be a lot of work. :-(

> ...
> kernel BUG at xfs_debug.c:86!
> due to panic@0xc01e2ef9
>
> kdb> bt
>
> assfail
> vn_rele
> linvfs_put_inode
> iput
> nfsd_iget
> find_fh_dentry
> fh_verify
> nfsd_statfs
> nfsd_proc_statfs
> nfsd_dispatch
> svc_process
> nfsd
> kernel_thread

--
Russell Cattelan
cattelan@xxxxxxxxxxx




<Prev in Thread] Current Thread [Next in Thread>