http://oss.sgi.com/bugzilla/show_bug.cgi?id=417
Summary: Reading snapshot gives error in debug.c /
xfs_bmap_search_extents
Product: Linux XFS
Version: Current
Platform: PC
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P2
Component: XFS kernel code
AssignedTo: xfs-master@xxxxxxxxxxx
ReportedBy: schaffoe@xxxxxxxxxxxxxxxxxxxxxxxx
System is SuSE SLES 9 SP1 with kernel 2.6.11.12 (because SuSE-supplied kernel
hangs system). An EVMS (dm-snapshot) snapshot of the XFS-formatted /home volume
(LVM2 on an easyRaid X12; shared via NFS) is taken/reset once a night for backup
purposes. It works for a few days, but then I get the following console message:
ko-cluster kernel: Access to block zero: fs: <dm-34> inode: 762404546
start_block : 0 start_off : 0 blkcnt : 0 extent-state : 0
dm-34 is the snapshot volume. And the log file says:
Jun 30 23:00:17 ko-cluster kernel: Access to block zero: fs: <dm-34> inode:
762404546 start_block : 0 start_off : 0 blkcnt : 0 extent-state : 0
Jun 30 23:00:17 ko-cluster kernel: ------------[ cut here ]------------
Jun 30 23:00:17 ko-cluster kernel: kernel BUG at fs/xfs/support/debug.c:106!
Jun 30 23:00:17 ko-cluster kernel: invalid operand: 0000 [#1]
Jun 30 23:00:17 ko-cluster kernel: SMP
Jun 30 23:00:17 ko-cluster kernel: Modules linked in: nls_cp850 nls_utf8 smbfs
bond0 nfsd w83627hf eeprom w83781d adm1021 i2c_sensor ipt_MASQUERADE tg3 ipt
_TCPMSS ipt_TOS e100 mii e1000 i2c_i801 hw_random i2c_core uhci_hcd evdev
ipt_state ipt_LOG usbcore ipt_REJECT iptable_mangle iptable_filter ip_nat_ftp
ipt
able_nat ip_conntrack_ftp ip_conntrack ip_tables ide_cd cdrom capability
commoncap xfs exportfs ext3 jbd dm_snapshot dm_mod aic7xxx sd_mod scsi_mod
Jun 30 23:00:17 ko-cluster kernel: CPU: 2
Jun 30 23:00:17 ko-cluster kernel: EIP: 0060:[<f8f6c3f5>] Not tainted VLI
Jun 30 23:00:17 ko-cluster kernel: EFLAGS: 00010246 (2.6.11.12MSTEST)
Jun 30 23:00:17 ko-cluster kernel: EIP is at cmn_err+0xa5/0xd0 [xfs]
Jun 30 23:00:17 ko-cluster kernel: eax: f8f83c84 ebx: f8f6f1e8 ecx: cc047898
edx: 00000293
Jun 30 23:00:17 ko-cluster kernel: esi: 00000000 edi: f8f88140 ebp: 00000000
esp: cc047894
Jun 30 23:00:17 ko-cluster kernel: ds: 007b es: 007b ss: 0068
Jun 30 23:00:18 ko-cluster kernel: Process bpbkar (pid: 31168,
threadinfo=cc046000 task=f54de540)
Jun 30 23:00:18 ko-cluster kernel: Stack: f8f6efdc f8f6efa3 f8f88140 00000293
00000000 00000000 cc047a04 d86eee90
Jun 30 23:00:18 ko-cluster kernel: f8f16f08 00000000 f8f6f1e8 f35d5780
2d715ec2 00000000 00000000 00000000
Jun 30 23:00:18 ko-cluster kernel: 00000000 00000000 00000000 00000000
00000000 00000000 d86eeee0 d86eee90
Jun 30 23:00:18 ko-cluster kernel: Call Trace:
Jun 30 23:00:18 ko-cluster kernel: [<f8f16f08>]
xfs_bmap_search_extents+0xf8/0x120 [xfs]
Jun 30 23:00:18 ko-cluster kernel: [<f8f18382>] xfs_bmapi+0x2b2/0x1750 [xfs]
Jun 30 23:00:18 ko-cluster kernel: [<f886c9e8>] dm_request+0x68/0xa0 [dm_mod]
Jun 30 23:00:18 ko-cluster kernel: [<c0133350>]
autoremove_wake_function+0x0/0x50
Jun 30 23:00:18 ko-cluster kernel: [<c024aed7>] generic_make_request+0xb7/0x220
Jun 30 23:00:18 ko-cluster kernel: [<c0291913>] nf_iterate+0x63/0xb0
Jun 30 23:00:18 ko-cluster kernel: [<c0133350>]
autoremove_wake_function+0x0/0x50
Jun 30 23:00:18 ko-cluster kernel: [<c0133301>] finish_wait+0x21/0x70
Jun 30 23:00:18 ko-cluster kernel: [<f886c954>] __split_bio+0xf4/0x120 [dm_mod]
Jun 30 23:00:18 ko-cluster kernel: [<f8f4212e>] xfs_imap_to_bmap+0x2e/0x2b0
[xfs]
Jun 30 23:00:18 ko-cluster kernel: [<f8f42535>] xfs_iomap+0x185/0x4b0 [xfs]
Jun 30 23:00:18 ko-cluster kernel: [<f8f62ae3>] __linvfs_get_block+0x83/0x320
[xfs]
Jun 30 23:00:18 ko-cluster kernel: [<f8f62daf>] linvfs_get_block+0x2f/0x40
[xfs]
Jun 30 23:00:18 ko-cluster kernel: [<c018228c>] do_mpage_readpage+0x18c/0x490
Jun 30 23:00:18 ko-cluster kernel: [<c0111bd5>] smp_send_reschedule+0x55/0x70
Jun 30 23:00:18 ko-cluster kernel: [<c013e26a>] add_to_page_cache+0xba/0xe0
Jun 30 23:00:18 ko-cluster kernel: [<c01825e6>] mpage_readpages+0x56/0x120
Jun 30 23:00:18 ko-cluster kernel: [<f8f62d80>] linvfs_get_block+0x0/0x40 [xfs]
Jun 30 23:00:18 ko-cluster kernel: [<c014270a>] rmqueue_bulk+0x7a/0x90
Jun 30 23:00:18 ko-cluster kernel: [<c0145210>] read_pages+0xf0/0x100
Jun 30 23:00:18 ko-cluster kernel: [<f8f62d80>] linvfs_get_block+0x0/0x40 [xfs]
Jun 30 23:00:18 ko-cluster kernel: [<c0142db5>] __alloc_pages+0xc5/0x3b0
Jun 30 23:00:18 ko-cluster kernel: [<c01452fe>]
__do_page_cache_readahead+0xde/0x150
Jun 30 23:00:18 ko-cluster kernel: [<c0145500>]
blockable_page_cache_readahead+0x40/0x60
Jun 30 23:00:18 ko-cluster kernel: [<c01456a0>]
page_cache_readahead+0x180/0x2a0
Jun 30 23:00:18 ko-cluster kernel: [<c013ebe5>]
do_generic_mapping_read+0x355/0x510
Jun 30 23:00:18 ko-cluster kernel: [<c013eda0>] file_read_actor+0x0/0xf0
Jun 30 23:00:18 ko-cluster kernel: [<c013f082>]
__generic_file_aio_read+0x1f2/0x230
Jun 30 23:00:18 ko-cluster kernel: [<c013eda0>] file_read_actor+0x0/0xf0
Jun 30 23:00:18 ko-cluster kernel: [<f8f68ff1>] xfs_read+0x141/0x300 [xfs]
Jun 30 23:00:18 ko-cluster kernel: [<c0123b02>] __do_softirq+0x62/0xe0
Jun 30 23:00:18 ko-cluster kernel: [<f8f656c5>] linvfs_aio_read+0x85/0xb0 [xfs]
Jun 30 23:00:18 ko-cluster kernel: [<c015e4c2>] do_sync_read+0xb2/0x100
Jun 30 23:00:18 ko-cluster kernel: [<c016d0fb>] __user_walk+0x1b/0x70
Jun 30 23:00:18 ko-cluster kernel: [<c0133350>]
autoremove_wake_function+0x0/0x50
Jun 30 23:00:18 ko-cluster kernel: [<c015d1f0>] sys_access+0xf0/0x170
Jun 30 23:00:18 ko-cluster kernel: [<c015e5e3>] vfs_read+0xd3/0x130
Jun 30 23:00:18 ko-cluster kernel: [<c015e8b1>] sys_read+0x41/0x70
Jun 30 23:00:18 ko-cluster kernel: [<c0103cd3>] syscall_call+0x7/0xb
Jun 30 23:00:18 ko-cluster kernel: Code: b8 40 81 f8 f8 89 44 24 08 8b 04 ad a0
3c f8 f8 89 44 24 04 e8 8d 29 1b c7 8b 54 24 0c b8 84 3c f8 f8 e8 ff 6b 38
c7 85 ed 75 08 <0f> 0b 6a 00 c3 ef f6 f8 8b 5c 24 10 8b 74 24 14 8b 7c 24 18 8b
Since the first appearance of the log entry, we have this message in the logs
everytime a backup is run. The backup administrator says that the backup works
for about 1 hour or exactly 10.182.656 bytes, but it should be more.
I already checked the machine's RAM with memtest86+ without finding errors.
--
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|