Some interesting new information (at least interesting to me). Ignoring the unionfs issue for the moment, I played around with the pinned files. I found out that persistence works if I only pin the following 4 files:
Package: udev Pin: version 093-0ubuntu18.0edgy2 Pin-Priority: 1001 Package: upstart Pin: version 0.2.7-7 Pin-Priority: 1001 Package: upstart-compat-sysv Pin: version 0.2.7-7 Pin-Priority: 1001 Package: upstart-logd Pin: version 0.2.7-7 Pin-Priority: 1001 The other thing that I did was upgrade to the 1.91 version of casper from gutsy because I suspected that the other debian changes had been rolled into the gutsy version of casper. Sure enough, persistence works fine. It seemed that gutsy's casper file was fine as it has been revised. The other thing that I had done, before upgrading to the gutsy version of casper, was to unpin the three upstart files. Again, with this last change, persistence still worked, but I received a failure to umount local filesystems. So, persistence worked with the only pinned file was udev. I have suspected this from the beginning, but this really re-enforces my belief that there has to be some issue in udev that is causing this problem. Alternatively, it could be an interaction between udev and the upstart files. But, based upon these results, it seems there has to be a problem in one of these. I am going to play around a little more to see if I can generate any additional useful information. __________________ -- feisty 20070210/herd5 persistent mode doesn't work https://bugs.launchpad.net/bugs/84591 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
