I'm still seeing this on 12.04, but not on 13.04. Reproducible as
follows:
me@laptop ~/temp $ mkdir ro rw aufs
me@laptop ~/temp $ touch ro/dummy
me@laptop ~/temp $ sudo mount -t aufs -o dirs=rw:ro=ro none aufs
[sudo] password for me:
me@laptop ~/temp $ ls aufs/
dummy
me@laptop ~/temp $ rm
Upgrade from what to what?
I see this on a tmpfs+aufs mount.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663069
Title:
non-accessable symlink errors when using aufs-shaddowed read-only
root
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
Where do get the fix for this? Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663069
Title:
non-accessable symlink errors when using aufs-shaddowed read-only
root filesystem
To manage
This was fixed by this commit:
UBUNTU: ubuntu: Yama: if an underlying filesystem provides a permissions op
When we are checking permissions on hardlinks we use generic_permissions()
to work out if the user actually has read/write permissions and only
then allow the link.
** Changed in: launchpad
Status: Triaged = Won't Fix
** No longer affects: launchpad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663069
Title:
non-accessable symlink errors when using
** Also affects: launchpad
Importance: Undecided
Status: New
** Changed in: launchpad
Status: New = Triaged
** Changed in: launchpad
Importance: Undecided = Low
** Tags added: paralleltest
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: launchpad
Importance: Low = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663069
Title:
non-accessable symlink errors when using aufs-shaddowed read-only
root filesystem
Confirmed. This also causes problems if you try to use aufs to create a
sandbox directory for LTSP guest users, like this:
http://kristianlyng.wordpress.com/2010/03/19/a-sandboxed-home-directory/
This fails because xauth can't remove and replace the .Xauthority file
when you log in graphically.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663069
Title:
non-accessable symlink errors when using aufs-shaddowed read-only root
Can be easily reproduced with the following steps:
mkdir ro rw aufs
touch ro/foo
sudo mount -t aufs -o br:rw:ro none aufs
mv aufs/{foo,bar}
Gives the following output:
mv: cannot move `aufs/foo' to `aufs/bar': Operation not permitted
And:
dmesg | tail -1
[179473.298795] non-accessible
11 matches
Mail list logo
