XFS: bad clientid on recovery on MIPS (VIPT cache)

Ajeet Yadav ajeet.yadav.77 at gmail.com
Thu Oct 21 08:27:15 CDT 2010


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_range in 2.6.30.9 as well.I
will be grateful if you can provide me sample code for the above API.



On Thu, Oct 21, 2010 at 6:22 PM, Christoph Hellwig <hch at infradead.org>wrote:

> On Thu, Oct 21, 2010 at 05:41:43PM +0530, Ajeet Yadav wrote:
> > 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: bad clientid
> > XFS: log mount/recovery failed: error 5
> > XFS: log mount failed
> > This problem does not occur, if I connect the same USB flash to PC/ARM
> > target.
> > I have tested this on 2.6.30 - 2.6.34 (It everywhere when concerend with
> > MIPS)
>
> 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 and sh actually implement these so far.
> You'll need to implement an implementation of these APIs for your cache
> architecture to make XFS work on MIPS with virtually indexed caches.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20101021/d0ebd809/attachment.htm>


More information about the xfs mailing list