Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] snapshot with bigmem broken
Date: Fri May 16 06:08:02 2003	[thread overview]
Message-ID: <20030516125958.B24422@sistina.com> (raw)
In-Reply-To: <37885B2630DF0C4CA95EFB47B30985FB020EBD2E@exchange-1.umflint.edu>; from jlauro@umflint.edu on Wed, May 14, 2003 at 06:50:46AM -0400

On Wed, May 14, 2003 at 06:50:46AM -0400, Lauro, John wrote:
> Hello,
> 
>  
> 
> I did more testing, and it appears that snapshots in LVM will not work
> with either 4GB or or 64GB support enabled in the kernel under 2.4.20.
> This includes both LVM 1.0.7 or the latest LVM2.  
> 

That's a known issue. You are faced with a VM flaw.

I presume that it's not LVM snapshots only bacause HIGHMEM is
basically broken.

>  
> 
> Is there anyone using LVM snapshots with 64GB RAM support (or even 4GB
> RAM support, as snapshots would be good for at least our medium size
> servers if not our large ones)?  Is so, let me know the kernel version
> and LVM version you are using so that I can try it.

Probably not, because the system lifelocks on bounce buffers (which is
the sympton of the principle HIGHMEM bug).
Obviously not a lot of HIGHMEM users out there raising priorities to fix this.

> 
>  
> 
> PS: As mentioned previously, everything else in LVM seems to be ok
> with larger kernel memory models.  It's mainly just snapshots that
> appear to be broken using the latest LVMs and kernel.
> 
>  
> 

-- 

Regards,
Heinz    -- The LVM Guy --

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

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

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-05-16  6:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15  7:33 [linux-lvm] snapshot with bigmem broken Lauro, John
2003-05-16  6:08 ` Heinz J . Mauelshagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-16  7:40 Lauro, John
2003-05-20  2:43 ` Heinz J . Mauelshagen
2003-05-21 10:45 ` Andrew Rechenberg

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=20030516125958.B24422@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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