[Bug 663069] [NEW] "non-accessable symlink" errors when using aufs-shaddowed read-only root filesystem

[robbak]

Public bug reported:

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.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
"non-accessable symlink" errors when using aufs-shaddowed read-only root filesystem
https://bugs.launchpad.net/bugs/663069
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.