overlayfs shows some files as ?????

Bug #1167305 reported by Matthias Gehre
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

1. I mounted an overlayfs with uppderdir=/a, lowerdir=/b to /c
2. I copied fileA to the upperdir
3a. Did 'ls -l /a' Output is
-rwxrwxrwx 1 root root 22153090041 Jan 11 22:45 fileA
3b. Did 'ls -l /b' Output is empty.
3c. Did 'ls -l /c'. Output is
-????????? ? ? ? ? ? fileA
4. Did 'stat /c/fileA', Output is:
stat: cannot stat `fileA': No such file or directory

Is overlayfs broken? Did I do something wrong?
There is nothing in dmesg. Kernel is 3.5.0-26-generic #42.

How can I debug this?
I can do fairly advanced specific kernel debugging/recompiling with patches etc, but I don't know where to start.
---
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D2', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D9p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 12.10
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: System manufacturer System Product Name
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LC_CTYPE=en_US.UTF-8
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic root=UUID=34781a0f-967e-4105-8127-22f56322773c ro nomodeset bootdegraded=true
ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-26-generic N/A
 linux-backports-modules-3.5.0-26-generic N/A
 linux-firmware 1.95
RfKill: Error: [Errno 2] No such file or directory
Tags: quantal
Uname: Linux 3.5.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

WifiSyslog: Apr 10 12:31:54 data0 kernel: [345384.976058] usb 1-4: reset high-speed USB device number 3 using ehci_hcd
dmi.bios.date: 04/07/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1013
dmi.board.name: A8N-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 2.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1013:bd04/07/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Matthias Gehre (m-gehre)
description: updated
Matthias Gehre (m-gehre)
Changed in lxc (Ubuntu):
status: New → Invalid
no longer affects: lxc (Ubuntu)
Matthias Gehre (m-gehre)
no longer affects: linux
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1167305

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: quantal
Revision history for this message
Matthias Gehre (m-gehre) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Matthias Gehre (m-gehre) wrote : BootDmesg.txt

apport information

Revision history for this message
Matthias Gehre (m-gehre) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Matthias Gehre (m-gehre) wrote : Lspci.txt

apport information

Revision history for this message
Matthias Gehre (m-gehre) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Matthias Gehre (m-gehre) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Matthias Gehre (m-gehre) wrote : ProcModules.txt

apport information

Revision history for this message
Matthias Gehre (m-gehre) wrote : UdevDb.txt

apport information

Revision history for this message
Matthias Gehre (m-gehre) wrote : UdevLog.txt

apport information

Matthias Gehre (m-gehre)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

I'm not sure this is a bug. The upperdir is maintained by overlayfs as a delta between lowerdir and the mount target (i.e. a and c). You're not meant to play with the upperdir yorself. If you, after this experiment, unmount and remount the overlayfs, does the file then show up correctly?

Revision history for this message
Matthias Gehre (m-gehre) wrote :

You are right [1]. I thought that this would be allowed. This bug can be closed.

I needed to modify the underlying filesystems because of the following: rename() on the overlayfs gave me EOVERFLOW. Maybe you got an idea about what may cause EOVERFLOW as result to rename syscall?

[1]:
Last paragraph of Documentation/filesystems/overlayfs.txt:
Changes to the underlying filesystems while part of a mounted overlay
filesystem are not allowed. If the underlying filesystem is changed,
the behavior of the overlay is undefined, though it will not result in
a crash or deadlock.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.