Unlistable, Undeletable File in old-jailed clientmqueue folder

[Polytropon]

On Sun, 09 Mar 2014 01:40:40 -0500, John L. Templer wrote:
> I dunno, since the "ls" returned the name of a file, and the "ls -la"
> returned an error about there being no such file, it sounds like there's
> a directory entry but no corresponding inode.  Perhaps an fsck is in
> order?

Probably yes. In the past, I had a similar problem with
a file system which was subject to background_fsck="YES"
and somehow kept stuck in an "unclean, but working" state.
Putting background_fsck="NO" and forcing a file system
check solved the problem.

However, my impression was that the posted problem took
place on a ZFS file system, not a UFS one, and ZFS does
not have a fsck utility.

If I'm wrong with this assumption, I highly recommend
performing a file system check on the unmounted partition,
usually from within single-user mode or from a live system
CD or DVD or USB stick. If file system corruption was the
reason, it should be gone afterwards.

Additionally, there's a way to forcedly remove directory
entries: fsdb. It will be applied on the unmounted partition.
Use ls -i to determine the inode number and navigate to the
correct directory using fsdb. Then remove the offending
entry. Write the chance, and perform a fsck right afterwards.
See "man fsdb" for details. (Again, this recipe applies to
UFS, not to ZFS.)



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...