From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] q: BLOCK_SIZE
Date: Wed, 28 Feb 2001 12:38:37 +0000 [thread overview]
Message-ID: <20010228123837.H4361@srv.sistina.com> (raw)
In-Reply-To: <200102272025.f1RKPg727605@webber.adilger.net>; from adilger@turbolinux.com on Tue, Feb 27, 2001 at 01:25:42PM -0700
On Tue, Feb 27, 2001 at 01:25:42PM -0700, Andreas Dilger wrote:
> Michael writes:
> > Little question that I already posted here a long time ago.
> > What drawbacks can suffer if one changes BLOCK_SIZE in
> > include/linux/lvm.h from 1024 (or 4096 on S/390) to 512?
>
> On S/390 it would appear that the DASD block devices have a 4096
> byte sector size. However, on most other systems there is only
> a 512 byte sector size, so I don't see any reason there would
> be problems with BLOCK_SIZE = 512.
>
> I think Andrea Arcangeli was complaining about this as well.
>
> > This is about using lvm with rawio -- on 2.2, rawio wan't
> > work with i/o size be not a multiple of blocksize, while
> > on 2.4 it works. Or at least this was on Dec-2000.
> > Oh yes, this is about 2.2 kernel and lvm-0.9.
>
> If it works for you at 512 bytes, leave it then.
Yep.
> Maybe Heinz
> will let us know why it is set to 1024 bytes.
It is basically an approach to support larger LV sizes than 2T :)
Because the Linux kernel supports 2^32 blocks per block minor up to version 2.4,
this is one approach (with tradeoffs for sure) to raise that limit.
With the 4k block size on S/390 DASD devices this means 16T per LV!
Sure: we won't have a satisfying solution before Linux 2.5.
>
> Cheers, Andreas
> --
> Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
> \ would they cancel out, leaving him still hungry?"
> http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-02-28 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 18:36 [linux-lvm] q: BLOCK_SIZE Michael Tokarev
2001-02-27 20:25 ` Andreas Dilger
2001-02-27 21:29 ` Joe Thornber
2001-02-28 12:38 ` Heinz J. Mauelshagen [this message]
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=20010228123837.H4361@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;
as well as URLs for NNTP newsgroup(s).