xfs
[Top] [All Lists]

[Bug 186] xfs_force_shutdown on a lvm device

To: xfs-master@xxxxxxxxxxx
Subject: [Bug 186] xfs_force_shutdown on a lvm device
From: bugzilla-daemon@xxxxxxxxxxx
Date: Sat, 26 Oct 2002 20:21:50 -0700
Sender: linux-xfs-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=186





------- Additional Comments From c.pascoe@xxxxxxxxxxxxxx  2002-10-26 20:21 
-------
Happy to turn on whatever you think will be useful.  I have done a debug build 
and set panic_mask to 127; no asserts tripped, but it did panic as promised.

xfs_force_shutdown(lvm(58,0),0x8) called from line 1055 of file xfs_trans.c.  
Return address = 0xf8a5603f (this line number doesn't match, I was trying 
changed code)
Filesystem "lvm(58,0)": xfs_itobp: xfs_trans_read_buf() returned error 5, 
imap.im_blkno 0x27a00, imap.im_len 0x10
XFS: Transforming an alert into a BUG.
Filesystem "lvm(58,0)": Corruption of in-memory data detected.  Shutting down 
filesystem: lvm(58,0)

The one time I ran this, it was a mkdir operation being cancelled.

In case it's of any use, I've disabled linvfs_fh_to_dentry/linvfs_dentry_to_fh 
operations (and reinstated xfs_read_inode) on my kernel and retested.  I don't 
get the shutdown now - but after a few hours of running I got a NULL pointer 
dereference in nfsd_findparent, on the line:
        pdentry = child->d_inode->i_op->lookup(child->d_inode, tdentry);

I've added checks to find out exactly which pointer was NULL, and am trying 
again..

Regards,
Chris



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


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