On 10/16/07, Erez Zadok <[EMAIL PROTECTED]> wrote: > Ryan, I brought the issue up on lkml, and there was some discussion about > ensuring that msync(2) never returns AOP_WRITEPAGE_ACTIVATE back to > userland. In addition, based on recommendations from Pekka, I've got this > patch tested well on 2.6.23.1. I plan to test it on all the backports and > then release it officially. But in the mean time, it'd be very useful if > anyone who's noted problems with msync(2) (esp. when using unionfs w/ tmpfs) > to try this patch below. I especially like it if you can try it with an > unpatched apt-get and see if when it calls msync(2), does it ever get > AOP_WRITEPAGE_ACTIVATE back.
Thank you, looks like we have a winner! It patched cleanly against 2.1.6 for 2.6.22 and Debian's 2.6.22-4 source tree + other junk needed for Finnix to work. I can now do an "apt-get check" without issues. However, at the beginning of an "apt-get update", I get this: unionfs: error creating directory tree for rename, bindex = 1, err = -30 unionfs: error creating directory tree for rename, bindex = 1, err = -30 unionfs: error creating directory tree for rename, bindex = 1, err = -30 However, the update operation seems to complete successfully. Is this a concern? Ryan _______________________________________________ unionfs mailing list: http://unionfs.filesystems.org/ unionfs@mail.fsl.cs.sunysb.edu http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
