View Incident:
http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=803625
Status : open Priority : 2
Assigned Engineer : ananth Submitter : ajag
*Modified User : lord *Modified User Domain : sgi.com
*Description :
The growfs QA test creates a 16Mb filesystem with one allocation group and
sucessively grows its size to 17, 33, 35 and 48 megabyte (3 ags) with four
calls to
xfs_growfs. The first growfs appears to succeed, however, subsequents calls fail
on a call to xfs_read_buf (line 336 xfs_fsops.c) while writing out the redundant
superblocks for the filesystem. The call sequence looks like:
xfs_growfs_data_private
xfs_read_buf (function)
xfs_buf_read (macro)
pagebuf_get (function call at line 747 page_buf.c)
.....
==========================
ADDITIONAL INFORMATION (ADD)
From: lord@xxxxxxx (BugWorks)
Date: Oct 03 2000 11:22:27AM
==========================
It looks like the pagebuf written out for the first superblock
update has not been written yet - it should get unlocked at the
end of the write to disk. If you turn on pagebuf tracing,
and call BUG() where the EBUSY error is happening the pbtrace
will tell you who did what with the buffer.
|