All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems with snapshots on sparc64
Date: Mon Jun  2 10:15:02 2003	[thread overview]
Message-ID: <20030602170507.B6678@sistina.com> (raw)
In-Reply-To: <20030602131232.GB9679@wh9155.stw.uni-rostock.de>; from daniel.bayer@stud.uni-rostock.de on Mon, Jun 02, 2003 at 03:12:32PM +0200

On Mon, Jun 02, 2003 at 03:12:32PM +0200, Daniel Bayer wrote:
> Hallo
> 
> On Mon, Jun 02, 2003 at 11:39:39AM +0200, Heinz J . Mauelshagen wrote:
> > which LVM version (kernel and tools)
> 
> kernel: 1.0.5+(22/07/2002)
> tools:  1.0.4-4
> 
> > and do you have HIGHMEM configured
> > (IOW: more than 960M memory) ?
> 
> Its a 64Bit architecture. There is no need for things like HIGHMEM.
> But yes, the system has 2GB RAM.

Oh, overlooked that in your email :(

> 
> > There's flaws with Linux 2.4.20 highmem which show with snapshots :(
> 
> But this problem:
> > > Another related problem is, that "cat /proc/lvm/global" in the most
> > > cases doesn't output the usual data but some random memory. Its really
> > > odd. But if I try often enough I sometimes also get the right output
> > > (and no, I didn't calculated the probability). The other files in
> > > /proc/lvm work fine.
> 
> appears also if there are no snapshots at all. (This time I only had
> to try 2 times to get the version-string.)
> 
> Tomorrow I will have some time to update the kernel and the tools to
> the current versions.

Yes, my recommendation anyway.

> 
> 
> Daniel
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.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                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-06-02 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 19:09 [linux-lvm] Problems with snapshots on sparc64 Daniel Bayer
2003-06-02  4:50 ` Heinz J . Mauelshagen
2003-06-02  8:11   ` Daniel Bayer
2003-06-02 10:15     ` Heinz J . Mauelshagen [this message]
2003-06-03 14:38       ` Daniel Bayer
2003-06-04 10:53         ` [linux-lvm] LVM + software Raid 5 : freeze when using snapshots Serge Rossi
  -- strict thread matches above, loose matches on Subject: below --
2003-05-29  7:09 [linux-lvm] Problems with snapshots on sparc64 Daniel Bayer

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=20030602170507.B6678@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 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.