Dear member, If I remove USB flash storage from PC/ARM/MIPS target (i.e without umount) while copying file to XFS partition and connect it to MIPS target I always get XFS: xlog_recover_process_data:
Dear member, If I remove USB flash storage from PC/ARM/MIPS target (i.e without umount) while copying file to XFS partition and connect it to MIPS target I always get XFS: xlog_recover_process_data:
Since Linux 2.6.34 Linux uses the flush_kernel_vmap_range/ invalidate_kernel_vmap_range APIs to make I/O to vmapped areas work on systems with virtually indexed caches. Unfortunately only arm, parisc
Thanks for response, Linux kernel I am using is 2.6.30, where as XFS I have ported until 2.6.34 on given kernel. Do you think I need the mentioned API flush_kernel_vmap_range/invalidate_kernel_vmap
Hello, I wish to know, why the problem of bad clientid does not come, if we safely umount the USB storage device. Also if anyone can help where XFS uses these flush_kernel_vmap_range/invalidate_kerne
I don't really know how to implement it - it's up to the cache architecture. Take a look at the existing implementations in 2.6.34+ kernels and possibly ask on the Linux-mips mainglinglist how to imp
Ok, I will implement flush_kernel_vmap_range/invalidate_kernel_vmap_range APIs but do I need to modify XFS code also ? Where do I make call to flush_kernel_vmap_range()/ invalidate_kernel_vmap_range(
Hi, You are using which kernel version ? because this is fixed in XFS in kernel 2.6.34 http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commit;h=73c77e2ccc14413c232c3e0b3aa43a0c4b7