oh jeez - sorry for the noise. Wrong list.
On Fri, Apr 3, 2015 at 11:17 AM, G. Richard Bellamy
wrote:
> I've just noticed that I'm having issues with finding files using
> "locate" when those files are on btrfs subvolume mounts.
>
> The issue is that updatedb cannot discern the difference between
On Fri, Apr 03, 2015 at 12:27:07PM +0200, Kashyap Chamarthy wrote:
> On Fri, Apr 03, 2015 at 10:13:38AM +0200, Kashyap Chamarthy wrote:
> > On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote:
> > > Migration without --p2p works just fine, ie. the below works:
> > >
> > >
> > >
I've just noticed that I'm having issues with finding files using
"locate" when those files are on btrfs subvolume mounts.
The issue is that updatedb cannot discern the difference between a
btrfs bind mount and btrfs subvolume [1]. This generally means that if
you're using btrfs subvolume mounts a
On Fri, Apr 03, 2015 at 10:13:38AM +0200, Kashyap Chamarthy wrote:
> On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote:
> > Migration without --p2p works just fine, ie. the below works:
> >
> >
> > $ virsh migrate --verbose --copy-storage-all \
> > --live cvm1 qemu+ssh
On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote:
> Migration without --p2p works just fine, ie. the below works:
>
>
> $ virsh migrate --verbose --copy-storage-all \
> --live cvm1 qemu+ssh://kashyapc@devstack3/system
> Migration: [100 %]
>
[. . .]
>
> (2) Per
Migration without --p2p works just fine, ie. the below works:
$ virsh migrate --verbose --copy-storage-all \
--live cvm1 qemu+ssh://kashyapc@devstack3/system
Migration: [100 %]
Result:
- On the source host, the guest is shut off
- On the destination host, the
