All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: dm-devel@redhat.com, lvm-devel@redhat.com
Subject: rebased snapshot-merge patches
Date: Mon, 31 Aug 2009 18:08:35 -0400	[thread overview]
Message-ID: <20090831220834.GA15126@redhat.com> (raw)

I've updated both the DM and LVM2 snapshot-merge patches to the latest
upstream Linux and LVM2.

All patches (both Linux and LVM2) have been tested to pass the LVM2
testsuite.  There is more work to be done on these patches but I wanted
to make others aware of them sooner rather than later.

The basis for the DM snapshot-merge patches is Linux 2.6.31-rc8 + the
remaining DM fixes that Alasdair should be pushing to Linus this week:
http://people.redhat.com/msnitzer/patches/dm-2.6.31-rc-fixes/

The DM snapshot-merge patches are here:
http://people.redhat.com/msnitzer/patches/snapshot-merge/kernel/2.6.31/

The LVM2 snapshot-merge patches are here:
http://people.redhat.com/msnitzer/patches/snapshot-merge/lvm2/LVM2-2.02.52-cvs/

I threw some real work at snapshot-merge by taking a snap _before_
formatting a 100G LV with ext3.  Then merged all the exceptions.  One
observation is that the merge process is _quite_ slow in comparison to
how long it took to format the LV (with associated snapshot exception
copy-out).  Will need to look at this further shortly... it's likely a
function of using minimal system resources during the merge via kcopyd;
whereas the ext3 format puts excessive pressure on the system's page
cache to queue work for mkfs's immediate writeback.

# lvcreate -n testlv -L 100G test
# lvcreate -n testlv_snap -s -L 20G test/testlv
# lvs
  LV          VG   Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  testlv      test owi-a- 100.00G
  testlv_snap test swi-a-  20.00G testlv   0.00
# mkfs.ext3 /dev/test/testlv
# lvs
  LV          VG   Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  testlv      test owi-a- 100.00G
  testlv_snap test swi-a-  20.00G testlv   8.52
# lvconvert -M test/testlv_snap
  Merging of volume testlv_snap started.
  testlv: Merged: 8.5%
  testlv: Merged: 8.4%
  testlv: Merged: 8.4%
  testlv: Merged: 8.3%
  ...
  testlv: Merged: 7.2%
  ...
  testlv: Merged: 0.0%
  testlv: Merged: 0.0%
  testlv: Merged: 0.0%
  Merge into logical volume testlv finished.
  Logical volume "snapshot1" successfully removed

--
lvm-devel mailing list
lvm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/lvm-devel

WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: rebased snapshot-merge patches
Date: Mon, 31 Aug 2009 18:08:35 -0400	[thread overview]
Message-ID: <20090831220834.GA15126@redhat.com> (raw)

I've updated both the DM and LVM2 snapshot-merge patches to the latest
upstream Linux and LVM2.

All patches (both Linux and LVM2) have been tested to pass the LVM2
testsuite.  There is more work to be done on these patches but I wanted
to make others aware of them sooner rather than later.

The basis for the DM snapshot-merge patches is Linux 2.6.31-rc8 + the
remaining DM fixes that Alasdair should be pushing to Linus this week:
http://people.redhat.com/msnitzer/patches/dm-2.6.31-rc-fixes/

The DM snapshot-merge patches are here:
http://people.redhat.com/msnitzer/patches/snapshot-merge/kernel/2.6.31/

The LVM2 snapshot-merge patches are here:
http://people.redhat.com/msnitzer/patches/snapshot-merge/lvm2/LVM2-2.02.52-cvs/

I threw some real work at snapshot-merge by taking a snap _before_
formatting a 100G LV with ext3.  Then merged all the exceptions.  One
observation is that the merge process is _quite_ slow in comparison to
how long it took to format the LV (with associated snapshot exception
copy-out).  Will need to look at this further shortly... it's likely a
function of using minimal system resources during the merge via kcopyd;
whereas the ext3 format puts excessive pressure on the system's page
cache to queue work for mkfs's immediate writeback.

# lvcreate -n testlv -L 100G test
# lvcreate -n testlv_snap -s -L 20G test/testlv
# lvs
  LV          VG   Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  testlv      test owi-a- 100.00G
  testlv_snap test swi-a-  20.00G testlv   0.00
# mkfs.ext3 /dev/test/testlv
# lvs
  LV          VG   Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  testlv      test owi-a- 100.00G
  testlv_snap test swi-a-  20.00G testlv   8.52
# lvconvert -M test/testlv_snap
  Merging of volume testlv_snap started.
  testlv: Merged: 8.5%
  testlv: Merged: 8.4%
  testlv: Merged: 8.4%
  testlv: Merged: 8.3%
  ...
  testlv: Merged: 7.2%
  ...
  testlv: Merged: 0.0%
  testlv: Merged: 0.0%
  testlv: Merged: 0.0%
  Merge into logical volume testlv finished.
  Logical volume "snapshot1" successfully removed



             reply	other threads:[~2009-08-31 22:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31 22:08 Mike Snitzer [this message]
2009-08-31 22:08 ` rebased snapshot-merge patches Mike Snitzer
2009-09-08 14:17 ` [dm-devel] " Mikulas Patocka
2009-09-08 14:17   ` Mikulas Patocka
2009-09-11  6:51   ` Mike Snitzer
2009-09-11  6:51     ` Mike Snitzer
2009-09-12  6:56     ` Mike Snitzer
2009-09-12  6:56       ` Mike Snitzer
2009-09-12  7:54       ` Mikulas Patocka
2009-09-12  7:54         ` Mikulas Patocka

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=20090831220834.GA15126@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=lvm-devel@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.