Messages in this thread | | | Date | Mon, 20 Jun 2005 17:04:59 +1000 | From | Nathan Scott <> | Subject | Re: [2.6.12] XFS: Undeletable directory |
| |
On Sun, Jun 19, 2005 at 07:04:49PM +0200, Jan De Luyck wrote: > Hello lists, > > I've had some XFS troubles today, and after cleaning up with xfs_repair and so > I'm stuck with one undeletable directory in /lost+found: > > precious:/lost+found# ls -l > total 8 > drwxrwxrwx 2 root root 8192 Jun 19 2005 4207214 > precious:/lost+found# rm -r 4207214 > rm: cannot remove directory `4207214': Directory not empty > precious:/lost+found# ls -l 4207214/ > total 0 > precious:/lost+found# > > So there's one dir 4207214 there, and i can rename it and whatever, just not > remove it. > > xfs_repair didn't solve the problem. > > Any ideas?
What does: xfs_db -r -c 'inode 4207214' -c print /dev/XXX report?
I have seen a similar thing once before, awhile back, where the directory inode was "empty" (only . and ..) and hence should've been in shortform, but other fields indicated the inode was in extent form still. Never got to the bottom of it... I'd guess there's somehow a case where the kernel XFS code can miss this transformation - not sure where/how though.
If it comes to it, you can always zero out individual inode fields for that inode in xfs_db (with -x option to enable write mode) and then xfs_repair should be able to get past it.
cheers.
-- Nathan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |