From: "Donald Murray P.Eng." <donald.murray@pason.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM snapshot sizes.
Date: Mon, 7 Jun 2004 12:34:34 -0600 [thread overview]
Message-ID: <20040607123434.2256e2ab.donald.murray@pason.com> (raw)
In-Reply-To: <40C4B1E5.8040801@staff.theuseful.com>
Is your MySQL slave logging to the database partition? Replication
binary logs can grow pretty quickly, which might be the reason your
snapshot overflows.
You could try making your snapshot volumes larger.
On Mon, 07 Jun 2004 14:20:21 -0400
Yaroslav Klyukin <yklyukin@staff.theuseful.com> wrote:
>
> I have created an LVM logical volume of the size arount 60G and
> formatted it with reiserfs. After that I put MySQL database onto this
> partition and made it a replicating slave.
> Using this configuration I took several LVM snapshots, 1G each.
> It did not take long for these snapshots to overflow.
>
> So here is the question:
> Why would it take so fast to overflow an LVM snapshot?
> In other words, what are the parameters, which affect snapshot fillups?
> Is it possible, that journaling filesystem can contribute to the size of
> changing data on the logical volume, and would LVM2 be more efficient?
>
> Thank you!
>
> --
> Systems Administrator, NiuTech.
> Cellular: (561) 843-1552
> AIM: infiniteparticle
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
------------------------------------------
Donald Murray, P.Eng.
Senior Software Engineer
Pason Systems Corp.
Direct: (403) 301-3473
prev parent reply other threads:[~2004-06-07 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 18:20 [linux-lvm] LVM snapshot sizes Yaroslav Klyukin
2004-06-07 18:34 ` Donald Murray P.Eng. [this message]
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=20040607123434.2256e2ab.donald.murray@pason.com \
--to=donald.murray@pason.com \
--cc=linux-lvm@redhat.com \
/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