On Wed, Jul 23, 2014 at 1:40 PM, Klaus Kreil <klaus.kreil@xxxxxxxxxxxx> wrote: > > >> Is there some hint in the dmesg output? >> > The messag from dmesg reads as follows: > [ 1.323319] overlayfs: failed to resolve '/.work': -2 > > Now that I find strange because an ls -la /mnt/root_rw from the emergency > shell started from my initramfs looks as follows: > # ls -la /mnt/root_rw/ > total 52 > drwxr-xr-x 11 0 0 4096 Jul 21 22:57 . > drwxr-xr-x 5 0 0 0 Jul 20 23:36 .. > drwxr-xr-x 2 0 0 4096 Jul 20 23:26 .work > drwxr-xr-x 2 0 0 4096 Feb 25 23:36 dev > drwxr-xr-x 7 0 0 4096 Jul 21 22:31 etc > drwxr-xr-x 3 0 0 4096 Mar 3 21:10 lib64 > drwx------ 2 0 0 16384 Feb 25 23:28 lost+found > drwx------ 2 0 0 4096 May 29 13:01 root > drwxr-xr-x 2 0 0 4096 Jul 21 22:30 run > drwxrwxrwt 4 0 0 4096 Jul 21 22:31 tmp > drwxr-xr-x 6 0 0 4096 Apr 25 18:47 var > > To me this shows that the directory actually exists ... although the error > message states that it "failed to resolve" and not "No such file or > directory" or a similar message. > > The mount command from within the initramfs (all on one line) looks as > follows: > mount -t overlayfs overlayfs -o > lowerdir=/mnt/root_ro,upperdir=/mnt/root_rw,workdir=/.work /mnt/root > > and the output from the mount command (also from within the rescue-shell): > # mount > none on /dev type devtmpfs (0) > none on /proc type proc (0) > none on /sys type sysfs (0) > /dev/xvda1 on /mnt/root_ro type ext4 (ro,noatime) > /dev/xvda3 on /mnt/root_rw type ext4 (noatime,user_xattr,acl) > > So I am still somehow at loss and don't know where to go from here. > > Thanks again and best regards, > > Klaus > > P.S. Do you want me to move this discussion the the mailing list? > -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
