Is this still happening? I no longer have the system that I found this bug on. I posted the workaround in this threads first message, and a solution was committed to Ubuntu long ago. Should not be a problem in current ubuntu. Yes, my searches say that the fix was committed in July 2011.
If you are still having this issue, and you have updated to a current version, then post a new bug: You've caught a regression. If you have not updated, then do. On 7 October 2012 04:00, rbhkamal <[email protected]> wrote: > Where do get the fix for this? Thanks > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/663069 > > Title: > "non-accessable symlink" errors when using aufs-shaddowed read-only > root filesystem > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/663069/+subscriptions -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to a duplicate bug report (729338). https://bugs.launchpad.net/bugs/663069 Title: "non-accessable symlink" errors when using aufs-shaddowed read-only root filesystem Status in “linux” package in Ubuntu: Fix Released Bug description: When I updated my pxeboot/nfs system to 10.10, several applets failed to load, and the log files contained the following messages: Oct 19 22:25:58 computer08 kernel: [ 66.326808] non-accessible hardlink creation was attempted by: gconfd-2 (fsuid 1000) Oct 19 22:26:05 computer08 kernel: [ 73.491138] non-accessible hardlink creation was attempted by: gconfd-2 (fsuid 114) Oct 19 22:26:05 computer08 kernel: [ 73.580608] non-accessible hardlink creation was attempted by: gdm-session-wor (fsuid 1000) Oct 19 22:26:09 computer08 kernel: [ 77.545565] non-accessible hardlink creation was attempted by: indicator-apple (fsuid 1000) Oct 19 22:26:09 computer08 kernel: [ 77.670861] non-accessible hardlink creation was attempted by: indicator-apple (fsuid 1000) Setting kernel.yama.protected_nonaccess_hardlinks=0 allows everything to work. The read-only root is configured according to the instructions at http://www.logicsupply.com/blog/2009/01/27/how-to-build-a-read-only- linux-system . It uses a initramfs script to create a tmpfs, move /, and mount the aufs union filesystem on / early in the boot process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/663069/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
