Message-ID: <20020620204303.34013.qmail@web13104.mail.yahoo.com>
Date: Thu, 20 Jun 2002 13:43:03 -0700 (PDT)
From: Ravi Wijayaratne <ravi_wija@yahoo.com>
Subject: Re: Case of the dissapearing files!
To: Steve Lord <lord@sgi.com>
Cc: linux-xfs@oss.sgi.com
In-Reply-To: <1024605119.5039.102.camel@jen.americas.sgi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

Hi Steve,

kernel version is 2.4.18-xfs-1.1
If I create a diretory in the "/" it remains after
a reboot and gets to the inode. I verified the inode
info with xfs_db.

thanks
Ravi
--- Steve Lord <lord@sgi.com> wrote:
> 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


=====
------------------------------
Ravi Wijayaratne

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com