This is fixed in Vivid now that 3.19 has landed.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1405004
Title:
10de:
This is fixed in utopic and later.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1277741
Title:
15 sec timeout when
Hi,
this is an Ubuntu-specific bug, the overlayfs v1 compat patch is not
included upstream.
(For completeness, I did boot the 3.19-rc4 mainline kernel and verify
that, per comment 4.)
FWIW, I think (but am not sure how to confirm) that it's falling into
vfs_rename with flags including RENAME_WHI
Unlinking a file or directory and renaming a file all result in a
symlink whiteout, it's just renaming a file that does the wrong thing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/14104
Reading what seems to be the relevant commit:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
vivid.git;a=commitdiff;h=9a742a48114e416e9a4cd6e8615ba0d261dda599
If I'm reading that right, then a v1 overlayfs (mounted as "overlayfs")
should be using the old-style (symlink) whiteouts, right? Why am I
s
OK, this is interesting.
root@plonk:~# mkdir /lower /upper /work /ovl
root@plonk:~# touch /lower/testfile
root@plonk:~# mkdir /lower/testdir
root@plonk:~# mount -t overlay -o lowerdir=/lower,upperdir=/upper,workdir=/work
overlay /ovl
root@plonk:~# mv /ovl/testfile /ovl/renamed-testfile
root@plonk
** Description changed:
On a recent vivid livecd, after I rename a file that exists in the lower
filesystem, the whiteout entry is visible.
root@ubuntu:~# ls -l /etc/fstab
-rw-r--r-- 1 root root 63 Jan 13 11:56 /etc/fstab
root@ubuntu:~# mv /etc/fstab /etc/fstab.renamed
root@ubuntu:~
Not true of all directories, actually. /root is special somehow.
(detach_mounts is suspicious... probably the initramfs mounted the real
root at /root, or something like that?) Renaming /mnt or /opt works
properly and no whiteout is left behind.
** Summary changed:
- 3.18 overlayfs doesn't rename
Public bug reported:
On a recent vivid livecd, after I rename a file that exists in the lower
filesystem, the whiteout entry is visible.
root@ubuntu:~# ls -l /etc/fstab
-rw-r--r-- 1 root root 63 Jan 13 11:56 /etc/fstab
root@ubuntu:~# mv /etc/fstab /etc/fstab.renamed
root@ubuntu:~# ls -l /etc/fsta
Hi,
The following commit:
http://cgit.freedesktop.org/nouveau/linux-2.6/patch/?id=4761703bd04bbdf56396d264903cc5a1fdcb3c01
fixes the bug for me. I tested it by rebuilding the current vivid kernel
(3.16.0-28.38) with that patch added.
That commit is found in the linux-3.19 branch at
http://cgit.
Hi,
Thanks for the guidance.
My system does not boot properly with the 3.19-rc1 and 3.19-rc2 mainline
kernels. Some upstart job is hanging. I will investigate that
separately.
The bug exists in the 3.18.1 mainline kernel.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.1
Public bug reported:
Hi,
I'm opening a new report against the kernel, as requested by Christopher
M. Penalver (penalvch) in https://bugs.launchpad.net/ubuntu/+source
/xserver-xorg-video-nouveau/+bug/1181902/comments/18
I'm including apport information collected via ssh from the vivid daily
liveC
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1277741
Title:
15 sec timeout when mounting with nfs4
Status in “linu
Public bug reported:
With the default nfs-common configuration (rpc.gssd not running), there
is a 15 second delay when mounting an NFSv4 filesystem. After setting
NEED_GSSD=yes and starting rpc.gssd, there is no delay.
I don't know exactly when this was introduced. I reproduced it in
trusty, in s
Also affected on Elitebook 8560w (Quadro 1000M). Confirming fixed in
3.13.0-5.20 which is now in trusty.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
On a DL380 G5 with a P400 array, this seems to be working again with the
lts-raring kernel (3.8.0-32-generic) and newer (e.g. lts-saucy
3.11.0-13-generic from ppa:canonical-kernel-team/ppa). Can anyone else
verify that?
--
You received this bug notification because you are a member of Kernel
Pack
16 matches
Mail list logo
