Re: Another Bug with cachefs during underlaying nfs server timeout

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 04 May 2010 19:03:59 David Howells wrote:
> Romain DEGEZ <romain.degez@xxxxxxxxxxxx> wrote:
> > [1365947.770498] page:ffffea000cb91cf8 flags:0200000000001008 count:0
> > mapcount:0 mapping:(null) index:7052

Hi David,

> I *think* that means that PG_private_2 (PG_fscache) is still set on the
>  page (the '1' three places from the end of the flags being bit 12).
> 
> Now this looks very odd...  Ext4 doesn't use fscache yet (as far as I
>  know), so this bit shouldn't be set in Ext4 pages.  The pages can't have
>  had this bit set when they were allocated, because
>  get_page_from_freelist() checks for that.
> 
> I'm not sure what's going on here.  PG_private_2 should only be set on
>  pages that NFS hands to fscache to read into.  At the point they're set,
>  NFS should still own them:-/
> 
> Are you using anything other than NFS that could be doing caching?  AFS of
>  9PFS for example?


Nothing like this : We are using NFSv3 with fscache and ext4 backend. Nothing 
special.

Here is an output of my /proc/mounts:

/dev/md3 /var/cache/fscache ext4 
rw,noatime,nodiratime,user_xattr,barrier=0,journal_async_commit,nobh,data=writeback 
0 0
storage-prod:/data/ondemand /data/ondemand nfs 
ro,noatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.10.30.209,mountvers=3,mountport=35795,mountproto=tcp,fsc,addr=10.10.30.209 
0 0

( /var/cache/fscache is the root cache dir configured in /etc/cachefilesd.conf )

Regards,

-- 
RD

--
Linux-cachefs mailing list
Linux-cachefs@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cachefs

[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]
  Powered by Linux