Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g5KKUpnC009315 for ; Thu, 20 Jun 2002 13:30:51 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g5KKUpES009314 for linux-xfs-outgoing; Thu, 20 Jun 2002 13:30:51 -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 g5KKUfnC009271 for ; Thu, 20 Jun 2002 13:30:41 -0700 Received: from daisy-e185.americas.sgi.com (daisy-e185.americas.sgi.com [128.162.185.214]) by zeus-e8.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id PAA04607; Thu, 20 Jun 2002 15:33:40 -0500 (CDT) Received: from jen.americas.sgi.com (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 PAA67877; Thu, 20 Jun 2002 15:33:39 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id g5KKVxE30021; Thu, 20 Jun 2002 15:31:59 -0500 Subject: Re: Case of the dissapearing files! From: Steve Lord To: Ravi Wijayaratne Cc: linux-xfs@oss.sgi.com In-Reply-To: <20020620202550.87751.qmail@web13101.mail.yahoo.com> References: <20020620202550.87751.qmail@web13101.mail.yahoo.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.7 Date: 20 Jun 2002 15:31:59 -0500 Message-Id: <1024605119.5039.102.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Spam-Status: No, hits=-3.1 required=5.0 tests=IN_REP_TO,PLING,SIGNATURE_DELIM version=2.20 X-Spam-Level: Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 2002-06-20 at 15:25, Ravi Wijayaratne wrote: > Hi All, > > I have an xfs root file system. > > I increased the size of the inodes to 1024 by using > mkfs -i size=1024 option. After that I see some of the > newly created files in the "/" directory vanishing > when I reboot the system gracefully. However the newly > created files in subdirectories are persistent > accross > reboots. > > If I powercycle the system (ungraceful shutdown) the > newly created files in the "/" directory appears. > > I ran xfs_db to examine the inode of the root > directory. I see that when I create a file (even non > empty) the files info (inode num, name etc) does not > appear in the inodes u.sfdir2.list[x].xxxx components. > > My guess is that the file creation in the "/" > directory > gets registered in the xfs meta data logs but does not > update the incore inode and hence when the system is > shutdown does not write to the disk inodes. When the > system is abruptly shutdown xfs_repair reinstates the > files. > > When I run xfs_repair -n on the root partition it > complains about unlinked inodes. > > Furthermore /proc/slabinfo tells me that the object > size is 436 bytes for the xfs_inode slab cache. > > My questions are > > (a). What is the maximum size for xfs_inode ? 1024 too > big ? > > (b). Why is the behavior different for "/" directory. > For instance "/tmp" or "/etc" works fine and I can > create and delete files in these directories. It does sound a little like the root inode is not getting flushed during unmount. If your root directoy size is less than 4K then it is all within the inode. Is this a recent kernel? Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com