xfs-masters
[Top] [All Lists]

[Bug 14714] New: intermittent xfs crash

To: xfs-masters@xxxxxxxxxxx
Subject: [Bug 14714] New: intermittent xfs crash
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 2 Dec 2009 00:32:53 GMT
Auto-submitted: auto-generated
http://bugzilla.kernel.org/show_bug.cgi?id=14714

           Summary: intermittent xfs crash
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.32-rc8
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: XFS
        AssignedTo: xfs-masters@xxxxxxxxxxx
        ReportedBy: kevmitch@xxxxxxxxx
        Regression: Yes


After upgrading from 2.6.32-rc7 to rc8 I have experienced a number of
unexpected crashes that appear to be related to my xfs filesystems. When these
occur, dmesg says:

    [33091.758929] xfs_force_shutdown(sda6,0x2) called from line 1043 of file  
 fs/xfs/xfs_log.c.  Return address = 0xffffffff8114c5d3
    [33091.758951] Filesystem "sda6": Log I/O Error Detected.  Shutting down
filesystem: sda6
    [33091.758956] Please umount the filesystem, and rectify the problem(s)
    ...
    [33171.850058] Filesystem "sda6": xfs_log_force: error 5 returned.
    [33191.540124] No probe response from AP 00:16:b6:26:41:29 after 500ms,
disconnecting.

Any further attempts to access files on the affected filesystem hang, however
anything else that has already been loaded into memory continues to work fine.
An ls -l shows the mountpoint as red with question marks in the metadata
fields. Attempts to unmount the filesystem fail saying that it is in use, while
an fuser on the mount point hangs like everything else.

This appears to occur approximately once daily with the typical usage patterns
for my laptop. There does not appear to be a particular action on my part that
triggers it. So unfortunately it will be difficult to consistently reproduce.
It can occur quite suddenly under only mild disk usage such as saving,
compiling a latex document followed by rereading the postscript file. I recall
that it also occurred once after a suspend to ram.

Let me know if there is any additional information I can provide.

Kevin

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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