[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: [Xen-users] kernel error messages with 2.6.16: XFS internal error xfs_ialloc_read_agi at line 1357 of file fs/xfs/xfs_ialloc.c
I use the XFS filesystem all the time. I'm running it on both dom0 and domU on several machines, and have had absolutely no problems. The error messages you included indicate a corrupt filesystem. I'd try standard stuff - dismount it, run fsck on it, and try again. Also, make absolutely sure that filesystem is only being used by ONE system, real or virtual. You can't mount an XFS partition read/write by multiple systems, or you'll have corruption problems like this. On Wed, 2006-03-22 at 09:25 +0100, Hans-Christian Armingeon wrote: > Hi, > > I have a domU running on xfs. > > It throws many error messages like these. > > Has anyone xfs in domU running? > What is the source of these problems? > > Thanks in advance, > > Johnny > > [ 2431.604455] 0x0: 01 00 00 00 ff ff 4f 00 00 00 00 00 3f 1f ca 6c > [ 2431.604462] Filesystem "sda1": XFS internal error xfs_ialloc_read_agi at > line 1357 of file fs/xfs/xfs_ialloc.c. Caller 0xffffffff80203c9b > [ 2431.604466] > [ 2431.604467] Call Trace: <ffffffff80201ff1>{xfs_corruption_error+228} > [ 2431.604477] <ffffffff80223645>{kmem_zone_zalloc+28} > <ffffffff801f1e1d>{xfs_buf_item_init+86} > [ 2431.604484] <ffffffff8021a35e>{xfs_trans_read_buf+648} > <ffffffff8020339e>{xfs_ialloc_read_agi+190} > [ 2431.604492] <ffffffff80203c9b>{xfs_dialloc+332} > <ffffffff801e5ea0>{xfs_bmap_search_extents+106} > [ 2431.604499] <ffffffff80203c9b>{xfs_dialloc+332} > <ffffffff802235dc>{kmem_zone_alloc+73} > [ 2431.604505] <ffffffff801f304e>{xfs_da_do_buf+1197} > <ffffffff802258d9>{xfs_buf_rele+48} > [ 2431.604512] <ffffffff801f25e8>{xfs_da_brelse+110} > <ffffffff801fa61c>{xfs_dir2_leaf_lookup_int+506} > [ 2431.604519] <ffffffff8020a4a4>{xfs_ialloc+74} > <ffffffff801f6857>{xfs_dir2_isleaf+25} > [ 2431.604526] <ffffffff8021aeb8>{xfs_dir_ialloc+142} > <ffffffff8035e318>{__down_write+18} > [ 2431.604534] <ffffffff802216e5>{xfs_mkdir+854} > <ffffffff80229bc8>{linvfs_mknod+474} > [ 2431.604542] <ffffffff80207990>{xfs_iunlock+87} > <ffffffff8021d9c1>{xfs_access+61} > [ 2431.604548] <ffffffff80229233>{linvfs_permission+18} > <ffffffff8017d963>{permission+124} > [ 2431.604555] <ffffffff8017e9fe>{__link_path_walk+358} > <ffffffff80189b6a>{mntput_no_expire+23} > [ 2431.604562] <ffffffff80189b6a>{mntput_no_expire+23} > <ffffffff80180ef0>{vfs_mkdir+215} > [ 2431.604569] <ffffffff80180fd2>{sys_mkdirat+160} > <ffffffff8017039b>{fd_install+37} > [ 2431.604576] <ffffffff8017096e>{do_sys_open+175} > <ffffffff8010a982>{system_call+134} > [ 2431.604582] <ffffffff8010a8fc>{system_call+0} > [ 2434.487301] ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) > Driver (PCI) > [ 2434.495818] USB Universal Host Controller Interface driver v2.3 > [ 2435.230553] 0x0: 01 00 00 00 ff ff 4f 00 00 00 00 00 3f 1f ca 6c > [ 2435.230560] Filesystem "sda1": XFS internal error xfs_ialloc_read_agi at > line 1357 of file fs/xfs/xfs_ialloc.c. Caller 0xffffffff80203c9b > [ 2435.230564] > [ 2435.230565] Call Trace: <ffffffff80201ff1>{xfs_corruption_error+228} > [ 2435.230576] <ffffffff80223645>{kmem_zone_zalloc+28} > <ffffffff801f1e1d>{xfs_buf_item_init+86} > [ 2435.230583] <ffffffff8021a35e>{xfs_trans_read_buf+648} > <ffffffff8020339e>{xfs_ialloc_read_agi+190} > [ 2435.230591] <ffffffff80203c9b>{xfs_dialloc+332} > <ffffffff80203c9b>{xfs_dialloc+332} > [ 2435.230597] <ffffffff80155374>{__alloc_pages+99} > <ffffffff80156ce3>{blockable_page_cache_readahead+83} > [ 2435.230606] <ffffffff8015090e>{file_read_actor+140} > <ffffffff80151d2f>{do_generic_mapping_read+979} > [ 2435.230612] <ffffffff80150882>{file_read_actor+0} > <ffffffff80155274>{get_page_from_freelist+810} > [ 2435.230618] <ffffffff80155274>{get_page_from_freelist+810} > <ffffffff8015517d>{get_page_from_freelist+563} > [ 2435.230625] <ffffffff80155274>{get_page_from_freelist+810} > <ffffffff8020a4a4>{xfs_ialloc+74} > [ 2435.230632] <ffffffff8021aeb8>{xfs_dir_ialloc+142} > <ffffffff8035e318>{__down_write+18} > [ 2435.230640] <ffffffff802216e5>{xfs_mkdir+854} > <ffffffff80229bc8>{linvfs_mknod+474} > [ 2435.230648] <ffffffff80207990>{xfs_iunlock+87} > <ffffffff8021d9c1>{xfs_access+61} > [ 2435.230654] <ffffffff80229233>{linvfs_permission+18} > <ffffffff8017d963>{permission+124} > [ 2435.230661] <ffffffff8017e9fe>{__link_path_walk+358} > <ffffffff80189b6a>{mntput_no_expire+23} > [ 2435.230668] <ffffffff80189b6a>{mntput_no_expire+23} > <ffffffff80180ef0>{vfs_mkdir+215} > [ 2435.230675] <ffffffff80180fd2>{sys_mkdirat+160} > <ffffffff8017039b>{fd_install+37} > [ 2435.230682] <ffffffff8017096e>{do_sys_open+175} > <ffffffff8010a982>{system_call+134} > [ 2435.230689] <ffffffff8010a8fc>{system_call+0} > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users > -- Patrick Wolfe (pwolfe@xxxxxxxxxxxxxx) Attachment:
signature.asc _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |