Re: Unionmount and overlayfs testsuite

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote:

> # LC_ALL=C TEST_OVERLAYFS="1" ./run.sh
> [ run.sh ] TEST_OVERLAYFS is 1
> ***
> *** ./run.sh open-plain.test
> ***
> [ mount_union.sh ] TEST_OVERLAYFS is 1
> TEST100: Open O_RDONLY
>  - open_file -r /mnt/a/foo100 -R :xxx:yyy:zzz
>  - open_file -r /mnt/a/foo100 -R :xxx:yyy:zzz
> TEST101: Open O_WRONLY
>  - open_file -w /mnt/a/foo101 -W q
> /mnt/a/foo101: Test file not on upper filesystem  (line 30)

This looks like what I see when I run it:

	[root@andromeda union-testsuite]# TEST_OVERLAYFS=1 ./run.sh 
	***
	*** ./run.sh open-plain.test
	***
	umount: /mnt: not mounted
	TEST100: Open O_RDONLY
	 - open_file -r /mnt/a/foo100 -R :xxx:yyy:zzz
	 - open_file -r /mnt/a/foo100 -R :xxx:yyy:zzz
	TEST101: Open O_WRONLY
	 - open_file -w /mnt/a/foo101 -W q
	/mnt/a/foo101: Test file not on upper filesystem  (line 30)

I think the problem is that the script expecting the "upper" fs inodes to have
the overlay superblock dev ID and not the upper superblock dev ID.  That
should be easily fixable.

David
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux