From owner-freebsd-chat Tue Feb 26 18:26:38 2002 Delivered-To: freebsd-chat@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 2561837B400 for ; Tue, 26 Feb 2002 18:26:36 -0800 (PST) Received: from hades.hell.gr (patr530-a221.otenet.gr [212.205.215.221]) by mailsrv.otenet.gr (8.12.2/8.12.2) with ESMTP id g1R2QRI8004017 for ; Wed, 27 Feb 2002 04:26:28 +0200 (EET) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id g1R2QRl17362 for chat@freebsd.org; Wed, 27 Feb 2002 04:26:27 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Wed, 27 Feb 2002 04:26:26 +0200 From: Giorgos Keramidas To: chat@freebsd.org Subject: linux and newfs -b 16384 -f 2048 Message-ID: <20020227022626.GA17146@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org A recent post in one of the Greek Linux user lists, revealed that linux UFS support lacks a 16384 block size in the UFS filesystem support. The user who asked thought that it was a bug of the linux kernel, and I pointed to Sheldon's post of benchmarks/tests in -arch. It seems that the linux kernel lacks a 16384 block size: > in my kernel messages: > ufs_read_super: fs_bsize 16384 != {4096, 8192, 32768} > ufs_read_super: bad magic number Adding the block size, and checking that the fragment size of 4096 is also on the list of fragment sizes solved his problems :-))) Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message