public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Tassonis <stuff@decentral.ch>
To: linux-kernel@vger.kernel.org
Subject: overlayfs: "filesystem of lowerdir is not supported" on cdrom
Date: Tue, 28 Oct 2014 19:10:36 +0100	[thread overview]
Message-ID: <544FDC1C.9040908@decentral.ch> (raw)

Hi

Just installed 3.18-rc2 and tried to test the overlayfs stuff:

$ mkdir /ovtmp
$ mount -t tmpfs tmpfs /ovtmp/
$ mkdir /ovtmp/work
$ mkdir /ovtmp/upper
$ mkdir /cdrw
$ mount /dev/sr0 /mnt
$ mount |egrep "ovtmp|sr0"

/dev/sr0 on /mnt type iso9660 (ro,relatime)
tmpfs on /ovtmp type tmpfs (rw,relatime)

$ mount -t overlayfs overlayfs \
 -olowerdir=/mnt,upperdir=/ovtmp/upper,workdir=/ovtmp/work /cdrw

mount: wrong fs type, bad option, bad superblock on overlayfs,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

$ dmesg |tail

[ 3266.793218] overlayfs: filesystem of lowerdir is not supported

However, the doc in Documentation/filesystems/overlayfs.txt states:

"The lower filesystem can be any filesystem supported by Linux and does
not need to be writable.  The lower filesystem can even be another
overlayfs.  The upper filesystem will normally be writable and if it
is it must support the creation of trusted.* extended attributes, and
must provide valid d_type in readdir responses, so NFS is not suitable."

So: Is the documentation wrong, the error message in dmesg wrong, or
have missed something completely?


Kind regards
Tim


             reply	other threads:[~2014-10-28 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 18:10 Tim Tassonis [this message]
2014-10-28 21:13 ` overlayfs: "filesystem of lowerdir is not supported" on cdrom Al Viro
2014-10-28 22:54   ` Al Viro
2014-10-29  2:47     ` Tim Tassonis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=544FDC1C.9040908@decentral.ch \
    --to=stuff@decentral.ch \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox