From: Falko Zurell <falko.zurell@idmedia.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] very slow fw performance when snapshots active
Date: Thu, 18 Oct 2007 10:39:50 +0200 [thread overview]
Message-ID: <47171BD6.3090709@idmedia.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi List,
I have an actual CentOS Linux with LVM on hardware RAID1+0.
fs layout looks like this:
[root@C20-DB1-00 ~]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy%
LVOpt VG0 -wi-ao 300.00G
LVRoot VG0 -wi-ao 43.94G
LVSwap VG0 -wi-ao 23.44G
Then I create a snapshot vor VG0/LVOpt with 40 GB size.
Then I edit a 2 GB text file on /opt (XFS filesystem) with vi (just
hitting "enter" and save this minor change). This will take minutes to
finish the vi during saving.
I see the kcopyd in the process list which fills up the snapshot.
When the snapshot is off then saving the same file with the same minor
change will take only seconds.
I understand that snapshots are copy-on-write. But I can't explain why
this takes minutes for a 2 GB file which has changed only in a few bytes.
Shouldn't only the changed blocks be copied to the snapshot space? Even
if only whole PEs are copied then it shouldn't take only seconds to copy
to the snapshot.
- From the actual point of view activating snapshots on this database
machine absolutly kills performance.
Did I something wrong on that?
- --
Falko Zurell
Skype: zero_data
/i-d media AG
Ohlauer Stra�e 43
D-10999 Berlin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHFxvWsdVNK8p2VTARArgkAJ9KK9hpQBH6gxhzMQiYdZMH87Q0GwCgwOSy
w9tcXzNveVWCnTfB4EO5bKU=
=u+DI
-----END PGP SIGNATURE-----
next reply other threads:[~2007-10-18 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 8:39 Falko Zurell [this message]
2007-10-18 13:52 ` [linux-lvm] very slow fw performance when snapshots active Gabriel Barazer
-- strict thread matches above, loose matches on Subject: below --
2007-10-18 14:01 AW: " Zurell, Falko
2007-10-18 15:18 ` Gabriel Barazer
2007-10-18 16:01 ` malahal
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=47171BD6.3090709@idmedia.com \
--to=falko.zurell@idmedia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.