From owner-freebsd-arch  Tue Jan 15  9:22:24 2002
Delivered-To: freebsd-arch@freebsd.org
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by hub.freebsd.org (Postfix) with ESMTP id C8CC037B405
	for <arch@FreeBSD.ORG>; Tue, 15 Jan 2002 09:22:16 -0800 (PST)
Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id EAA03708;
	Wed, 16 Jan 2002 04:14:34 +1100
Date: Wed, 16 Jan 2002 04:15:43 +1100 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender:  <bde@gamplex.bde.org>
To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>,
	Max Khon <fjoe@iclub.nsu.ru>, <arch@FreeBSD.ORG>
Subject: Re: request for review 
In-Reply-To: <200201151434.g0FEYlK72569@cwsys.cwsent.com>
Message-ID: <20020116035325.T2884-100000@gamplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG

On Tue, 15 Jan 2002, Cy Schubert - ITSD Open Systems Group wrote:

> In addition to making FreeBSD consistent with OpenBSD and Linux, as
> stated by the originator of this thread, the patch also makes FreeBSD
> consistent with Solaris and Tru64-UNIX.  I'm for it.

Please don't top post.

This patch also makes FreeBSD almost compatible with FreeBSD (versions
1, 2, 3) that is.  Old versions vn_stat() simply passed back the
va_blocksize set by VOP_GETTATTR().  This at least gave individual
filesystems a chance to set it right.  It was too bad that they mostly
set it wrong using slightly different hacks than the ones in the
-current vn_stat().  The patch under review restores the old behaviour
for non-disk character devices only.  Unfortunately, it was character
(and block) devices that had the most bogus values for va_blocksize.

> In message <19068.1011092026@critter.freebsd.dk>, Poul-Henning Kamp
> writes:
> >
> > I think it is bogus for devices other than disks to flout a
> > va_blocksize, but I am on the other hand not sure what the
> > relevant (if any) standards say.

Please don't top post.

POSIX says almost the same as the quote from www.opengroup.org in the
sources: "A file system-specific [sic] preferred I/O block size for
this object".  0 is wrong except possibly for /dev/null since it is
a very bad I/O size.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message