From: Mike Fedyk <mfedyk@matchmail.com>
To: Hans Reiser <reiser@namesys.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Anish Srivastava <anish@bidorbuyindia.com>,
linux-kernel@vger.kernel.org, edward@thebsh.namesys.com
Subject: Re: File BlockSize
Date: Mon, 18 Feb 2002 13:14:53 -0800 [thread overview]
Message-ID: <20020218211453.GA20336@matchmail.com> (raw)
In-Reply-To: <002e01c1b397$1a26d270$3c00a8c0@baazee.com> <20020212075203.GF767@holomorphy.com> <3C6E08FB.7030308@namesys.com>
In-Reply-To: <3C6E08FB.7030308@namesys.com>
On Sat, Feb 16, 2002 at 10:23:39AM +0300, Hans Reiser wrote:
> William Lee Irwin III wrote:
>
> >On Tue, Feb 12, 2002 at 01:00:07PM +0530, Anish Srivastava wrote:
> >
> >>Hi!!
> >>Is there any way I can have 8K block sizes in ext2, reiserfs or ext3.
> >>I am trying to install Oracle on Linux with 8K DB_Block_size.
> >>But it gives me a Block size mismatch saying that the File BlockSize is
> >>only
> >>4K
> >>Maybe, there is a kernel patch available which enables Linux to create 8K
> >>file blocks.
> >>Thanks in anticipation....
> >>
> >
> >Unfortunately filesystem block sizes larger than PAGE_SIZE are unsupported.
> >I wish they were, though.
I believe that is _page cache_ size instead of PAGE_SIZE. Though,
page_cache_size is based on PAGE_SIZE...
> >
> I should be more precise, on alpha you can do it with reiserfs.
>
> Hans
And ext2 and ext3 and ...
next prev parent reply other threads:[~2002-02-18 21:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 7:30 File BlockSize Anish Srivastava
2002-02-12 7:52 ` William Lee Irwin III
2002-02-12 7:55 ` William Lee Irwin III
2002-02-16 7:23 ` Hans Reiser
2002-02-18 21:14 ` Mike Fedyk [this message]
2002-02-12 14:37 ` Alan Cox
2002-02-12 20:57 ` William Lee Irwin III
2002-02-12 22:00 ` Rik van Riel
2002-02-12 22:25 ` Alan Cox
2002-02-12 22:16 ` Rik van Riel
2002-02-13 0:36 ` Daniel Phillips
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=20020218211453.GA20336@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=anish@bidorbuyindia.com \
--cc=edward@thebsh.namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=wli@holomorphy.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