xfs
[Top] [All Lists]

RE: Bug : XFS - XSCALE "Directory Not Empty"

To: Vinesh Christopher <vineshc@xxxxxxx>
Subject: RE: Bug : XFS - XSCALE "Directory Not Empty"
From: Mike Burger <mburger@xxxxxxxxxxxxxxxxx>
Date: Wed, 10 Mar 2004 20:01:35 -0500 (EST)
Cc: "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx>
In-reply-to: <8CCBDD5583C50E4196F012E79439B45C04C9A322@atl-ms1.megatrends.com>
References: <8CCBDD5583C50E4196F012E79439B45C04C9A322@atl-ms1.megatrends.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
What does ls -al t show you?

On Wed, 10 Mar 2004, Vinesh Christopher wrote:

> Same result => rm: cannot remove directory 't' : Directory not empty
> But all the files are deleted and the directory is empty
> I tried rmdir t . It says Directory not empty
> 
> 
> -----Original Message-----
> From: Mike Burger [mailto:mburger@xxxxxxxxxxxxxxxxx] 
> Sent: Wednesday, March 10, 2004 2:31 PM
> To: Vinesh Christopher
> Cc: 'linux-xfs@xxxxxxxxxxx'
> Subject: Re: Bug : XFS - XSCALE "Directory Not Empty"
> 
> What happens if you just try "rm -rf t"?
> 
> On Wed, 10 Mar 2004, Vinesh Christopher wrote:
> 
> >  
> > Intel IQ80321 (Xscale)  Evaluation Board  
> > Running Linux 2.6.0 with -rmk2 patches
> > xfsprogs_2.6.3-1  is taken from debian
> >  
> > I did the following
> >  
> > # mkfs.xfs /dev/sda1
> > # mount /dev/sda1 /mnt
> > # cd /mnt
> > # mkdir t
> > # cp /lib/* t
> > # rm -r -f t
> > rm: cannot remove directory 't' : Directory not empty
> > #
> >  
> > But the directory is empty. Unmounted the filesystem
> > and ran xfs_repair -n /dev/sda1 which produced the following
> > output :
> >  
> > Phase 1 - find and verify superblock...
> > Phase 2 - using internal log
> >         - scan filesystem freespace and inode maps...
> >         - found root inode chunk
> > Phase 3 - for each AG...
> >         - scan (but don't clear) agi unlinked lists...
> >         - process known inodes and perform inode discovery...
> >         - agno = 0
> > size of entry #0 overflows space left in in shortform dir 131
> > would junk 2 entries
> > would have corrected entry count in directory 131 from 2 to 0
> > would have corrected directory 131 size from 30 to 8
> >         - agno = 1
> >         - agno = 2
> >         - agno = 3
> >         - agno = 4
> >         - agno = 5
> >         - agno = 6
> >         - agno = 7
> >         - process newly discovered inodes...
> > Phase 4 - check for duplicate blocks...
> >         - setting up duplicate extent list...
> >         - check for inodes claiming duplicate blocks...
> >         - agno = 0
> > entry "  libwrap.so.0.7" in shortform directory 131 references
> non-existent
> > inod
> > e 18432
> > size of entry #0 overflows space left in in shortform dir 131
> > would junk 2 entries
> > would have corrected entry count in directory 131 from 2 to 0
> > would have corrected directory 131 size from 30 to 8
> >         - agno = 1
> >         - agno = 2
> >         - agno = 3
> >         - agno = 4
> >         - agno = 5
> >         - agno = 6
> >         - agno = 7
> > No modify flag set, skipping phase 5
> > Phase 6 - check inode connectivity...
> >         - traversing filesystem starting at / ...
> >         - traversal finished ...
> >         - traversing all unattached subtrees ...
> >         - traversals finished ...
> >         - moving disconnected inodes to lost+found ...
> > disconnected inode 267, would move to lost+found
> > disconnected inode 268, would move to lost+found
> > Phase 7 - verify link counts...
> > No modify flag set, skipping filesystem flush and exiting.
> >  
> >  
> >  
> > I tried with 2.4.21 and XFS 1.3.1 patches -> same problem
> >  
> > Anybody seen this? 
> >  
> >  
> > Help!!
> >  
> >  
> >  
> > 
> > 
> > [[HTML alternate version deleted]]
> > 
> > 
> 
> 

-- 
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000

To be notified of updates to the web site, visit 
http://www.bubbanfriends.org/mailman/listinfo/site-update, or send a 
message to:

site-update-request@xxxxxxxxxxxxxxxxx

with a message of: 

subscribe


<Prev in Thread] Current Thread [Next in Thread>