Re: XFS errors... can't repair them

2011-02-21 Thread Heinz Diehl
On 21.02.2011, Martín Marqués wrote: 

> Feb 21 09:47:08 dagobah kernel: XFS internal error
> XFS_WANT_CORRUPTED_RETURN at line 358 of file fs/xfs/xfs_alloc.c.
> Caller 0xa0fc126e
> Feb 21 09:47:08 dagobah kernel: Pid: 979, comm: flush-8:0 Tainted: P
> 2.6.34.7-66.fc13.x86_64 #1
> Feb 21 09:47:08 dagobah kernel: Call Trace:
> Feb 21 09:47:08 dagobah kernel: []
> xfs_error_report+0x41/0x43 [xfs]
> Feb 21 09:47:08 dagobah kernel: [] ?
> xfs_alloc_ag_vextent_near+0x370/0xa0f [xfs]
[]

Looks like the btree structure of free blocks got corrupted after free
space has been allocated (had a short look into xfs_alloc.c, but I'm by 
no means an XFS specialist and not familiar with the code either). 

This could indicate a defective partition/harddrive.

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


Re: XFS errors... can't repair them

2011-02-21 Thread Martín Marqués
This was the message that I found in my /var/log/messages at the time
the FS was filling up. This message repeats lots of times, changing
only the page number.

Feb 21 09:47:08 dagobah kernel: XFS internal error
XFS_WANT_CORRUPTED_RETURN at line 358 of file fs/xfs/xfs_alloc.c.
Caller 0xa0fc126e
Feb 21 09:47:08 dagobah kernel: Pid: 979, comm: flush-8:0 Tainted: P
2.6.34.7-66.fc13.x86_64 #1
Feb 21 09:47:08 dagobah kernel: Call Trace:
Feb 21 09:47:08 dagobah kernel: []
xfs_error_report+0x41/0x43 [xfs]
Feb 21 09:47:08 dagobah kernel: [] ?
xfs_alloc_ag_vextent_near+0x370/0xa0f [xfs]
Feb 21 09:47:08 dagobah kernel: []
xfs_alloc_fixup_trees+0x256/0x291 [xfs]
Feb 21 09:47:08 dagobah kernel: []
xfs_alloc_ag_vextent_near+0x370/0xa0f [xfs]
Feb 21 09:47:08 dagobah kernel: []
xfs_alloc_ag_vextent+0x31/0xfb [xfs]
Feb 21 09:47:08 dagobah kernel: []
xfs_alloc_vextent+0x31e/0x4aa [xfs]
Feb 21 09:47:08 dagobah kernel: []
xfs_bmap_btalloc+0x32b/0x4c8 [xfs]
Feb 21 09:47:08 dagobah kernel: []
xfs_bmap_alloc+0xe/0x10 [xfs]
Feb 21 09:47:08 dagobah kernel: [] xfs_bmapi+0x6dd/0xd79 [xfs]
Feb 21 09:47:08 dagobah kernel: [] ?
kmem_zone_alloc+0x69/0xb1 [xfs]
Feb 21 09:47:08 dagobah kernel: [] ?
xfs_iext_get_ext+0x45/0x69 [xfs]
Feb 21 09:47:08 dagobah kernel: []
xfs_iomap_write_allocate+0x20b/0x32b [xfs]
Feb 21 09:47:08 dagobah kernel: [] xfs_iomap+0x306/0x381 [xfs]
Feb 21 09:47:08 dagobah kernel: []
xfs_map_blocks+0x2d/0x31 [xfs]
Feb 21 09:47:08 dagobah kernel: []
xfs_page_state_convert+0x29c/0x531 [xfs]
Feb 21 09:47:08 dagobah kernel: [] ?
radix_tree_gang_lookup_tag_slot+0x84/0xa9
Feb 21 09:47:08 dagobah kernel: []
xfs_vm_writepage+0xdc/0x11c [xfs]
Feb 21 09:47:08 dagobah kernel: [] __writepage+0x17/0x30
Feb 21 09:47:08 dagobah kernel: []
write_cache_pages+0x20f/0x345
Feb 21 09:47:08 dagobah kernel: [] ? __writepage+0x0/0x30
Feb 21 09:47:08 dagobah kernel: []
generic_writepages+0x24/0x26
Feb 21 09:47:08 dagobah kernel: []
xfs_vm_writepages+0x4d/0x56 [xfs]
Feb 21 09:47:08 dagobah kernel: [] do_writepages+0x21/0x2a
Feb 21 09:47:08 dagobah kernel: []
writeback_single_inode+0xbe/0x1df
Feb 21 09:47:08 dagobah kernel: []
writeback_inodes_wb+0x2e3/0x3a0
Feb 21 09:47:08 dagobah kernel: [] wb_writeback+0x139/0x1bb
Feb 21 09:47:08 dagobah kernel: [] ? call_rcu_sched+0x15/0x17
Feb 21 09:47:08 dagobah kernel: [] ? call_rcu+0xe/0x10
Feb 21 09:47:08 dagobah kernel: [] wb_do_writeback+0x6e/0x15c
Feb 21 09:47:08 dagobah kernel: []
bdi_writeback_task+0x3f/0xc0
Feb 21 09:47:08 dagobah kernel: [] ? bdi_start_fn+0x0/0xd9
Feb 21 09:47:08 dagobah kernel: [] bdi_start_fn+0x71/0xd9
Feb 21 09:47:08 dagobah kernel: [] ? bdi_start_fn+0x0/0xd9
Feb 21 09:47:08 dagobah kernel: [] kthread+0x7f/0x87
Feb 21 09:47:08 dagobah kernel: []
kernel_thread_helper+0x4/0x10
Feb 21 09:47:08 dagobah kernel: [] ? kthread+0x0/0x87
Feb 21 09:47:08 dagobah kernel: [] ?
kernel_thread_helper+0x0/0x10
Feb 21 09:47:08 dagobah kernel: Filesystem "sda3": page discard on
page ea1da470, inode 0x18000164, offset 308723712.


El día 21 de febrero de 2011 10:36, Martín Marqués
 escribió:
> I have a system with /home in XFS format. Just today I tried to copy a
> big file not knowing that there was little space left in the device.
> The thing is that the system didn't let me access /home anymore (not
> even as root). I rebooted and tried to use xfs_check and xfs_repair,
> with no luck (it looks as if they do nothing).
>
> BTW, no reboot /home doesn't get mounted printing a lot of error messages.
>
> Any ideas?
>




-- 
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines