linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: siranee.ja@tpc.co.th
To: "Chris Murphy" <lists@colorremedies.com>
Cc: "Chris Murphy" <lists@colorremedies.com>,
	"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
	voravat@tpcorp.co.th
Subject: Re: btrfs issue with mariadb incremental backup
Date: Thu, 10 Aug 2017 09:03:15 +0700 (ICT)	[thread overview]
Message-ID: <2136.49.228.125.166.1502330595.squirrel@mail> (raw)
In-Reply-To: <CAJCQCtTpE26mxLq7ufUxCin37sajcXhnM3QsgjXjVd8x_Pw9PA@mail.gmail.com>

I'll test and response the result to you soon.

I have another question about the combination within Host lxd ubuntu and lxd
container centos

Host Machine X (16.04.3 LTS with lxd 2.0.10 and btrfs-progs v4.4
 kernel 4.4 ) set 1 lvm raw partitions and format to btrfs filesystem (on host)
Partition A  mount to /opt/partA

Container A (CentOS Linux release 7.3.1611 (Core) )  is in Host Machine X
mount /opt/partA to /var/lib/mariadb in container A

Container A making local readonly snapshot everyday

The Options are (online "btrfs send ||ssh btrfs receive" or batch "btrfs send >
file.btrfs" and scp from local to remote then "btrfs receive -f file.btrfs")
1. use btrfs send from Host Machine X to Host Machine Y
2. use btrfs send from Container A to Host Machine Y
3. use btrfs send from Container A to Container B
4. use btrfs send incremental from Host Machine X to Host Machine Y
5. use btrfs send incremental from Container A to Host Machine Y
6. use btrfs send incremental from Container A to Container B


Host Machine Y (16.04.3 LTS with lxd 2.0.10 and btrfs-progs v4.4
 kernel 4.4 ) set 1 lvm raw partitions and format to btrfs filesystem (on host)
Partition B  mount to /opt/partB

Container B (CentOS Linux release 7.3.1611 (Core) ) is in Host Machine Y
mount /opt/partB to /var/lib/mariadb in container B

The Options are (online "btrfs send ||ssh btrfs receive" or batch "btrfs send >
file.btrfs" and scp from local to remote then "btrfs receive -f file.btrfs")

1. use btrfs receive from Host Machine X to Host Machine Y
2. use btrfs receive from Container A to Host Machine Y
3. use btrfs receive from Container A to Container B
4. use btrfs receive incremental from Host Machine X to Host Machine Y
5. use btrfs receive incremental from Container A to Host Machine Y
6. use btrfs receive incremental from Container A to Container B

Could you please suggest me what is the combination that should work properly with
btrfs send and receive?

I plan to setup 2 Site (Production Site and DR site) each site has 1 box (Host
Machine X and Y) and want to test btrfs to send incremental.

Best Regards,

Siranee Jarwachirakul.


> On Wed, Aug 9, 2017 at 12:36 AM,  <siranee.ja@tpc.co.th> wrote:
>
>>   488  btrfs sub snap mysql_201707230830 mysql
>>   489  systemctl start mariadb
>>   490  btrfs sub list .
>>   491  cat /var/log/mariadb/mariadb.log
>
> OK so mysql_201707230830 once on machine B is inconsistent somehow. So
> the questions I have are:
>
> Is mysql_201707230830 on machine A really identical to
> mysql_201707230830 on machine B? You can do an rsync -anc (double
> check those options) which should independently check whether those
> two subvolumes are in fact identical. The -n is a no op, which doesn't
> really matter much because as read only subvolumes any attempt to sync
> will just result in noisy messages. The -c causes rsync to do its own
> checksum verification on both sides.
>
> If the subvolumes are different, we need to find out why.
>
> If the subvolumes are the same, then I wonder if you can reproduce the
> mariadb complaint on machine A merely by making a rw snapshot of
> mysql_201707230830 and trying to start it. If so, then it's not a send
> receive problem, it sounds like the snapshot itself is inconsistent,
> maybe mariadb hasn't actually completely closed out the database at
> the time the read only snapshot was taken? I'm not sure.
>
> If the subvolumes are different, I'm going to recommend updating at
> least the btrfs-progs because 4.4 is kinda old at this point. The
> kernel code is what's mainly responsible for the send stream, and the
> user space code is mainly responsible for receiving. And I don't off
> hand know or want to look up all the send receive changes between 4.4
> and 4.12 to speculate on whether this is has already been fixed.
>
> What's the kernel version?
>
> --
> Chris Murphy
>



  reply	other threads:[~2017-08-10  2:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09  4:32 btrfs issue with mariadb incremental backup siranee.ja
2017-08-09  5:46 ` Chris Murphy
2017-08-09  6:36   ` siranee.ja
2017-08-09 17:59     ` Chris Murphy
2017-08-10  2:03       ` siranee.ja [this message]
2017-08-11  4:40       ` siranee.ja
2017-08-11  6:00         ` siranee.ja
2017-08-11 15:35           ` Chris Murphy
2017-08-12  2:38             ` siranee.ja
2017-08-12  4:31               ` Chris Murphy
2017-08-12  5:08                 ` siranee.ja
2017-08-12 21:34                   ` Chris Murphy
2017-08-12 22:41                     ` Janos Toth F.
2017-08-12 23:07                       ` Chris Murphy
2017-08-12 22:49                     ` Hugo Mills
2017-08-12 23:14                       ` Chris Murphy
2017-08-13  2:20                     ` siranee.ja
2017-08-13  2:59                       ` Chris Murphy
2017-08-13  3:40                         ` siranee.ja
2017-08-13  4:34                           ` Chris Murphy
2017-08-13 10:49                             ` siranee.ja
2017-08-13 19:31                               ` Chris Murphy
2017-08-13  6:20                           ` A L
2017-08-13 10:52                             ` siranee.ja
2017-08-13 12:51                               ` A L
2017-08-13 14:00                                 ` siranee.ja
2017-08-13 21:31                                   ` A L
2017-08-14  1:57                                     ` siranee.ja
2017-08-13 19:50                               ` Chris Murphy
2017-08-14  2:04                                 ` siranee.ja
2017-08-11 15:06         ` Chris Murphy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2136.49.228.125.166.1502330595.squirrel@mail \
    --to=siranee.ja@tpc.co.th \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=voravat@tpcorp.co.th \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).