[mythtv-users] a read-only disk/directory in a storage group?
Brian J. Murrell
brian at interlinx.bc.ca
Wed Oct 6 12:06:17 UTC 2010
On Wed, 2010-10-06 at 07:51 -0400, Jim Morton wrote:
> Not discounting what you are saying but how do you know the corruption
> is due to XFS?
Uhm, because XFS is complaining about it:
Oct 4 06:29:53 pvr kernel: [317519.748140] XFS internal error XFS_WANT_CORRUPTED_RETURN at line 381 of file /build/buildd/linux-2.6.32/fs/xfs/xfs_alloc.c. Caller 0xf898c0d5
Oct 4 06:29:53 pvr kernel: [317519.910822] Pid: 1822, comm: flush-252:7 Tainted: P 2.6.32-23-generic #37-Ubuntu
Oct 4 06:29:53 pvr kernel: [317519.910826] Call Trace:
Oct 4 06:29:53 pvr kernel: [317519.910900] [<f89b35a3>] xfs_error_report+0x53/0x60 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.910917] [<f898c0d5>] ? xfs_alloc_ag_vextent_near+0x535/0x9f0 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.910931] [<f898a5b3>] xfs_alloc_fixup_trees+0x2a3/0x340 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.910945] [<f898c0d5>] ? xfs_alloc_ag_vextent_near+0x535/0x9f0 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.910960] [<f898d183>] ? xfs_allocbt_init_cursor+0x33/0x80 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.910974] [<f898c0d5>] xfs_alloc_ag_vextent_near+0x535/0x9f0 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.910988] [<f898c65f>] xfs_alloc_ag_vextent+0xcf/0x120 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911002] [<f898cddf>] xfs_alloc_vextent+0x1cf/0x480 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911017] [<f899d03a>] xfs_bmap_btalloc+0x1da/0xb70 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911035] [<f89b99d8>] ? xfs_iext_bno_to_ext+0x88/0x180 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911051] [<f899d9ef>] xfs_bmap_alloc+0x1f/0x40 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911065] [<f899e107>] xfs_bmapi+0x6f7/0x16a0 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911076] [<c012a498>] ? default_spin_lock_flags+0x8/0x10
Oct 4 06:29:53 pvr kernel: [317519.911095] [<f89c0000>] ? xfs_iomap+0x180/0x370 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911113] [<f89bf048>] xfs_iomap_write_allocate+0x218/0x420 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911131] [<f89c01a6>] xfs_iomap+0x326/0x370 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911152] [<f89d9728>] xfs_map_blocks+0x38/0x40 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911170] [<f89dab52>] xfs_page_state_convert+0x402/0x7d0 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911176] [<c01ca397>] ? find_get_pages_tag+0x37/0x110
Oct 4 06:29:53 pvr kernel: [317519.911194] [<f89db05d>] xfs_vm_writepage+0x6d/0x110 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911200] [<c01d1110>] __writepage+0x10/0x40
Oct 4 06:29:53 pvr kernel: [317519.911204] [<c01d2186>] write_cache_pages+0x186/0x360
Oct 4 06:29:53 pvr kernel: [317519.911208] [<c01d1100>] ? __writepage+0x0/0x40
Oct 4 06:29:53 pvr kernel: [317519.911226] [<f89daff0>] ? xfs_vm_writepage+0x0/0x110 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911230] [<c01d2384>] generic_writepages+0x24/0x30
Oct 4 06:29:53 pvr kernel: [317519.911248] [<f89d9e99>] xfs_vm_writepages+0x49/0x60 [xfs]
Oct 4 06:29:53 pvr kernel: [317519.911252] [<c01d23ac>] do_writepages+0x1c/0x40
Oct 4 06:29:53 pvr kernel: [317519.911259] [<c0226355>] writeback_single_inode+0xd5/0x380
Oct 4 06:29:53 pvr kernel: [317519.911263] [<c0226e59>] writeback_inodes_wb+0x389/0x530
Oct 4 06:29:53 pvr kernel: [317519.911267] [<c02270f7>] wb_writeback+0xf7/0x1a0
Oct 4 06:29:53 pvr kernel: [317519.911271] [<c02273be>] wb_do_writeback+0x15e/0x170
Oct 4 06:29:53 pvr kernel: [317519.911275] [<c022740b>] bdi_writeback_task+0x3b/0xb0
Oct 4 06:29:53 pvr kernel: [317519.911280] [<c01e1670>] ? bdi_start_fn+0x0/0xc0
Oct 4 06:29:53 pvr kernel: [317519.911283] [<c01e16cd>] bdi_start_fn+0x5d/0xc0
Oct 4 06:29:53 pvr kernel: [317519.911287] [<c01e1670>] ? bdi_start_fn+0x0/0xc0
Oct 4 06:29:53 pvr kernel: [317519.911291] [<c0167574>] kthread+0x74/0x80
Oct 4 06:29:53 pvr kernel: [317519.911295] [<c0167500>] ? kthread+0x0/0x80
Oct 4 06:29:53 pvr kernel: [317519.911300] [<c0104087>] kernel_thread_helper+0x7/0x10
And this has come back several times in several days despite my doing
xfs_repairs on it.
From my brief googling of it, it appears to be a known corruption bug
that was supposedly addressed in several previous releases of the kernel
but apparently, given that I am running 2.6.32, it is not properly fixed
yet.
Additionally, this has not been my first XFS corruption problem. I have
had a number over the years of using it and am now just done with it.
> I have 3 video storage disks that are XFS and had no problems with
> corruption. If there is something I should be watching out for, it'd be
> nice to know.
Good luck and may that run continue for you.
Cheers,
b.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20101006/80bd3b44/attachment.pgp>
More information about the mythtv-users
mailing list