Thread (83 messages) 83 messages, 8 authors, 2014-07-09

Re: Unionmount and overlayfs testsuite

From: Sedat Dilek <hidden>
Date: 2014-05-29 20:00:44
Also in: lkml

On Thu, May 29, 2014 at 9:35 PM, David Howells [off-list ref] wrote:
Sedat Dilek [off-list ref] wrote:
quoted
# 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.
"Fixable" in your testsuite?

- Sedat -
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help