Hello list, i wanted to try to out btrfs send and restore but i''m failing on a simple step: [server: /btrfs/target]# btrfs send /btrfs/src/\@snapshot/1 | btrfs receive /btrfs/target/\@snapshot/ At subvol /btrfs/src/@snapshot/1 At subvol 1 [server: /btrfs/target]# ls -la /btrfs/target/\@snapshot/ total 4 drwxr-xr-x 1 root root 2 Oct 11 20:25 . dr-xr-xr-x 1 root root 18 Oct 11 20:25 .. dr-xr-xr-x 1 root root 52 Oct 10 23:52 1 <= works fine [server: /btrfs/target]# btrfs send -i /btrfs/src/\@snapshot/1 /btrfs/src/\@snapshot/2 | btrfs receive /btrfs/target/\@snapshot/ At subvol /btrfs/src/@snapshot/2 At subvol 2 ERROR: failed to open /btrfs/target/@snapshot/@snapshot/1/test.tar. No such file or directory Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Oct 11, 2012 at 09:33:54PM +0200, Stefan Priebe wrote:> [server: /btrfs/target]# btrfs send -i /btrfs/src/\@snapshot/1 > /btrfs/src/\@snapshot/2 | btrfs receive /btrfs/target/\@snapshot/ > At subvol /btrfs/src/@snapshot/2 > At subvol 2 > ERROR: failed to open /btrfs/target/@snapshot/@snapshot/1/test.tar. No such file or directory^^^^^^^^^^^^^^^^^^^ I wonder if this is the ghost snapshot dir entry that Miao fixed. Did somehow get into the ''send'' stream and confused the receive side. david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Am 11.10.2012 21:43, schrieb David Sterba:> On Thu, Oct 11, 2012 at 09:33:54PM +0200, Stefan Priebe wrote: >> [server: /btrfs/target]# btrfs send -i /btrfs/src/\@snapshot/1 >> /btrfs/src/\@snapshot/2 | btrfs receive /btrfs/target/\@snapshot/ >> At subvol /btrfs/src/@snapshot/2 >> At subvol 2 >> ERROR: failed to open /btrfs/target/@snapshot/@snapshot/1/test.tar. No such file or directory > ^^^^^^^^^^^^^^^^^^^ > > I wonder if this is the ghost snapshot dir entry that Miao fixed. Did > somehow get into the ''send'' stream and confused the receive side. > > davidi missed two facts: 1.) vanilla kernel 3.6.1 2.) latest btrfs tools git (cloned at 10/10/2012) Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On thu, 11 Oct 2012 21:54:48 +0200, Stefan Priebe wrote:> Am 11.10.2012 21:43, schrieb David Sterba: >> On Thu, Oct 11, 2012 at 09:33:54PM +0200, Stefan Priebe wrote: >>> [server: /btrfs/target]# btrfs send -i /btrfs/src/\@snapshot/1 >>> /btrfs/src/\@snapshot/2 | btrfs receive /btrfs/target/\@snapshot/ >>> At subvol /btrfs/src/@snapshot/2 >>> At subvol 2 >>> ERROR: failed to open /btrfs/target/@snapshot/@snapshot/1/test.tar. No such file or directory >> ^^^^^^^^^^^^^^^^^^^ >> >> I wonder if this is the ghost snapshot dir entry that Miao fixed. Did >> somehow get into the ''send'' stream and confused the receive side. >> >> david > > i missed two facts: > 1.) vanilla kernel 3.6.1 > 2.) latest btrfs tools git (cloned at 10/10/2012)Sorry, I can not reproduce this problem, could you send me the detailed steps? Thanks Miao> > Stefan > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Am 15.10.2012 12:16, schrieb Miao Xie:> On thu, 11 Oct 2012 21:54:48 +0200, Stefan Priebe wrote: >> Am 11.10.2012 21:43, schrieb David Sterba: >>> On Thu, Oct 11, 2012 at 09:33:54PM +0200, Stefan Priebe wrote: >>>> [server: /btrfs/target]# btrfs send -i /btrfs/src/\@snapshot/1 >>>> /btrfs/src/\@snapshot/2 | btrfs receive /btrfs/target/\@snapshot/ >>>> At subvol /btrfs/src/@snapshot/2 >>>> At subvol 2 >>>> ERROR: failed to open /btrfs/target/@snapshot/@snapshot/1/test.tar. No such file or directory >>> ^^^^^^^^^^^^^^^^^^^ >>> >>> I wonder if this is the ghost snapshot dir entry that Miao fixed. Did >>> somehow get into the ''send'' stream and confused the receive side. >>> >>> david >> >> i missed two facts: >> 1.) vanilla kernel 3.6.1 >> 2.) latest btrfs tools git (cloned at 10/10/2012) > > Sorry, I can not reproduce this problem, could you send me the detailed steps?mhm there is nothing special. But i try to provide more information / a small howto: # mount |grep btrfs /dev/sdb on /btrfs/src type btrfs (rw) /dev/sdc on /btrfs/target type btrfs (rw) # btrfs subvolume list /btrfs/target/ # btrfs subvolume list /btrfs/src/ ID 277 top level 5 path @snapshot/1 ID 278 top level 5 path @snapshot/2 ID 288 top level 5 path @snapshot/3 # btrfs send /btrfs/src/\@snapshot/1 | btrfs receive /btrfs/target/\@snapshot/ At subvol /btrfs/src/@snapshot/1 At subvol 1 # Now i was trying to send an incremental snapshot: # btrfs send -i /btrfs/src/\@snapshot/1 /btrfs/src/\@snapshot/2 | btrfs receive /btrfs/target/\@snapshot/ At subvol /btrfs/src/@snapshot/2 At subvol 2 ERROR: failed to open /btrfs/target/@snapshot/@snapshot/1/test.tar. No such file or directory # Greets, Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Stefan, Is /btrfs/target/\@snapshot/ a subvolume or a directory? can you pls try the patch that I posted here: http://www.spinics.net/lists/linux-btrfs/msg19583.html I feel that you''re hitting a similar issue here. Before you apply the patch, please verify that you have /etc/mtab on your system (I will make a more formal patch later). Thanks, Alex. On Mon, Oct 15, 2012 at 9:21 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:> Am 15.10.2012 12:16, schrieb Miao Xie: > >> On thu, 11 Oct 2012 21:54:48 +0200, Stefan Priebe wrote: >>> >>> Am 11.10.2012 21:43, schrieb David Sterba: >>>> >>>> On Thu, Oct 11, 2012 at 09:33:54PM +0200, Stefan Priebe wrote: >>>>> >>>>> [server: /btrfs/target]# btrfs send -i /btrfs/src/\@snapshot/1 >>>>> /btrfs/src/\@snapshot/2 | btrfs receive /btrfs/target/\@snapshot/ >>>>> At subvol /btrfs/src/@snapshot/2 >>>>> At subvol 2 >>>>> ERROR: failed to open /btrfs/target/@snapshot/@snapshot/1/test.tar. No >>>>> such file or directory >>>> >>>> ^^^^^^^^^^^^^^^^^^^ >>>> >>>> I wonder if this is the ghost snapshot dir entry that Miao fixed. Did >>>> somehow get into the ''send'' stream and confused the receive side. >>>> >>>> david >>> >>> >>> i missed two facts: >>> 1.) vanilla kernel 3.6.1 >>> 2.) latest btrfs tools git (cloned at 10/10/2012) >> >> >> Sorry, I can not reproduce this problem, could you send me the detailed >> steps? > > > mhm there is nothing special. But i try to provide more information / a > small howto: > > # mount |grep btrfs > /dev/sdb on /btrfs/src type btrfs (rw) > /dev/sdc on /btrfs/target type btrfs (rw) > > # btrfs subvolume list /btrfs/target/ > # btrfs subvolume list /btrfs/src/ > ID 277 top level 5 path @snapshot/1 > ID 278 top level 5 path @snapshot/2 > ID 288 top level 5 path @snapshot/3 > > # btrfs send /btrfs/src/\@snapshot/1 | btrfs receive > /btrfs/target/\@snapshot/ > At subvol /btrfs/src/@snapshot/1 > At subvol 1 > # > > Now i was trying to send an incremental snapshot: > > # btrfs send -i /btrfs/src/\@snapshot/1 /btrfs/src/\@snapshot/2 | btrfs > receive /btrfs/target/\@snapshot/ > At subvol /btrfs/src/@snapshot/2 > At subvol 2 > ERROR: failed to open /btrfs/target/@snapshot/@snapshot/1/test.tar. No such > file or directory > # > > Greets, > > Stefan > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Am 15.10.2012 21:42, schrieb Alex Lyakas:> Is /btrfs/target/\@snapshot/ a subvolume or a directory?A simple directory.> can you pls try the patch that I posted here: > http://www.spinics.net/lists/linux-btrfs/msg19583.html > > I feel that you''re hitting a similar issue here. Before you apply the > patch, please verify that you have /etc/mtab on your system (I will > make a more formal patch later).With your patch it works FINE!! Great! Another problem i''m seeing is: # btrfs send -i /btrfs/src/\@snapshot/1 /btrfs/src/\@snapshot/2 | btrfs receive /btrfs/target/\@snapshot/ At subvol /btrfs/src/@snapshot/2 ERROR: Failed to lookup path for root 0 - No such file or directory ERROR: unable to resolve path for root 350 Then i have to wait some seconds and the same command works fine. I see the same with btrfs subvolume list PATH and it is unrelated to your patch. Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Stefan, the second issue you''re seeing was discussed here: http://www.spinics.net/lists/linux-btrfs/msg19672.html You can apply the patch I sent there meanwhile, but as Miao pointed out, I will need to make a better patch (hope will do it soon, together with this one). Thanks, Alex. On Mon, Oct 15, 2012 at 10:06 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:> Am 15.10.2012 21:42, schrieb Alex Lyakas: > >> Is /btrfs/target/\@snapshot/ a subvolume or a directory? > > A simple directory. > > >> can you pls try the patch that I posted here: >> http://www.spinics.net/lists/linux-btrfs/msg19583.html >> >> I feel that you''re hitting a similar issue here. Before you apply the >> patch, please verify that you have /etc/mtab on your system (I will >> make a more formal patch later). > > > With your patch it works FINE!! Great! > > Another problem i''m seeing is: > > # btrfs send -i /btrfs/src/\@snapshot/1 /btrfs/src/\@snapshot/2 | btrfs > receive /btrfs/target/\@snapshot/ > At subvol /btrfs/src/@snapshot/2 > ERROR: Failed to lookup path for root 0 - No such file or directory > ERROR: unable to resolve path for root 350 > > Then i have to wait some seconds and the same command works fine. I see the > same with btrfs subvolume list PATH > > and it is unrelated to your patch. > > Stefan-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Am 15.10.2012 22:14, schrieb Alex Lyakas:> Stefan, > the second issue you''re seeing was discussed here: > http://www.spinics.net/lists/linux-btrfs/msg19672.html > > You can apply the patch I sent there meanwhile, but as Miao pointed > out, I will need to make a better patch (hope will do it soon, > together with this one).ah OK thanks. So i hope we''ll see an updated btrfs-progs git repo soon ;-) Thanks! Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html