mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petro <petro@corp.vendio.com>
To: Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LVM, snapshots and Linux 2.4.x
Date: Wed, 16 Jul 2003 14:29:44 -0700	[thread overview]
Message-ID: <20030716212944.GB30218@corp.vendio.com> (raw)
In-Reply-To: <E19catr-0002rI-00@calista.inka.de>

On Wed, Jul 16, 2003 at 03:16:07AM +0200, Bernd Eckenfels wrote:
> In article <20030715223342.GH26404@corp.vendio.com> you wrote:
> > if I turn off HIGHIO, the lvcreate command completes successfully, but
> > the snapshot is unmountable. 
> 
> kvm was segfaulting for me with xfs if the snapsht volume gets full, but I
> think this is fixed.
> What filesystem do you had on the snapshot volume? Depending on the
> filesystem, you may need to mount it without journal replay, or with
> ignoring duplicate uuids.

    Kernel 2.4.18 segfaults when I do the lvcreate -s 
    
    Kernel 2.4.21 with the HighMem I/O fails on the lvcreate -s. 
    
    Kernel 2.4.21 without HighMem I/O fails but with High mem fails 
                  when I try to mount the snapshot. 

    Kernel 2.4.21 without high memory, and without high i/o suceeds 
                  in both creating and mounting the snapshot. 

-- 
"On two occasions, I have been asked [by members of Parliament], 'Pray, 
Mr. Babbage, if you put into the machine wrong figures, will the right 
answers come out?' I am not able to rightly apprehend the kind of confusion 
of ideas that could provoke such a question." -- Charles Babbage 

  reply	other threads:[~2003-07-16 21:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 22:33 Petro
2003-07-16  1:16 ` Bernd Eckenfels
2003-07-16 21:29   ` Petro [this message]
2003-07-18 23:20 ` Kernel Oops--2.4.18 Petro

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=20030716212944.GB30218@corp.vendio.com \
    --to=petro@corp.vendio.com \
    --cc=ecki@calista.eckenfels.6bone.ka-ip.net \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®