xfs
[Top] [All Lists]

[Bug 193] New: when tested with fsstress in scsi, the process is locked.

To: xfs-master@xxxxxxxxxxx
Subject: [Bug 193] New: when tested with fsstress in scsi, the process is locked.
From: bugzilla-daemon@xxxxxxxxxxx
Date: Wed, 13 Nov 2002 18:03:35 -0800
Sender: linux-xfs-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=193

           Summary: when tested with fsstress in scsi, the process is
                    locked.
           Product: Linux XFS
           Version: Current
          Platform: IA32
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: High
         Component: XFS kernel code
        AssignedTo: xfs-master@xxxxxxxxxxx
        ReportedBy: wddi_1976@xxxxxxxxxxxx


What kernel are you using:
2.4.19-xfs
Where did the XFS code come from?  (CVS, Linus, your distribution, etc):
CVS kernel
Description of Problem:

Just now, I tried that test on the  cvs kernel again, it did not 
oops anymore,
but it is locked after a while, I studied all the process trace of 
the system, 
it seems that only one process is locked, the trace is here.
__down()
__down_failed()
 [xfs].text.lock.xfs_log
 xlog_state_get_iclog_space()
 xlog_write()
 xfs_log_write()
 xfs_trans_commit()
 xfs_attr_rolltrans£¨£©
 xfs_attr_mode_addname()
 xfs_attr_set()
 linvfs_setxattr()
 setxattr()
 sys_lsetxattr()
 system_call()
 (It seems that some process was wirting the log to disk. but no other 
process was writing to disk at this time)

How Reproducible:
 Run the shell command 
          /fsstress -d /mnt/tmp \
         -f allocsp=0 \
         -f freesp=0 \
         -f bulkstat=0 \
         -f bulkstat1=0 \
         -f resvsp=0 \
         -f unresvsp=0 \
         -f attr_set=100 -f attr_remove=100 \
         -S -p 1 -n 10000
 (A 200m xfs partition is mounted at /mnt/tmp, use scsi)
  fsstress is the program provided in xfstest package.

Actual Results:
 
the process was locked.

Additional Information:



------- 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>
  • [Bug 193] New: when tested with fsstress in scsi, the process is locked., bugzilla-daemon <=