From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay2.corp.sgi.com [137.38.102.29]) by oss.sgi.com (Postfix) with ESMTP id F07487F3F for ; Sun, 27 Apr 2014 11:07:06 -0500 (CDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay2.corp.sgi.com (Postfix) with ESMTP id D20C5304032 for ; Sun, 27 Apr 2014 09:07:03 -0700 (PDT) Received: from sandeen.net (sandeen.net [63.231.237.45]) by cuda.sgi.com with ESMTP id Bh4cipuOY13mHBB2 for ; Sun, 27 Apr 2014 09:07:01 -0700 (PDT) Message-ID: <535D2B26.4010702@sandeen.net> Date: Sun, 27 Apr 2014 11:07:02 -0500 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: How to find the inodes in XFS References: <5359912A.70603@sandeen.net> <535AE19D.8@sandeen.net> In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Felipe Monteiro de Carvalho Cc: xfs@oss.sgi.com On 4/27/14, 10:53 AM, Felipe Monteiro de Carvalho wrote: > Maybe my flaw is that to get the disk position I simply multiply the > block number by the size of a block ... I tryed to use > XFS_FSB_TO_DADDR instead but it gives 64 for block nr 8, which doesn't > make much sense, I'd expect 0x8000 if you have 4k blocks, filesystem block #8 is at 32k, or 64 512-byte "daddrs" so that is correct. A "DADDR" is in 512-byte units. -Eric _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs