From: Marian Csontos <mcsontos@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Micky <mickylmartin@gmail.com>
Subject: Re: [linux-lvm] Very slow i/o after snapshotting
Date: Tue, 09 Jul 2013 07:01:45 +0200 [thread overview]
Message-ID: <51DB9939.7010803@redhat.com> (raw)
In-Reply-To: <CAKAA-nmORsWxeOX1O0Hnv6nFx_1nM41CUULk15biAfuderXmGg@mail.gmail.com>
On 07/09/2013 03:37 AM, Micky wrote:
> On a machine, where weekly snapshots are created for dumping raw data,
> the overall disk i/o has drastically degraded to few megabytes per
> second. It is quite random and so slow that commands freeze often.
>
> I was using chunk size of 512K and same byte size with dd.
>
> Is it quite common; I read that such freezes require a reboot. Is
> there a way to avert?
> What am I missing here?
What do you mean by weekly snapshots?
If you mean old-style snapshots not thin-ones, many snapshots with
single origin LV then how many snapshots are you keeping around?
If you have N snapshots up to (N+1)*chunksize is written for every write.
Also if this setup is used on HDDs the seektime may be relevant as well.
Old style snapshots were not meant for long term use and should be used
while snapshot is copied over to permanent location.
You may be better off using thin-snapshots. Otherwise the solution is
dumping old snapshots or moving over to tape, whatever, just do not keep
more of them.
-- Marian
>
> _______________________________________________
> 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/
>
next prev parent reply other threads:[~2013-07-09 5:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 1:37 [linux-lvm] Very slow i/o after snapshotting Micky
2013-07-09 5:01 ` Marian Csontos [this message]
2013-07-09 8:26 ` Micky
2013-07-09 9:54 ` Zdenek Kabelac
2013-07-09 11:51 ` Micky
2013-07-09 12:19 ` Marian Csontos
2013-07-09 12:43 ` Micky
2013-07-09 13:20 ` Zdenek Kabelac
2013-07-09 14:04 ` Micky
2013-07-09 14:18 ` Zdenek Kabelac
2013-07-09 14:57 ` Micky
2013-07-09 15:14 ` Zdenek Kabelac
2013-07-09 15:26 ` Micky
2013-07-09 15:26 ` Marian Csontos
2013-07-09 15:35 ` Micky
2013-07-09 15:39 ` Micky
2013-07-09 18:47 ` Zdenek Kabelac
2013-07-09 23:15 ` Micky
2013-07-09 23:29 ` Micky
2013-07-09 17:59 ` matthew patton
2013-07-09 18:42 ` Zdenek Kabelac
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=51DB9939.7010803@redhat.com \
--to=mcsontos@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=mickylmartin@gmail.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;
as well as URLs for NNTP newsgroup(s).