Grozdan Nikolov (openSUSE Linux) wrote:
> I do not know what version is the latest of xfsprogs. I use my distro's
> default (2.8.11)
Ok, 2.9.4 is latest. 2.8.11 is from Aug 2006.... Perhaps the more
recent version will properly fix your fs.
From the changelog:
xfsprogs-2.8.15 (19 October 2006)
- Fix up nlink checks and repairs in phase 7 for xfs_repair.
>> using xfs_metadump to provide a filesystem image for Barry to reproduce
>> with would be helpful.
>
> I can't find xfs_metadump on my system. I only have xfsdump. Is this the same?
Nope, it's not there in your older xfsprogs.
>>> 3. run ls -lR on the dir that has problems
>>> 4. run ls -li on the director(ies) that cannot be deleted for the inode
>>> #s
>> ls -a on the dir to be sure there are no hidden dotfiles
> ls -a "MusicApps/Loops/loops/Acid Loops/Bass"
>
> . ..
Ok, no hidden files.
>
>> ls -id on the dir to see if it is inode 184549517
>
> ls -id "MusicApps/Loops/loops/Acid Loops/Bass"
So, the dir you can't delete is the one with the link count mismatch
stated by xfs_check - that's what I figured but wanted to double check.
I'd be willing to bet that the latest xfsprogs would fix this for you.
Alternately some xfs_db hackery could too, but using more recent repair
would be the best route I think.
-Eric
> 184549517 MusicApps/Loops/loops/Acid Loops/Bass
>
>> -Eric
>
|