All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Valentan <rov_200603@solid-soft.at>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvcreate - race condition creating snapshots
Date: Sat, 10 Jun 2006 19:31:37 +0200	[thread overview]
Message-ID: <448B01F9.604@solid-soft.at> (raw)

I think, there is a race condition in lvcreate while
makeing a new snapshot.

System: Tyan with 2 Opteron 246
        xen 3.0.2-3
        linux 2.6.16.13
        lvm 2.02.07
        3ware-Raid 9550 Raid5

Under xen i was unable to create a snapshot, I got
always "LV system/snap in use: not deactivating".
Without xen, i got occasionally a snapshot.


After i make a "dirty hack":
------ begin ----------
*** old/lvcreate.c      2006-06-10 19:22:37.000000000 +0200
--- lvcreate.c  2006-06-10 19:23:04.000000000 +0200
***************
*** 776,781 ****
--- 776,787 ----
                /* Reset permission after zeroing */
                if (!(lp->permission & LVM_WRITE))
                        lv->status &= ~LVM_WRITE;
+
+                 { struct timeval tv ;
+                   tv.tv_sec=10;
+                   tv.tv_usec=0;
+                   select(2, 0, 0, 0, &tv);
+                 }
                if (!deactivate_lv(cmd, lv)) {
                        log_err("Couldn't deactivate new snapshot.");
                        return 0;
------ end ---------

i got always a snapshot (on all 3 systems!). I think, there is an
other thread which is creating the new lv, and it will take longer as
the lvcreate will "think". I have to less knowledge to make a patch,
which is waiting for the correct event (creating lv complete).

-- 
regards
Robert Valentan

             reply	other threads:[~2006-06-10 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-10 17:31 Robert Valentan [this message]
2006-06-11  7:53 ` [linux-lvm] lvcreate - race condition creating snapshots Nate Carlson

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=448B01F9.604@solid-soft.at \
    --to=rov_200603@solid-soft.at \
    --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.