All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] snapshot with 2.6.5 kernel
Date: Tue, 11 May 2004 13:13:22 +0200	[thread overview]
Message-ID: <20040511111322.GC31390@redhat.com> (raw)
In-Reply-To: <20040503064205.GB1230@synapse.neuralscape.com>

On Sun, May 02, 2004 at 11:42:05PM -0700, Karen Shaeffer wrote:
> 
> Hello,
> 
> I am running a patched 2.6.5 kernel and using lvm2. Everything
> looks ok, but the snapshot may be having problems. Else I just
> may be ignorant about how to use the snapshot.
> 
> Here is what I am doing on a generic X86 server. I create a logical
> volume group out of a number of PEs that are properly configured. Then I
> create a logical volume. Then I start to dump a very large tar file
> into the logical volume. As this tar file is inflating the files into
> the logical volume, I then simultaneously create a snapshot volume of
> the recently created logical volume. The very large tar archive that
> was in the process of inflating its contents continues for a while,
> but finally just crashes and hangs at some point.
> 
> Am I missunderstanding how to use snapshot here? Or is this just
> severly broken software? Any advise is appreciated.


You should be able to create a snapshot fine in ythat situation, even though
the creation will happen slow under load.

Can you repeat the case ?
Do you have an oops ? If so, please provide the ksymoops output
for further analysis of the problem.

> 
> Thanks,
> Karen
> -- 
>  Karen Shaeffer
>  Neuralscape, Palo Alto, Ca. 94306
>  shaeffer@neuralscape.com  http://www.neuralscape.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/

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Red Hat GmbH
Consulting Development Engineer                   Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2004-05-11 11:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03  6:42 [linux-lvm] snapshot with 2.6.5 kernel Karen Shaeffer
2004-05-11 11:13 ` Heinz Mauelshagen [this message]
2004-05-16 21:45   ` Karen Shaeffer

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=20040511111322.GC31390@redhat.com \
    --to=mauelshagen@redhat.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.