Badly broken. I got Aufs2.1 from git on October 14, it is the only patch on pristine source, configured as I have done it many times before. I also checked that I am using aufs2-util from 2.1 git.
There is a lot wrong, but something to start with: I have a file in a partition. If I copy that into the layered filesystem, it seems to be the same, same size and permissions, but gives a different md5sum. I was testing a tarball, and 'tar' also gave errors when tried to expand it in the layered f.s.
However, the 184.108.40.206 kernel, configured the same, with Aufs2.1 from git October 6, works ok. I did an extra check to be sure. The same tarball, md5sum was ok, tar worked.
Earlier, I have built Puppy Linux with the 220.127.116.11 kernel and Aufs2 patch from git on June 26, and that also was ok. That kernel was also configured the same.
Someone else has reported that 18.104.22.168 works, 22.214.171.124 doesn't.
Well, this is bad news for me, as a lot of effort is waisted. I either have to roll back to an earlier Aufs2, or wait until it is fixed. Then I have to go through the entire process of compiling the kernel again, and probably will need to re-do all the 3rd-party modules, then of course re-upload lots of files.
Comments:Posted on 18 Oct 2010, 21:55 by kirk
I've had problems with aufs2-util for 2.1 with the 126.96.36.199 kernel. I've been using patriot's clean shutdown stuff in rc.shutdown, but it would hang with the new aufs-utils. I was hoping Junjiro would be putting out another release soon, but I guess he's got a life :). To bad the kernel bozos decided union mounts was the only way to go. I probably should just try compiling aufs2-util again, if that doesn't work I guess I'll try aufs 2 instead of aufs 2.1 if it supports 2.6.35.