Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f5SDsOl26847 for linux-xfs-outgoing; Thu, 28 Jun 2001 06:54:24 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f5SDsKV26829 for ; Thu, 28 Jun 2001 06:54:20 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id PAA447476 for ; Thu, 28 Jun 2001 15:54:17 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2201240; Thu, 28 Jun 2001 08:53:00 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA01796; Thu, 28 Jun 2001 08:53:00 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f5SDsmp15488; Thu, 28 Jun 2001 08:54:48 -0500 Message-Id: <200106281354.f5SDsmp15488@jen.americas.sgi.com> To: "Holger Smolinski" cc: linux-xfs@oss.sgi.com Subject: Re: Contraint to Blksize 512? References: Comments: In-reply-to "Holger Smolinski" message dated "Thu, 28 Jun 2001 15:37:01 +0200." Date: Thu, 28 Jun 2001 08:54:48 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hello, > I tried to use XFS with devices of sector sizes larger than 512 Byte and > failed. > Apparently there are dependencies to a fixed blocksize of 512 Byte all over > the code of XFS. > Are these contraints unavoidable by the design of XFS or could you imagine > running an XFS e.g. on a device with 4k blocksize and what needs to be done > to the code in order to do so? > > Gruesse / Regards > Dr. Holger Smolinski Yes, unfortunately XFS is built around assumptions about 512 byte block sizes. There was an internal project to clean this up which was shelved a while back, I will ask around and see if the code still exists. I think this would end up with an incompatible on disk format, given that some structures would change size, but I think that would be an acceptable solution for devices with a larger block size. I mentioned one of the aspects in email yesterday, there are some 512 byte long metadata objects which need to be separately accessible on disk. The one I forgot is the log, which is written in 512 byte chunks. Steve