so I would guess you didn't unload the FS-Cache module between goes, which
would have reset the counters to 0. I should probably add a facility to allow
the counters to be reset to 0 without having to resort to unloading.
David
I cleared the cache rebooted using the 2.6.30-rc6 kernel, output of
/proc/.../stats is below.
FS-Cache statistics
Cookies: idx=2 dat=133335 spc=0
Objects: alc=133338 nal=0 avl=133338 ded=115616
ChkAux : non=0 ok=0 upd=0 obs=0
Pages : mrk=460795 unc=408918
Acquire: n=133337 nul=0 noc=0 ok=133337 nbf=0 oom=0
Lookups: n=133338 neg=133338 pos=0 crt=133338
Updates: n=0 nul=0 run=0
Relinqs: n=115616 nul=0 wcr=0
AttrChg: n=0 ok=0 nbf=0 oom=0 run=0
Allocs : n=0 ok=0 wt=0 nbf=0
Allocs : ops=0 owt=0
Retrvls: n=161495 ok=0 wt=15633 nod=161495 nbf=0 int=0 oom=0
Retrvls: ops=161495 owt=1623
Stores : n=460765 ok=460765 agn=0 nbf=0 oom=0
Stores : ops=166483 run=627248
Ops : pend=1623 run=326355 enq=627248
Ops : dfr=0 rel=327978 gc=0
I then rebooted again to clear counters and started the same copy again,
below is output from dmesg and /proc/.../stats/
Pid: 2058, comm: kslowd Not tainted 2.6.30-rc6 #1
Call Trace:
[<ffffffffa027cc6e>] ? cachefiles_read_waiter+0xd9/0x147 [cachefiles]
[<ffffffff804bc35d>] ? __wait_on_bit+0x60/0x6f
[<ffffffff8022bb3b>] ? __wake_up_common+0x3f/0x71
[<ffffffff8022cbb2>] ? __wake_up+0x30/0x44
[<ffffffff8024a3fb>] ? __wake_up_bit+0x28/0x2d
[<ffffffffa003a793>] ? ext3_truncate+0x4d7/0x8ed [ext3]
[<ffffffff802c827a>] ? __getblk+0x25/0x209
[<ffffffff802c827a>] ? __getblk+0x25/0x209
[<ffffffff802915c9>] ? unmap_mapping_range+0x59/0x1ff
[<ffffffff8022cbb2>] ? __wake_up+0x30/0x44
[<ffffffff80293550>] ? vmtruncate+0xc2/0xe2
[<ffffffff802bd67b>] ? inode_setattr+0x22/0x10a
[<ffffffffa003baa5>] ? ext3_setattr+0x17b/0x1e6 [ext3]
[<ffffffff802bd8e9>] ? notify_change+0x186/0x2c9
[<ffffffffa02789de>] ? cachefiles_attr_changed+0x133/0x1cd [cachefiles]
[<ffffffff8024a411>] ? wake_up_bit+0x11/0x22
[<ffffffffa0278f7f>] ? cachefiles_lookup_object+0xcf/0x12a [cachefiles]
[<ffffffffa0269165>] ? fscache_lookup_object+0x110/0x122 [fscache]
[<ffffffffa026989a>] ? fscache_object_slow_work_execute+0x567/0x65f
[fscache]
[<ffffffff8027e102>] ? slow_work_thread+0x285/0x43a
[<ffffffff8024a422>] ? autoremove_wake_function+0x0/0x2e
[<ffffffff8027de7d>] ? slow_work_thread+0x0/0x43a
[<ffffffff8024a2f3>] ? kthread+0x54/0x81
[<ffffffff8020c93a>] ? child_rip+0xa/0x20
[<ffffffff8024a29f>] ? kthread+0x0/0x81
[<ffffffff8020c930>] ? child_rip+0x0/0x20
CacheFiles: I/O Error: Readpage failed on backing file 100000000000830
FS-Cache statistics
Cookies: idx=2 dat=133335 spc=0
Objects: alc=4 nal=0 avl=4 ded=1
ChkAux : non=0 ok=2 upd=0 obs=0
Pages : mrk=0 unc=0
Acquire: n=133337 nul=0 noc=133334 ok=3 nbf=133334 oom=0
Lookups: n=4 neg=0 pos=4 crt=0
Updates: n=0 nul=0 run=0
Relinqs: n=1 nul=0 wcr=0
AttrChg: n=0 ok=0 nbf=0 oom=0 run=0
Allocs : n=0 ok=0 wt=0 nbf=0
Allocs : ops=0 owt=0
Retrvls: n=1 ok=1 wt=1 nod=0 nbf=0 int=0 oom=0
Retrvls: ops=1 owt=0
Stores : n=0 ok=0 agn=0 nbf=0 oom=0
Stores : ops=0 run=0
Ops : pend=0 run=1 enq=1
Ops : dfr=0 rel=1 gc=0
I did try the clean cache reboot copy once then copy again with no
reboot in between and as soon as the second copy started dmesg spit out
the same error. Also pretty much the same stats from /proc/.../stats
so I didn't include them.
Anything else I can provide you with for debugging?
Edward
--
Linux-cachefs mailing list
Linux-cachefs@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cachefs
