Cannot mount overlay with upperdir on overlay
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| linux (Ubuntu) |
High
|
Unassigned | ||
| Xenial |
High
|
Unassigned |
Bug Description
I have a docker setup using overlay as its storage driver. I mount an overlay in the container. Both the lower, upper and work directories are themselves on an overlay filesystem. This mount started to fail after upgrading to kernel 4.4.0-38 from 4.4.0-34 with the error message "overlayfs: filesystem on '/mnt/overlay/
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CurrentDesktop: Unity
Date: Fri Sep 30 20:06:03 2016
HibernationDevice: RESUME=
InstallationDate: Installed on 2016-07-23 (69 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. XPS13 9333
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.157.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/19/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: XPS13 9333
dmi.sys.vendor: Dell Inc.
Shaw (svrana) wrote : | #1 |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Joseph Salisbury (jsalisbury) wrote : | #3 |
Would it be possible for you to test the latest upstream stable kernel? Refer to https:/
If this bug is fixed in the mainline kernel, please add the following tag 'kernel-
If the mainline kernel does not fix this bug, please add the tag: 'kernel-
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
status: | Confirmed → Incomplete |
Changed in linux (Ubuntu Xenial): | |
status: | New → Incomplete |
importance: | Undecided → High |
tags: | added: kernel-da-key needs-bisect |
Shaw (svrana) wrote : | #4 |
Yes, exists in 4.4.23-
Shaw (svrana) wrote : | #5 |
Hmm, looking at the kernel source this seems intentional. See commit 76bc8e2843b66f8
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu Xenial): | |
status: | Incomplete → Confirmed |
Raphaël Droz (raphael-droz) wrote : | #6 |
Any workaround found so far? (still affect kernel 4.9 [both host and guest])
Shaw (svrana) wrote : | #7 |
I switched to devicemapper as the storage driver.
Brett Randall (javabrett) wrote : | #8 |
Commit link: https:/
Does anyone understand enough about "This does not work and does not make sense." to log an upstream/kernel bug, to request a fix/reconsidera
Brett Randall (javabrett) wrote : | #9 |
To answer my own question above, I found these posts: https:/
This change was made by a bot.