View Incident:
http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=799692
Status : open Priority : 2
Assigned Engineer : nb Submitter : ananth
*Modified User : ananth *Modified User Domain : engr
*Description :
I don't know how exactly to descibe this problem,
but dbench starts reporting errors under some circumstances.
AFAIK, this is related to the xfs-cmds version used
to mkfs/mount/repair (etc.) the file system.
Using the same kernel, dbench would run fine when
1.0.2 version of the xfs-cmds is used, but reports
errors when 1.0.4 version (as of today) of xfs-cmds is used.
ananth.
.....
==========================
ADDITIONAL INFORMATION (ADD)
From: ananth@engr (BugWorks)
Date: Aug 22 2000 05:23:03PM
==========================
Here's Nathan's suggestion:
--------
when you do a fresh mkfs, then run xfs_logprint, does it just
say:
# /usr/sbin/xfs_logprint /dev/hda7
xfs_logprint:
data device: 0x307
log device: 0x307 daddr: 1020128 length: 9600
xfs_logprint: skipped 9600 zeroed blocks
xfs_logprint: totally zeroed log
xfs_logprint: physical end of log
============================================================================
xfs_logprint: logical end of log
============================================================================
#
(thats what it should say, anyway).
--------------
Chait, can you try this on your system?
ananth.
|