xfs
[Top] [All Lists]

[Bug 350] Starting XFS recovery never complete

To: xfs-master@xxxxxxxxxxx
Subject: [Bug 350] Starting XFS recovery never complete
From: bugzilla-daemon@xxxxxxxxxxx
Date: Tue, 21 Dec 2004 03:00:02 -0800
Sender: linux-xfs-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=350





------- Additional Comments From tom@xxxxxxxxxxxxxx  2004-21-12 03:00 PDT 
-------
I've just had similar problem on Debian Sarge running 2.6.7-1-686-smp and
xfsprogs 2.6.20. The partition was /var and had postgres and openldap running on
it. The partition was taken offline due to the error, reboot didn't fix it,
though the xfs_repair did, sorry don't have the output :-(

Here's the trace from dmesg after the reboot if its useful. i *think* the error
msg was the same before the reboot.


Filesystem "md1": XFS internal error xfs_alloc_read_agf at line 2195 of file
fs/xfs/xfs_alloc.c.  Caller 0xf89a07ad
 [<f89a0c4d>] xfs_alloc_read_agf+0x12d/0x1f0 [xfs]
 [<f89a07ad>] xfs_alloc_fix_freelist+0x3fd/0x490 [xfs]
 [<f89a07ad>] xfs_alloc_fix_freelist+0x3fd/0x490 [xfs]
 [<f89a07ad>] xfs_alloc_fix_freelist+0x3fd/0x490 [xfs]
 [<f89f8562>] xfs_trans_log_buf+0x72/0xb0 [xfs]
 [<f89a09ba>] xfs_alloc_log_agf+0x5a/0x60 [xfs]
 [<f899e591>] xfs_alloc_ag_vextent+0x61/0x140 [xfs]
 [<f89a0e41>] xfs_alloc_vextent+0x131/0x4b0 [xfs]
 [<f89b1938>] xfs_bmap_alloc+0xd08/0x1c70 [xfs]
 [<f89ade0d>] xfs_bmap_add_extent_delay_real+0x8cd/0x16b0 [xfs]
 [<f888639d>] ide_build_sglist+0x3d/0xb0 [ide_core]
 [<f8886cc5>] __ide_dma_begin+0x35/0x50 [ide_core]
 [<f8886c80>] __ide_dma_write+0xc0/0xd0 [ide_core]
 [<f88862b0>] ide_dma_intr+0x0/0xb0 [ide_core]
 [<f89ad404>] xfs_bmap_add_extent+0x3b4/0x4f0 [xfs]
 [<f89b5fd8>] xfs_bmapi+0x5c8/0x1640 [xfs]
 [<c0108679>] handle_IRQ_event+0x49/0x80
 [<f89bd87f>] xfs_bmbt_get_state+0x2f/0x40 [xfs]
 [<f89b42ec>] xfs_bmap_do_search_extents+0xbc/0x420 [xfs]
 [<f89e712e>] xfs_log_reserve+0xde/0xf0 [xfs]
 [<f89e44ba>] xfs_iomap_write_allocate+0x2ca/0x530 [xfs]
 [<c011ef60>] autoremove_wake_function+0x0/0x60
 [<f89e349f>] xfs_iomap+0x3ff/0x560 [xfs]
 [<f8a044f8>] xfs_map_blocks+0x58/0xc0 [xfs]
 [<f8a056cb>] xfs_page_state_convert+0x54b/0x6d0 [xfs]
 [<c01b4e83>] radix_tree_gang_lookup_tag+0x63/0x80
 [<c013e53e>] find_get_pages_tag+0x4e/0xb0
 [<f8a05f46>] linvfs_writepage+0x66/0x100 [xfs]
 [<c0185521>] mpage_writepages+0x211/0x350
 [<f8a05ee0>] linvfs_writepage+0x0/0x100 [xfs]
 [<f8a01c1a>] xfs_inode_flush+0x21a/0x280 [xfs]
 [<f8a072fa>] pagebuf_rele+0x3a/0x170 [xfs]
 [<f8a0d9be>] xfs_bdstrat_cb+0x3e/0x50 [xfs]
 [<f89f7c26>] xfs_trans_first_ail+0x16/0x30 [xfs]
 [<c0144132>] do_writepages+0x42/0x50
 [<c01835b9>] __sync_single_inode+0x79/0x230
 [<c01839ee>] sync_sb_inodes+0x18e/0x2f0
 [<c0183cad>] writeback_inodes+0x15d/0x190
 [<c0143ea7>] wb_kupdate+0xa7/0x120
 [<c0144ac8>] __pdflush+0xf8/0x230
 [<c0144c00>] pdflush+0x0/0x30
 [<c0144c26>] pdflush+0x26/0x30
 [<c0143e00>] wb_kupdate+0x0/0x120
 [<c0144c00>] pdflush+0x0/0x30
 [<c013616a>] kthread+0xba/0xc0
 [<c01360b0>] kthread+0x0/0xc0
 [<c01042c5>] kernel_thread_helper+0x5/0x10

xfs_force_shutdown(md1,0x8) called from line 1088 of file fs/xfs/xfs_trans.c. 
Return address = 0xf8a0ee4b
Filesystem "md1": Corruption of in-memory data detected.  Shutting down
filesystem: md1
Please umount the filesystem, and rectify the problem(s)
xfs_force_shutdown(md1,0x1) called from line 353 of file fs/xfs/xfs_rw.c. 
Return address = 0xf8a0ee4b
XFS mounting filesystem md1



------- 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 350] Starting XFS recovery never complete, bugzilla-daemon <=