From: Bear Wolf <sportbear@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] new process dead after create multiple snapshot volumes
Date: Mon, 12 Sep 2005 16:42:13 +0800 [thread overview]
Message-ID: <95bbd19050912014220e457b@mail.gmail.com> (raw)
In-Reply-To: <20050912080543.GD25756@barkeeper1.linbit>
Dear Lars
I tried but not work,
the process is still hang when I trying to copy some data in source
volume or do sync command after create the 4rd snapshot volume.
should I patch the 8 and 9 of dm module?
ftp://sources.redhat.com/pub/dm/patches/2.6-unstable/2.6.12-rc2/2.6.12-rc2-udm1/
I saw that some discuss in previous mail-list
SportBear
2005/9/12, Lars Ellenberg <Lars.Ellenberg@linbit.com>:
> / 2005-09-12 10:34:15 +0800
> \ Bear Wolf:
> > Dear all
> >
> > I test snapshot function on my system.
> > when I create the first snapshot, everything works fine.
> > then I create more snapshot, everything works fine too.
> > but when I access the source volume and do sync
> > the sync command will be dead.
> >
> > and I test with a script file
> >
> > I=0
> > for I in 1 2 3 4 5 6 7 8 9
> > do
> > cp -af /etc /mnt/volume1
> > lvcreate -s -L 64 -n snaplv${I} /dev/VG01/volume1
> > sleep 1
> > done
> >
> > after create the 4th sn apshot volume, the system process hang without
> > any error message.
>
> lvcreate calls into device mapper.
> it suspends the affected targets, changes "tables", creates new targets,
> and resumes the targets again.
>
> if it fails to create the new targets, or fails to adjust the "tables",
>
> then it unfortunately aborts, leaving the existing targets in suspended
> state. I think that is a bug.
>
> to get the system working (sort of) again, you could try to
> for d in /dev/mapper/* ; do
> [[ $d == control ]] && continue
> dmsetup resume $d &
> # ^^^ important! background it!
> done
>
> background it, because if you "resume" some target that depends on some
> other target in suspended state, it will hang and wait for that other
> target to be resumed... doh.
>
> worked for me... (well, to get the system back, at least).
>
> see also dmsetup ls, dmsetup info, dmsetp table etc.
>
> cheers,
>
> --
> : Lars Ellenberg Tel +43-1-8178292-0 :
> : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
> : Schoenbrunner Str. 244, A-1120 Vienna/Europe http://www.linbit.com :
>
> _______________________________________________
> 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:[~2005-09-12 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 2:34 [linux-lvm] new process dead after create multiple snapshot volumes Bear Wolf
2005-09-12 8:05 ` Lars Ellenberg
2005-09-12 8:42 ` Bear Wolf [this message]
2005-09-17 6:27 ` Bear Wolf
2005-09-17 8:23 ` Bear Wolf
2005-09-17 8:31 ` Bear Wolf
2005-09-17 19:16 ` Lars Ellenberg
2005-09-19 1:35 ` Bear Wolf
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=95bbd19050912014220e457b@mail.gmail.com \
--to=sportbear@gmail.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;
as well as URLs for NNTP newsgroup(s).