View Incident:
http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=800480
*Status : closed Priority : 2
Assigned Engineer : lord Submitter : ananth
Opened Date : 08/29/00 *Closed Date : 09/13/00
*Fixed By : lord *Fixed By Domain : sgi.com
*Modified Date : 09/13/00 *Modified User : lord
*Modified User Domain : sgi.com *Fix Description :
==========================
ADDITIONAL INFORMATION (CLOSE)
From: lord@xxxxxxx (BugWorks)
Date: Sep 13 2000 12:19:12PM
==========================
Still not getting messages from ptools to bugworks...
Fixed by this mod:
A dummy log sequence number gets built to determine if the log needs
flushing to make room for a new transaction. This code was still
endian sensitive since it used hard coded locations within the 64 bit
LSN to store the cycle and block numbers. This meant that the comparison
being done was basically meaningless and would lead to when tail pushing
happened being somewhat variable.
Date: Wed Sep 13 11:49:22 PDT 2000
Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4.0-test5
The following file(s) were checked into:
bonnie.engr.sgi.com:/isms/slinx/2.4.0-test1-xfs
Modid: 2.4.0-test1-xfs:slinx:74322a
linux/fs/xfs/xfs_log.c - 1.221
- In calculating a threshold lsn for log flushing, do it in a byte order
independent way.
|