xfs-masters
[Top] [All Lists]

[Bug 81811] New: Internal error XFS_WANT_CORRUPTED_GOTO at line 1503

To: xfs-masters@xxxxxxxxxxx
Subject: [Bug 81811] New: Internal error XFS_WANT_CORRUPTED_GOTO at line 1503
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 07 Aug 2014 08:34:57 +0000
Auto-submitted: auto-generated
Delivered-to: xfs-masters@xxxxxxxxxxx
https://bugzilla.kernel.org/show_bug.cgi?id=81811

            Bug ID: 81811
           Summary: Internal error XFS_WANT_CORRUPTED_GOTO at line 1503
           Product: File System
           Version: 2.5
    Kernel Version: 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: XFS
          Assignee: xfs-masters@xxxxxxxxxxx
          Reporter: crosenbg@xxxxxxxxx
        Regression: No

Hi folks,

yesterday I deleted a great amount of data (didn't count files, so no numbers
here). After 2 hours of slow deleting, the filesystem hung. In dmesq I found
the following:

###################

XFS: Internal error XFS_WANT_CORRUPTED_GOTO at line 1503 of file
/build/linux-eKuxrT/linux-3.2.60/fs/xfs/xfs_alloc.c.  Caller 0xffffffffa025e106

Pid: 7342, comm: rm Not tainted 3.2.0-4-amd64 #1 Debian 3.2.60-1+deb7u3
Call Trace:
 [<ffffffffa025bd72>] ? xfs_free_ag_extent+0xec/0x66d [xfs]
 [<ffffffffa025e106>] ? xfs_free_extent+0xb7/0xf3 [xfs]
 [<ffffffffa025ad21>] ? kmem_zone_alloc+0x27/0x71 [xfs]
 [<ffffffffa0269c77>] ? xfs_bmap_finish+0xf3/0x162 [xfs]
 [<ffffffffa027e9e5>] ? xfs_itruncate_extents+0xe4/0x1ce [xfs]
 [<ffffffffa027eb4f>] ? xfs_itruncate_data+0x80/0xea [xfs]
 [<ffffffffa0259102>] ? xfs_inactive+0x1a0/0x3ae [xfs]
 [<ffffffff8110d6a5>] ? end_writeback+0x6a/0x77
 [<ffffffffa0255102>] ? xfs_fs_evict_inode+0xad/0xb9 [xfs]
 [<ffffffff8110d748>] ? evict+0x96/0x148
 [<ffffffff81105ea1>] ? do_unlinkat+0x107/0x156
 [<ffffffff81355452>] ? system_call_fastpath+0x16/0x1b
XFS (dm-0): xfs_do_force_shutdown(0x8) called from line 3729 of file
/build/linux-eKuxrT/linux-3.2.60/fs/xfs/xfs_bmap.c.  Return address =
0xffffffffa0269cac
XFS (dm-0): Corruption of in-memory data detected.  Shutting down filesystem
XFS (dm-0): Please umount the filesystem and rectify the problem(s)
XFS (dm-0): xfs_log_force: error 5 returned.

[... goes on and on]

XFS (dm-0): xfs_log_force: error 5 returned.
XFS (dm-0): xfs_do_force_shutdown(0x1) called from line 1033 of file
/build/linux-eKuxrT/linux-3.2.60/fs/xfs/xfs_buf.c.  Return address =
0xffffffffa024a8a4
XFS (dm-0): xfs_log_force: error 5 returned.
XFS (dm-0): xfs_log_force: error 5 returned.

#############

I couldn't mount the filesystem again. After using "xfs_repair" and removed
errors, I could luckily mount again.
This is a backup system so... I kind of have some doupts about the stability
right now.

This is the fstab entry:
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
UUID=blabla      /backup1        xfs     rw              0       0


I you need further information please dont't hesitate to ask!


Best regards
Carsten

-- 
You are receiving this mail because:
You are the assignee for the bug.

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