Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f5SEqFE31248 for linux-xfs-outgoing; Thu, 28 Jun 2001 07:52:15 -0700 Received: from d12lmsgate-2.de.ibm.com (d12lmsgate-2.de.ibm.com [195.212.91.200]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f5SEqDV31245 for ; Thu, 28 Jun 2001 07:52:13 -0700 Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22]) by d12lmsgate-2.de.ibm.com (1.0.0) with ESMTP id QAA237006; Thu, 28 Jun 2001 16:52:00 +0200 Received: from d12ml014.de.ibm.com (d12ml014_cs0 [9.165.223.55]) by d12relay01.de.ibm.com (8.11.1m3/NCO v4.96) with ESMTP id f5SEpsf128340; Thu, 28 Jun 2001 16:51:54 +0200 Subject: Re: Contraint to Blksize 512? To: Steve Lord Cc: linux-xfs@oss.sgi.com X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Holger Smolinski" Date: Thu, 28 Jun 2001 16:49:13 +0200 X-MIMETrack: Serialize by Router on D12ML014/12/M/IBM(Release 5.0.6 |December 14, 2000) at 28/06/2001 16:49:28 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii 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? >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. For sure we would have incompatible layouts between XFS(512) and XFS(4k). I'd imagine sth like replacing any 512 in the XFS code by blksize(device) or blksize(xfs-type) rsp. Do you see any design obstacles in doing so? Gruesse / Regards Dr. Holger Smolinski