From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] cache buffer size
Date: Wed Nov 6 07:08:01 2002 [thread overview]
Message-ID: <20021106140245.B1228@sistina.com> (raw)
In-Reply-To: <3DC85406.C03B0AA0@be.mbn.or.jp>; from nickey@be.mbn.or.jp on Wed, Nov 06, 2002 at 08:28:06AM +0900
On Wed, Nov 06, 2002 at 08:28:06AM +0900, Miwako Nakai wrote:
> Thank you, Mr.Mauelshagen
>
> JFS can not have fixed block size. But I heard from JFS group in IBM
> that on 2.5 or later it will be improved. I do not know JFS will have
> fixed block size or not. They said 'improved'.
Didn't know that as a JFS no-user :)
Fixed block sizes is a suboptimal solution for the various io
needs of a filesystem (think small metedata and large data io).
If they do io with varying blocksizes, that would explain the MD RAID5
behaviour already. No way to avoid it in your combination for now then
I guess.
>
> I think LVM(2?) will be able to handle non-consitant block size on
> 2.5 well.
Yes.
Regards,
Heinz -- The LVM Guy --
>
> "Heinz J . Mauelshagen" wrote:
> >
> > On Fri, Nov 01, 2002 at 12:07:40PM +0900, Miwako Nakai wrote:
> > > I'm using jfs on lvm/raid5 with snapshot.
> > >
> > > When I copy file, it happens frequently
> > > 'raid5: switching cache buffer size XXX -> XXX'.
> > > This message appears to syslog. It caused speed down to access disks.
> > > So, I cut this message. It's seemed ok.
> >
> > Could be filesystems with different blocksizes accessing the underlying
> > raid5 md through LVM constantly forcing the raid5 stripe cache to be flushed.
> > If that's the case, you want to put filesystems of the _same_ blocksize
> > onto all of the logical volumes allocated to the raid5 device.
> >
> > Regards,
> > Heinz -- The LVM Guy --
> >
> > >
> > > But it's still going to switch cache buffer size. I think it cost
> > > some cpu time. When switching buffer cache size, it always happen
> > > reflushing memories.
> > >
> > > I want to fix buffer size. What shall I do?
> > > I asked JFS group. But they do nothing about cache buffer.
> > >
> > > kernel 2.4.20-pre10-ac2
> > > lvm 1.0.5
> > > jfs 1.0.23
> > >
> > > --
> > > nakai@ezinc.com
> --
> nakai@ezinc.com
>
> _______________________________________________
> 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/
*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-11-06 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 21:11 [linux-lvm] cache buffer size Miwako Nakai
2002-11-05 8:15 ` Heinz J . Mauelshagen
2002-11-05 17:29 ` Miwako Nakai
2002-11-06 7:08 ` Heinz J . Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 11:17 Steve Best
2002-11-06 22:04 ` Miwako Nakai
2002-11-07 11:03 ` Heinz J . Mauelshagen
2002-11-08 2:12 ` Luca Berra
2002-11-08 8:54 ` Heinz J . Mauelshagen
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=20021106140245.B1228@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