Skip to contentSkip to conversation

btrfs send in 3.12 : can't find snapshot?

DISCUSSION Michael Welsh Duggan 4 participants 6 messages Dec 16, 2013 – Dec 17, 2013 Btrfs file system

lore
Share & tools
lore
#0 lore raw

I built the new btrfs-progs 3.12 recently. I note that the version information doesn't seem to match this:

    # ./btrfs --version
    Btrfs v0.20-rc1-358-g194aa4a

Regardless, I was trying to use btrfs send (which worked in the older btrfs), and failed. Here's an example:

    # ./btrfs send -vvv -p /snapshots/bo /snapshots/bp  > /dev/null
    At subvol /snapshots/bp
    ERROR: open @/snapshots/bp failed. No such file or directory

Any idea what might be going on here?

Here's the volume information:

    # ./btrfs sub show /
    /
            Name:                   @
            uuid:                   e5e505d6-1309-8447-b51e-73f08c9401d1
            Parent uuid:            156f93b9-1175-dc42-a1ee-65c00c5dcc2a
            Creation time:          2013-07-17 20:44:46
            Object ID:              259
            Generation (Gen):       296321
            Gen at creation:        20
            Parent:                 5
            Top Level:              5
            Flags:                  -
            Snapshot(s):
                                    snapshots/bo
                                    snapshots/bp

Kernel information:

    # uname -a
    Linux maru2 3.11-2-amd64 #1 SMP Debian 3.11.10-1 (2013-12-04) x86_64 GNU/Linux
Signature · 2 lines
Michael Welsh Duggan
([email protected])
#1 lore raw

Hello Michael,

Quoted 33 lines

I built the new btrfs-progs 3.12 recently. I note that the version information doesn't seem to match this:

   # ./btrfs --version
   Btrfs v0.20-rc1-358-g194aa4a

Regardless, I was trying to use btrfs send (which worked in the older btrfs), and failed. Here's an example:

   # ./btrfs send -vvv -p /snapshots/bo /snapshots/bp  > /dev/null
   At subvol /snapshots/bp
   ERROR: open @/snapshots/bp failed. No such file or directory

Any idea what might be going on here?

Here's the volume information:

   # ./btrfs sub show /
   /
           Name:                   @
           uuid:                   e5e505d6-1309-8447-b51e-73f08c9401d1
           Parent uuid:            156f93b9-1175-dc42-a1ee-65c00c5dcc2a
           Creation time:          2013-07-17 20:44:46
           Object ID:              259
           Generation (Gen):       296321
           Gen at creation:        20
           Parent:                 5
           Top Level:              5
           Flags:                  -
           Snapshot(s):
                                   snapshots/bo
                                   snapshots/bp
Quoted 1 line

Kernel information:

Here it seemed that you changed your default sub-volume.(259 not 5)
I sent a patch before to fix this problem, it has not been pushed into chris's master branch, patch url is:

https://patchwork.kernel.org/patch/3258971/

But is has been pushed into david's latest integration branch , you can pull from:

git pull http://github.com/kdave/btrfs-progs.git integration-20131211

Hopely it can fix your problem.^_^

Thanks,
Wang

Quoted 12 lines
   # uname -a
   Linux maru2 3.11-2-amd64 #1 SMP Debian 3.11.10-1 (2013-12-04) x86_64 GNU/Linux
Signature · 7 lines
Michael Welsh Duggan
([email protected])

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw
Quoted 41 lines · Wang Shilong

Hello Michael,

Quoted 33 lines

I built the new btrfs-progs 3.12 recently. I note that the version information doesn't seem to match this:

   # ./btrfs --version
   Btrfs v0.20-rc1-358-g194aa4a

Regardless, I was trying to use btrfs send (which worked in the older btrfs), and failed. Here's an example:

   # ./btrfs send -vvv -p /snapshots/bo /snapshots/bp  > /dev/null
   At subvol /snapshots/bp
   ERROR: open @/snapshots/bp failed. No such file or directory

Any idea what might be going on here?

Here's the volume information:

   # ./btrfs sub show /
   /
           Name:                   @
           uuid:                   e5e505d6-1309-8447-b51e-73f08c9401d1
           Parent uuid:            156f93b9-1175-dc42-a1ee-65c00c5dcc2a
           Creation time:          2013-07-17 20:44:46
           Object ID:              259
           Generation (Gen):       296321
           Gen at creation:        20
           Parent:                 5
           Top Level:              5
           Flags:                  -
           Snapshot(s):
                                   snapshots/bo
                                   snapshots/bp
Quoted 1 line

Kernel information:

Here it seemed that you changed your default sub-volume.(259 not 5) I sent a patch before to fix this problem, it has not been pushed into chris's master branch, patch url is:

Quoted 6 lines

https://patchwork.kernel.org/patch/3258971/

But is has been pushed into david's latest integration branch , you can pull from:

git pull http://github.com/kdave/btrfs-progs.git integration-20131211

After compiling this version the above tests works. Now, however, the receive fails:

    # ./btrfs send -p /snapshots/bo /snapshots/bp | ./btrfs receive /backup/snapshots/root/
    At subvol /snapshots/bp
    At snapshot bp
    ioctl(BTRFS_IOC_TREE_SEARCH, uuid, key 48f0ebae83fd32f1, UUID_KEY, 90139d8200afeaab) ret=-1, error: No such file or directory
    ioctl(BTRFS_IOC_TREE_SEARCH, uuid, key 48f0ebae83fd32f1, UUID_KEY, 90139d8200afeaab) ret=-1, error: No such file or directory
    ERROR: could not find parent subvolume

More volume information:

# ./btrfs sub show /backup/snapshots/root/bo
/backup/snapshots/root/bo
        Name:                   bo
        uuid:                   5e15ef24-f2d0-194f-886d-3f7afc7413a4
        Parent uuid:            9a226af3-8497-744b-90f7-d7e54d58946d
        Creation time:          2013-12-13 17:51:57
        Object ID:              1030
        Generation (Gen):       1046
        Gen at creation:        1042
        Parent:                 5
        Top Level:              5
        Flags:                  readonly
        Snapshot(s):
# ./btrfs sub show /snapshots/bo
/snapshots/bo
        Name:                   bo
        uuid:                   f132fd83-aeeb-f048-abea-af00829d1390
        Parent uuid:            e5e505d6-1309-8447-b51e-73f08c9401d1
        Creation time:          2013-12-13 17:50:15
        Object ID:              404
        Generation (Gen):       296977
        Gen at creation:        291623
        Parent:                 259
        Top Level:              259
        Flags:                  readonly
        Snapshot(s):
# ./btrfs sub show /snapshots/bp
/snapshots/bp
        Name:                   bp
        uuid:                   6f73d3f2-5f9b-4944-b2d2-3003331b2d10
        Parent uuid:            e5e505d6-1309-8447-b51e-73f08c9401d1
        Creation time:          2013-12-15 22:24:57
        Object ID:              405
        Generation (Gen):       296977
        Gen at creation:        296301
        Parent:                 259
        Top Level:              259
        Flags:                  readonly
        Snapshot(s):
Signature · 2 lines
Michael Welsh Duggan
([email protected])
#3 lore raw
Quoted 42 lines · Michael Welsh Duggan
Quoted 40 lines · Wang Shilong

Hello Michael,

Quoted 33 lines

I built the new btrfs-progs 3.12 recently. I note that the version information doesn't seem to match this:

    # ./btrfs --version
    Btrfs v0.20-rc1-358-g194aa4a

Regardless, I was trying to use btrfs send (which worked in the older btrfs), and failed. Here's an example:

    # ./btrfs send -vvv -p /snapshots/bo /snapshots/bp  > /dev/null
    At subvol /snapshots/bp
    ERROR: open @/snapshots/bp failed. No such file or directory

Any idea what might be going on here?

Here's the volume information:

    # ./btrfs sub show /
    /
            Name:                   @
            uuid:                   e5e505d6-1309-8447-b51e-73f08c9401d1
            Parent uuid:            156f93b9-1175-dc42-a1ee-65c00c5dcc2a
            Creation time:          2013-07-17 20:44:46
            Object ID:              259
            Generation (Gen):       296321
            Gen at creation:        20
            Parent:                 5
            Top Level:              5
            Flags:                  -
            Snapshot(s):
                                    snapshots/bo
                                    snapshots/bp
Quoted 1 line

Kernel information:

Here it seemed that you changed your default sub-volume.(259 not 5) I sent a patch before to fix this problem, it has not been pushed into chris's master branch, patch url is:

Quoted 8 lines
Quoted 6 lines

https://patchwork.kernel.org/patch/3258971/

But is has been pushed into david's latest integration branch , you can pull from:

git pull http://github.com/kdave/btrfs-progs.git integration-20131211

After compiling this version the above tests works. Now, however, the receive fails:

I will take a look at this issue.

Thanks,
wang

Quoted 51 lines
     # ./btrfs send -p /snapshots/bo /snapshots/bp | ./btrfs receive /backup/snapshots/root/
     At subvol /snapshots/bp
     At snapshot bp
     ioctl(BTRFS_IOC_TREE_SEARCH, uuid, key 48f0ebae83fd32f1, UUID_KEY, 90139d8200afeaab) ret=-1, error: No such file or directory
     ioctl(BTRFS_IOC_TREE_SEARCH, uuid, key 48f0ebae83fd32f1, UUID_KEY, 90139d8200afeaab) ret=-1, error: No such file or directory
     ERROR: could not find parent subvolume

More volume information:

# ./btrfs sub show /backup/snapshots/root/bo
/backup/snapshots/root/bo
         Name:                   bo
         uuid:                   5e15ef24-f2d0-194f-886d-3f7afc7413a4
         Parent uuid:            9a226af3-8497-744b-90f7-d7e54d58946d
         Creation time:          2013-12-13 17:51:57
         Object ID:              1030
         Generation (Gen):       1046
         Gen at creation:        1042
         Parent:                 5
         Top Level:              5
         Flags:                  readonly
         Snapshot(s):
# ./btrfs sub show /snapshots/bo
/snapshots/bo
         Name:                   bo
         uuid:                   f132fd83-aeeb-f048-abea-af00829d1390
         Parent uuid:            e5e505d6-1309-8447-b51e-73f08c9401d1
         Creation time:          2013-12-13 17:50:15
         Object ID:              404
         Generation (Gen):       296977
         Gen at creation:        291623
         Parent:                 259
         Top Level:              259
         Flags:                  readonly
         Snapshot(s):
# ./btrfs sub show /snapshots/bp
/snapshots/bp
         Name:                   bp
         uuid:                   6f73d3f2-5f9b-4944-b2d2-3003331b2d10
         Parent uuid:            e5e505d6-1309-8447-b51e-73f08c9401d1
         Creation time:          2013-12-15 22:24:57
         Object ID:              405
         Generation (Gen):       296977
         Gen at creation:        296301
         Parent:                 259
         Top Level:              259
         Flags:                  readonly
         Snapshot(s):
#4 lore raw
In reply to Michael Welsh Duggan

Hello Michael,

I sent a patch to fix the issue(cc you already), can you have a try and see if it fix your problem.

Thanks,
Wang

Quoted 101 lines · Michael Welsh Duggan
Quoted 40 lines · Wang Shilong

Hello Michael,

Quoted 33 lines

I built the new btrfs-progs 3.12 recently. I note that the version information doesn't seem to match this:

    # ./btrfs --version
    Btrfs v0.20-rc1-358-g194aa4a

Regardless, I was trying to use btrfs send (which worked in the older btrfs), and failed. Here's an example:

    # ./btrfs send -vvv -p /snapshots/bo /snapshots/bp  > /dev/null
    At subvol /snapshots/bp
    ERROR: open @/snapshots/bp failed. No such file or directory

Any idea what might be going on here?

Here's the volume information:

    # ./btrfs sub show /
    /
            Name:                   @
            uuid:                   e5e505d6-1309-8447-b51e-73f08c9401d1
            Parent uuid:            156f93b9-1175-dc42-a1ee-65c00c5dcc2a
            Creation time:          2013-07-17 20:44:46
            Object ID:              259
            Generation (Gen):       296321
            Gen at creation:        20
            Parent:                 5
            Top Level:              5
            Flags:                  -
            Snapshot(s):
                                    snapshots/bo
                                    snapshots/bp
Quoted 1 line

Kernel information:

Here it seemed that you changed your default sub-volume.(259 not 5) I sent a patch before to fix this problem, it has not been pushed into chris's master branch, patch url is:

Quoted 6 lines

https://patchwork.kernel.org/patch/3258971/

But is has been pushed into david's latest integration branch , you can pull from:

git pull http://github.com/kdave/btrfs-progs.git integration-20131211

After compiling this version the above tests works. Now, however, the receive fails:

     # ./btrfs send -p /snapshots/bo /snapshots/bp | ./btrfs receive /backup/snapshots/root/
     At subvol /snapshots/bp
     At snapshot bp
     ioctl(BTRFS_IOC_TREE_SEARCH, uuid, key 48f0ebae83fd32f1, UUID_KEY, 90139d8200afeaab) ret=-1, error: No such file or directory
     ioctl(BTRFS_IOC_TREE_SEARCH, uuid, key 48f0ebae83fd32f1, UUID_KEY, 90139d8200afeaab) ret=-1, error: No such file or directory
     ERROR: could not find parent subvolume

More volume information:

# ./btrfs sub show /backup/snapshots/root/bo
/backup/snapshots/root/bo
         Name:                   bo
         uuid:                   5e15ef24-f2d0-194f-886d-3f7afc7413a4
         Parent uuid:            9a226af3-8497-744b-90f7-d7e54d58946d
         Creation time:          2013-12-13 17:51:57
         Object ID:              1030
         Generation (Gen):       1046
         Gen at creation:        1042
         Parent:                 5
         Top Level:              5
         Flags:                  readonly
         Snapshot(s):
# ./btrfs sub show /snapshots/bo
/snapshots/bo
         Name:                   bo
         uuid:                   f132fd83-aeeb-f048-abea-af00829d1390
         Parent uuid:            e5e505d6-1309-8447-b51e-73f08c9401d1
         Creation time:          2013-12-13 17:50:15
         Object ID:              404
         Generation (Gen):       296977
         Gen at creation:        291623
         Parent:                 259
         Top Level:              259
         Flags:                  readonly
         Snapshot(s):
# ./btrfs sub show /snapshots/bp
/snapshots/bp
         Name:                   bp
         uuid:                   6f73d3f2-5f9b-4944-b2d2-3003331b2d10
         Parent uuid:            e5e505d6-1309-8447-b51e-73f08c9401d1
         Creation time:          2013-12-15 22:24:57
         Object ID:              405
         Generation (Gen):       296977
         Gen at creation:        296301
         Parent:                 259
         Top Level:              259
         Flags:                  readonly
         Snapshot(s):
#5 lore raw
In reply to Michael Welsh Duggan

Michael Welsh Duggan posted on Sun, 15 Dec 2013 22:40:55 -0500 as excerpted:

Quoted 4 lines

I built the new btrfs-progs 3.12 recently. I note that the version information doesn't seem to match this:

    # ./btrfs --version Btrfs v0.20-rc1-358-g194aa4a

I see Wang Shilong dealt with the snapshot issue; I'll tackle the version thing.

There was a bit of a hiccup in the versioning with the 3.12 tarball, since the version policy had just changed with it, and (I gather) the tarball prep script hadn't been updated appropriately. I believe a patch has already been applied to fix the problem (the patch was certainly posted on this list, but I haven't tracked whether it was actually applied yet) so the same problem won't happen the next time.

Meanwhile, btrfs properly reports v3.12 here, but I pull and build from live-git, and the v3.12 tagged commit simply happened to still be current HEAD last I updated. That does explain why the problem with the tarball version wasn't discovered earlier, however, since people (including the devs) building from live-git saw the expected v3.12; it was apparently only the process of preparing and releasing the tarball that was affected by the version bug.

Signature · 3 lines
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman