* XFS repair utils @ 2010-11-29 14:00 naveen yadav 2010-11-29 14:55 ` Christoph Hellwig 0 siblings, 1 reply; 5+ messages in thread From: naveen yadav @ 2010-11-29 14:00 UTC (permalink / raw) To: xfs Hi All, I am using XFS 2.6.34 kernel on my target, and I have #xfs_repair -V xfs_repair version 3.0.5 So is there any issue of compatibility with latest XFS_repair utils. or it will work fine with my latest kernel(2.6.34). Since some time mount fails. Thanks _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: XFS repair utils 2010-11-29 14:00 XFS repair utils naveen yadav @ 2010-11-29 14:55 ` Christoph Hellwig 2010-11-29 15:55 ` naveen yadav 0 siblings, 1 reply; 5+ messages in thread From: Christoph Hellwig @ 2010-11-29 14:55 UTC (permalink / raw) To: naveen yadav; +Cc: xfs On Mon, Nov 29, 2010 at 07:30:50PM +0530, naveen yadav wrote: > Hi All, > > I am using XFS 2.6.34 kernel on my target, and I have > #xfs_repair -V > xfs_repair version 3.0.5 > > So is there any issue of compatibility with latest XFS_repair utils. > or it will work fine with my latest kernel(2.6.34). It works just fine, but the 3.1.x series of xfsprogs brings large repair memory savings. > Since some time mount fails. What mount messages, what platform? _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: XFS repair utils 2010-11-29 14:55 ` Christoph Hellwig @ 2010-11-29 15:55 ` naveen yadav 2010-11-30 4:13 ` naveen yadav 0 siblings, 1 reply; 5+ messages in thread From: naveen yadav @ 2010-11-29 15:55 UTC (permalink / raw) To: Christoph Hellwig; +Cc: xfs Thanks for your response. I am using ARM as my target, and I got some time issue in radix tree.. with error Kernel BUG. radix_tree_tag_set+0x74/0xe43 [<801dfa80>] radix_tree_tag_set+0x74/0xe4 from[<801b6be0>] __xfs_inode_set_reclaim_tag+0x4c/0x7358:49:736 0358:49:736 [<801b6be0>] __xfs_inode_set_reclaim_tag+0x4c/0x70 from[<801b6c58>] xfs_inode_set_reclaim_tag+0358:49:752 x54/0xb8358:49:752 [<801b6c58>] xfs_inode_set_reclaim_tag+0x54/0xb8 from[<80182948>] xfs_iget+0x7d8/0x8b0358:49:752 [<80182948>] xfs_iget+0x7d8/0x8b0 from[<801a0eb0>] xfs_trans_iget+0x48/0x88358:49:767 [<801a0eb0>] xfs_trans_iget+0x48/0x88 from[<80186e88>] xfs_ialloc+0xd4/0x5b8358:49:767 [<80186e88>] xfs_ialloc+0xd4/0x5b8 from[<801a2014>] xfs_dir_ialloc+0x98/0x2a4358:49:783 [<801a2014>] xfs_dir_ialloc+0x98/0x2a4 from[<801a48b4>] xfs_create+0x2e0/0x6b8358:49:783 [<801a48b4>] xfs_create+0x2e0/0x6b8 from[<801b2fc0>] xfs_vn_mknod+0xc0/0x130358:49:783 [<801b2fc0>] xfs_vn_mknod+0xc0/0x130 from[<800c22cc>] vfs_create+0x80/0xe4358:49:799 [<800c22cc>] vfs_create+0x80/0xe4 from[<800c5328>] do_filp_open+0x284/0x8c8358:49:799 [<800c5328>] do_filp_open+0x284/0x8c8 from[<800b5858>] do_sys_open+0x6c/0x114358:49:814 [<800b5858>] do_sys_open+0x6c/0x114 from[<800102c4>] stack_done+0x20/0x3c358:49:814 On Mon, Nov 29, 2010 at 8:25 PM, Christoph Hellwig <hch@infradead.org> wrote: > On Mon, Nov 29, 2010 at 07:30:50PM +0530, naveen yadav wrote: >> Hi All, >> >> I am using XFS 2.6.34 kernel on my target, and I have >> #xfs_repair -V >> xfs_repair version 3.0.5 >> >> So is there any issue of compatibility with latest XFS_repair utils. >> or it will work fine with my latest kernel(2.6.34). > > It works just fine, but the 3.1.x series of xfsprogs brings large > repair memory savings. > >> Since some time mount fails. > > What mount messages, what platform? > > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: XFS repair utils 2010-11-29 15:55 ` naveen yadav @ 2010-11-30 4:13 ` naveen yadav 0 siblings, 0 replies; 5+ messages in thread From: naveen yadav @ 2010-11-30 4:13 UTC (permalink / raw) To: Christoph Hellwig; +Cc: xfs Hi Christoph, I got below issue on mount also: XFS mounting filesystem sda2 hub 2-0:1.0: port 1 disabled by hub (EMI?), re-enabling... usb 2-1: USB disconnect, address 5 sd 1:0:0:0: [sda] Unhandled error code sd 1:0:0:0: [sda] Result: hostbyte=0x07 driverbyte=0x00 end_request: I/O error, dev sda, sector 11741368 end_request: I/O error, dev sda, sector 11741608 end_request: I/O error, dev sda, sector 11741848 end_request: I/O error, dev sda, sector 11742088 end_request: I/O error, dev sda, sector 11742328 end_request: I/O error, dev sda, sector 11742568 end_request: I/O error, dev sda, sector 11742808 end_request: I/O error, dev sda, sector 11743048 end_request: I/O error, dev sda, sector 11743288 end_request: I/O error, dev sda, sector 11743528 end_request: I/O error, dev sda, sector 11743768 end_request: I/O error, dev sda, sector 11744008 end_request: I/O error, dev sda, sector 11744248 end_request: I/O error, dev sda, sector 11744488 end_request: I/O error, dev sda, sector 11744728 end_request: I/O error, dev sda, sector 11744968 end_request: I/O error, dev sda, sector 11745208 end_request: I/O error, dev sda, sector 11745448 xfs_force_shutdown(sda2,0x1) called from line 1004 of file fs/xfs/linux-2.6/xfs_ buf.c. Return address = 0x801acff8 Filesystem "sda2": I/O Error Detected. Shutting down filesystem: sda2 Please umount the filesystem, and rectify the problem(s) I/O error in filesystem ("sda2") meta-data dev sda2 block 0x3b84b8 ("xlog_ bwrite") error 5 buf count 2097152 XFS: failed to locate log tail XFS: log mount/recovery failed: error 5 XFS: log mount failed root hub reinitial ====> hub_port_init 1 Plug in USB Port1 usb 2-1: new high speed USB device using Mstar-ehci-1 and address 6 First get dev desc failed usb 2-1: device descriptor read/8, error -145 ====> hub_port_init 1 Plug in USB Port1 usb 2-1: new high speed USB device using Mstar-ehci-1 and address 7 First get dev desc failed usb 2-1: device descriptor read/8, error -145 ====> hub_port_init 1 Plug in USB Port1 usb 2-1: new high speed USB device using Mstar-ehci-1 and address 8 On Mon, Nov 29, 2010 at 9:25 PM, naveen yadav <yad.naveen@gmail.com> wrote: > Thanks for your response. > > I am using ARM as my target, and I got some time issue in radix tree.. > with error Kernel BUG. > > radix_tree_tag_set+0x74/0xe43 > > > [<801dfa80>] radix_tree_tag_set+0x74/0xe4 from[<801b6be0>] > __xfs_inode_set_reclaim_tag+0x4c/0x7358:49:736 > 0358:49:736 > [<801b6be0>] __xfs_inode_set_reclaim_tag+0x4c/0x70 from[<801b6c58>] > xfs_inode_set_reclaim_tag+0358:49:752 > x54/0xb8358:49:752 > [<801b6c58>] xfs_inode_set_reclaim_tag+0x54/0xb8 from[<80182948>] > xfs_iget+0x7d8/0x8b0358:49:752 > [<80182948>] xfs_iget+0x7d8/0x8b0 from[<801a0eb0>] > xfs_trans_iget+0x48/0x88358:49:767 > [<801a0eb0>] xfs_trans_iget+0x48/0x88 from[<80186e88>] > xfs_ialloc+0xd4/0x5b8358:49:767 > [<80186e88>] xfs_ialloc+0xd4/0x5b8 from[<801a2014>] > xfs_dir_ialloc+0x98/0x2a4358:49:783 > [<801a2014>] xfs_dir_ialloc+0x98/0x2a4 from[<801a48b4>] > xfs_create+0x2e0/0x6b8358:49:783 > [<801a48b4>] xfs_create+0x2e0/0x6b8 from[<801b2fc0>] > xfs_vn_mknod+0xc0/0x130358:49:783 > [<801b2fc0>] xfs_vn_mknod+0xc0/0x130 from[<800c22cc>] > vfs_create+0x80/0xe4358:49:799 > [<800c22cc>] vfs_create+0x80/0xe4 from[<800c5328>] > do_filp_open+0x284/0x8c8358:49:799 > [<800c5328>] do_filp_open+0x284/0x8c8 from[<800b5858>] > do_sys_open+0x6c/0x114358:49:814 > [<800b5858>] do_sys_open+0x6c/0x114 from[<800102c4>] > stack_done+0x20/0x3c358:49:814 > > > > > > > > > > On Mon, Nov 29, 2010 at 8:25 PM, Christoph Hellwig <hch@infradead.org> wrote: >> On Mon, Nov 29, 2010 at 07:30:50PM +0530, naveen yadav wrote: >>> Hi All, >>> >>> I am using XFS 2.6.34 kernel on my target, and I have >>> #xfs_repair -V >>> xfs_repair version 3.0.5 >>> >>> So is there any issue of compatibility with latest XFS_repair utils. >>> or it will work fine with my latest kernel(2.6.34). >> >> It works just fine, but the 3.1.x series of xfsprogs brings large >> repair memory savings. >> >>> Since some time mount fails. >> >> What mount messages, what platform? >> >> > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 5+ messages in thread
* XFS repair utils @ 2010-11-29 15:29 naveen yadav 0 siblings, 0 replies; 5+ messages in thread From: naveen yadav @ 2010-11-29 15:29 UTC (permalink / raw) To: hch, xfs Thanks for your response. I am using ARM as my target, and I got some time issue in radix tree.. with error Kernel BUG. radix_tree_tag_set+0x74/0xe43 [<801dfa80>] radix_tree_tag_set+0x74/0xe4 from[<801b6be0>] __xfs_inode_set_reclaim_tag+0x4c/0x7358:49:736 0358:49:736 [<801b6be0>] __xfs_inode_set_reclaim_tag+0x4c/0x70 from[<801b6c58>] xfs_inode_set_reclaim_tag+0358:49:752 x54/0xb8358:49:752 [<801b6c58>] xfs_inode_set_reclaim_tag+0x54/0xb8 from[<80182948>] xfs_iget+0x7d8/0x8b0358:49:752 [<80182948>] xfs_iget+0x7d8/0x8b0 from[<801a0eb0>] xfs_trans_iget+0x48/0x88358:49:767 [<801a0eb0>] xfs_trans_iget+0x48/0x88 from[<80186e88>] xfs_ialloc+0xd4/0x5b8358:49:767 [<80186e88>] xfs_ialloc+0xd4/0x5b8 from[<801a2014>] xfs_dir_ialloc+0x98/0x2a4358:49:783 [<801a2014>] xfs_dir_ialloc+0x98/0x2a4 from[<801a48b4>] xfs_create+0x2e0/0x6b8358:49:783 [<801a48b4>] xfs_create+0x2e0/0x6b8 from[<801b2fc0>] xfs_vn_mknod+0xc0/0x130358:49:783 [<801b2fc0>] xfs_vn_mknod+0xc0/0x130 from[<800c22cc>] vfs_create+0x80/0xe4358:49:799 [<800c22cc>] vfs_create+0x80/0xe4 from[<800c5328>] do_filp_open+0x284/0x8c8358:49:799 [<800c5328>] do_filp_open+0x284/0x8c8 from[<800b5858>] do_sys_open+0x6c/0x114358:49:814 [<800b5858>] do_sys_open+0x6c/0x114 from[<800102c4>] stack_done+0x20/0x3c358:49:814 On Mon, Nov 29, 2010 at 07:30:50PM +0530, naveen yadav wrote: > Hi All, > > I am using XFS 2.6.34 kernel on my target, and I have > #xfs_repair -V > xfs_repair version 3.0.5 > > So is there any issue of compatibility with latest XFS_repair utils. > or it will work fine with my latest kernel(2.6.34). It works just fine, but the 3.1.x series of xfsprogs brings large repair memory savings. > Since some time mount fails. What mount messages, what platform? _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-11-30 4:11 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-11-29 14:00 XFS repair utils naveen yadav 2010-11-29 14:55 ` Christoph Hellwig 2010-11-29 15:55 ` naveen yadav 2010-11-30 4:13 ` naveen yadav -- strict thread matches above, loose matches on Subject: below -- 2010-11-29 15:29 naveen yadav
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox