Re: [Linux-cachefs] 3.0.3 64-bit Crash running fscache/cachefilesd

[Дмитрий Ильин]

Same problem here bro)

Heavy NFS based web hosting too.

I get mostly this on 38 kernel

[416779.040059] CacheFiles: Error: Overlong wait for old active object
to go away
[416779.040104] object: OBJ43981
[416779.040127] objstate=OBJECT_LOOKING_UP fl=0 wbusy=2 ev=0[7b]
[416779.040154] ops=0 inp=0 exc=0
[416779.040174] parent=ffff8800cca3c3c0
[416779.040197] cookie=ffff880100029870 [pr=ffff8801131520f0
nd=ffff88000662b180 fl=7]
[416779.040241] key=[36]
'010007010100a00800000000e6c715cb23cd4aa38338eea581f3d1045c2e680a1b56d03d'
[416779.040325] xobject: OBJ431fe
[416779.040348] xobjstate=OBJECT_RECYCLING fl=0 wbusy=2 ev=20[3]
[416779.040373] xops=0 inp=0 exc=0
[416779.040394] xparent=ffff8800cca3c3c0
[416779.040416] xcookie=NULL

And 3.0.1 kernel crashes too.

No idea how to debug…

fscache is NOT stable and looks like will never be.
NFS without cache is too slow.

CIFS is even worse.
GFS2/OCFS2 too complex and unstable.
PVFS? Coda? GlusterFS? Lustre?
They do not suite well for shared web hosting(

Looks like clustering is bad idea and we'll have to return to separate servers and caching servers.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/