[Top] [All Lists]

Re: XFS on 2.4 Tib raid

To: dgc@xxxxxxx
Subject: Re: XFS on 2.4 Tib raid
From: lvismer@xxxxxxxxxxxxxxxx
Date: Tue, 10 May 2005 10:03:51 +0200
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <200505101008.47081.naude@picturenet.co.za>
References: <200505092210.25667.lvismer@picturenet.co.za> <200505100656.20204.lvismer@picturenet.co.za> <200505101008.47081.naude@picturenet.co.za>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) 3.2.4
Hi Dave

> > Hi
> >
> > I am using an ATTO scsi card speaking to an Infortrend 2.4 Tib raid
> > system.
> >
> > Some system config settings:
> > Distro: debian sarge
> > Kernel: 2.6.11 (kernel-image-2.6.11-1-686)
> > XFS:  xfsprogs (2.6.28-1)
> >
> > I created a filesystem using:
> > mkfs.xfs -L iftraid -f /dev/sdc
> >
> > After copying about 300Mb onto the newly mounted filesystem I get the
> What sort of data was being copied?
I am copying jpeg files 1-2mb in size.

> What's the actual error? This is the stack trace that's part of the
> error message, but does not inidcate what the error was. Can you
> include the error messages that were emitted before the stack trace?
I include the full error from /var/log/messages. As one copies files it stops at
some point and the following error loops and the machine needs to be rebooted.

0x0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Filesystem "sdc": XFS internal error xfs_alloc_read_agf at line 2195 of file fs/
xfs/xfs_alloc.c.  Caller 0xd0b638ca
 [<d0b63ced>] xfs_alloc_read_agf+0x12d/0x1f0 [xfs]
 [<d0b638ca>] xfs_alloc_fix_freelist+0x47a/0x490 [xfs]
 [<d0b638ca>] xfs_alloc_fix_freelist+0x47a/0x490 [xfs]
 [<d0b638ca>] xfs_alloc_fix_freelist+0x47a/0x490 [xfs]
 [<c0131ed0>] handle_IRQ_event+0x30/0x70
 [<c0114f33>] scheduler_tick+0x133/0x290
 [<c01078eb>] timer_interrupt+0x4b/0x100
 [<c0131ed0>] handle_IRQ_event+0x30/0x70
 [<d0b6407d>] xfs_alloc_vextent+0x2cd/0x500 [xfs]
 [<c011087f>] smp_apic_timer_interrupt+0x2f/0x80
 [<d0b743f8>] xfs_bmap_alloc+0xd08/0x1c60 [xfs]
 [<c0114e9e>] scheduler_tick+0x9e/0x290
 [<d0b8008f>] xfs_bmbt_get_state+0x2f/0x40 [xfs]
 [<d0b789f8>] xfs_bmapi+0x5b8/0x1780 [xfs]
 [<d0b8008f>] xfs_bmbt_get_state+0x2f/0x40 [xfs]
 [<d0b76d6c>] xfs_bmap_do_search_extents+0xfc/0x430 [xfs]
 [<c011007b>] acpi_copy_wakeup_routine+0x1b/0xa0
 [<d0bc4f55>] kmem_zone_zalloc+0x35/0x60 [xfs]
 [<d0ba8faf>] xfs_log_reserve+0xbf/0xd0 [xfs]
 [<d0ba628a>] xfs_iomap_write_allocate+0x2ba/0x580 [xfs]
 [<c011cbbb>] __do_softirq+0x7b/0x90
 [<c010527e>] do_IRQ+0x1e/0x30
 [<d0ba4f8f>] xfs_iomap+0x3ff/0x560 [xfs]
 [<d0bc5188>] xfs_map_blocks+0x58/0x90 [xfs]
 [<d0bc6194>] xfs_page_state_convert+0x4d4/0x610 [xfs]
 [<c0131ed0>] handle_IRQ_event+0x30/0x70
 [<c011cbbb>] __do_softirq+0x7b/0x90
 [<d0bc6997>] linvfs_writepage+0x67/0x100 [xfs]
 [<c013d694>] pageout+0xb4/0x100
 [<c0132a34>] __remove_from_page_cache+0x24/0x50
 [<c013d8c3>] shrink_list+0x1e3/0x3f0
 [<c013dc3c>] shrink_cache+0x16c/0x300
 [<c013b055>] drain_cpu_caches+0x45/0x50
 [<c013d3d8>] shrink_slab+0x88/0x190
 [<c013e32a>] shrink_zone+0xba/0xf0
 [<c013e838>] balance_pgdat+0x2b8/0x3b0
 [<c013ea19>] kswapd+0xe9/0x110
 [<c012b550>] autoremove_wake_function+0x0/0x60
 [<c012b550>] autoremove_wake_function+0x0/0x60
 [<c013e930>] kswapd+0x0/0x110
 [<c01012fd>] kernel_thread_helper+0x5/0x18

> BTW, were there I/O errors on the RAID device(s)?
No io errors on the raid device

Many thanks
Leon Vismer

This message was sent using IMP, the Internet Messaging Program.

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