Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] questions
Date: Fri, 9 Feb 2001 11:21:55 +0000	[thread overview]
Message-ID: <20010209112155.C21300@srv.sistina.com> (raw)
In-Reply-To: <20010209093404.B21158@caldera.de>; from hch@caldera.de on Fri, Feb 09, 2001 at 09:34:05AM +0100

On Fri, Feb 09, 2001 at 09:34:05AM +0100, Christoph Hellwig wrote:
> On Thu, Feb 08, 2001 at 05:05:36PM -0700, Andreas Dilger wrote:
> > Change all of the code paths in the kernel that assume block size is 512
> > bytes...
> 
> IIRC some S/390 devices already use 4K block size.

Yes. They have so called DASD drives which are 4K hard sectored.

Anyway. if you change the BLOCK_SIZE definition in lvm.h from 1 to 4k
you can build LVs larger than 2TB (or even 4TB which is the default with the
1k block size used by LVM today).
You can't go beyond PAGE_SIZE though because a whole pile of code in
the kernel doesn't support that.
That means that you could even go to 8k block size on machines supporting
that page size.
Remember: you loose comapatibility with 4k page sized systems in this case.

> 
> 	Christoph
> 
> -- 
> Of course it doesn't work. We've performed a software upgrade.
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 

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:[~2001-02-09 11:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08 19:55 [linux-lvm] questions Ragnar Kjørstad
2001-02-08 21:35 ` Heinz J. Mauelshagen
2001-02-08 22:44 ` Andreas Dilger
2001-02-08 23:30   ` Ragnar Kjørstad
2001-02-09  0:05     ` Andreas Dilger
2001-02-09  8:34       ` Christoph Hellwig
2001-02-09 11:21         ` Heinz J. Mauelshagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-05 17:08 Magosanyi Arpad
2001-11-07 19:26 ` Wolfgang Weisselberg
2001-11-08  2:23   ` Heinz J . Mauelshagen
2001-11-11 14:28     ` Wolfgang Weisselberg
2007-03-04  1:59 [linux-lvm] Questions Stuart D. Gathman
2007-03-05 11:53 ` Heinz Mauelshagen
2007-03-05 17:31   ` Stuart D. Gathman
2007-03-05 17:41   ` Stuart D. Gathman

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=20010209112155.C21300@srv.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