Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g5OBm4nC026339 for ; Mon, 24 Jun 2002 04:48:04 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g5OBm4rD026338 for linux-xfs-outgoing; Mon, 24 Jun 2002 04:48:04 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-linux-xfs@oss.sgi.com using -f Received: from zeus-e8.americas.sgi.com ([198.149.7.250]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g5OBlvnC026308 for ; Mon, 24 Jun 2002 04:47:57 -0700 Received: from poppy-e185.americas.sgi.com (poppy-e185.americas.sgi.com [128.162.185.207]) by zeus-e8.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id GAA28384; Mon, 24 Jun 2002 06:51:12 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id GAA33205; Mon, 24 Jun 2002 06:51:11 -0500 (CDT) Date: Mon, 24 Jun 2002 06:46:26 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: tom cc: linux-xfs@oss.sgi.com Subject: Re: question about inode count. In-Reply-To: <3D16F61F.FCAFC63B@mountainviewdata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Tom - if you look at the xfs superblock in kdb, you'll see: [0]kdb> xsb 0xc6140824 ... rootino 128 rbmino 129 rsumino 130 ... and these are: xfs_ino_t sb_rbmino; /* bitmap inode for realtime extents */ xfs_ino_t sb_rsumino; /* summary inode for rt bitmap */ However, I'm not sure offhand why these show up even if CONFIG_XFS_RT is not enabled. -Eric On Mon, 24 Jun 2002, tom wrote: > Sorry, maybe some one had asked the same question. > But I really want to figure out the phenomenon shown below. > $mount -t xfs /dev/hda6 /mnt > ## and touch a file, > $ touch /mnt/a > $ ls -i /mnt/a > 131 a > # the inode num is counted from 131, not 129(the root inode is 128), > # where are the inodes of 129 and 130?