There is another issue, i updated xfsprog from 2.10.1 to 3.1.5, and found i could not make the xfs filesystem when the logical volume size large than 8TB with command mkfs.xfs -f -i size=512 /dev/vg+vg00+20120406101850/lv+nxx+lv0000, this command seems hang, it did not return for a long time, is there any parameter i should adjust? Thank you very much Best Regards, Daobang Wang. On 4/6/12, daobang wang <wangdb1981@xxxxxxxxx> wrote: > Hi All, > > I have found the solution, i updated the xfsprogs from 2.10.1 to > 3.1.5, and could repair it, Thanks. > > Best Wishes, > Daobang Wang. > > On 4/6/12, Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx> wrote: >> On 4/5/2012 1:48 AM, daobang wang wrote: >>> Hi stan, >>> >>> I duplicated the input/output error issue, about the detail >>> operations and logs, please see the attachments, Is there any way to >>> fix this? thanks! >>> >>> Best Regards, >>> Daobang Wang. >> >> >> These fiilesystem issues have nothing to do with linux-raid. I'm >> copying the XFS mailing list which is where this discussion should be >> taking place from this point forward. Please reply-to-all, and paste >> the output you previously attached, but inline this time. >> >> Also, since the XFS folks are unfamiliar with what you're doing up to >> this point, please provide a basic description of your hardware/storage >> setup, kernel version, mdraid configuration, xfs_info output as well as >> your fstab XFS mount options, and a description of your workload. >> >> My best guess at this point as to the du and ls errors is that your >> application is not behaving properly, or you're still running with XFS >> barriers disabled, which, I say _loudly_ for the 2nd time, you should >> NOT do in the absence of BBWC, which you stated you do not have. >> >> -- >> Stan >> > -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
