I use CFS quite a bit and had no luck getting it to run when manually compiled (it currently lacks the ~amd64 keyword) until I used -m32 to compile it. It's now working very well on all my 32 and 64 bit systems. The really odd error that I was getting prior to using -m32 was: "RPC: Can't encode arguments" I guess that makes sense as it's caused by a marshalling failure inside RPC but I can't help but think that rpcgen should have make the correct marshalling bits. Oh well. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Please tell me you didn't CFLAGS="-m32" emerge app-crypt/cfs, please!
Yes, I know that in general that's a baaaad idea but in this particular case it allowed my to get all my data out of a cfs mount. I've tested all the data and there was no corruption. I actually modified the ebuild rather than setting CFLAGS in the environment.
