Unlistable, Undeletable File in old-jailed clientmqueue folder

[Gitsnik]

Thanks Tron you have solved my problem, I did not know that you could
import without mounting. After the scrub the folders did not show the 3,
they showed 2, and I could rm -rf the clientmqueue.

Thanks to everyone else who made comments and helped out.

On 10/03/2014 7:40 am, Trond Endrestøl wrote:
> 
>> drwxrwx---  2 root  wheel  3 Oct  3 21:26 clientmqueue
>                              ^
> 3 links to this directory? --+
> 
> ZFS is a bit peculiar as it records the number of links when dealing 
> with directories.
> 
> Assume for a moment that your clientmqueue directory really is empty. 
> It should then have a link count of 2; the clientmqueue link and the 
> dot link (.) inside the clientmqueue directory.
> 
> Back to reality, why are there 3 links, not two, to an otherwise empty 
> directory?
> 
> Chances are that the qfq8G32oib058119 entry has somehow been 
> transformed into a directory link pointing to dot.
> 
> This is just speculation on my part. Maybe some bad memory got written 
> to disk at some point, as ZFS assumes memory (RAM) is 100 % healthy at 
> all times.
> 
> You should make good backups of the pool's filesystems, export the 
> pool and try booting from the latest stable/9 snapshot. Try to import 
> the pool without mounting any of the filesystems (zpool import -N) and 
> run zpool scrub. If all goes well, export the pool, reboot, and import 
> the pool. Worst-case scenario is to re-create the pool and restoring 
> everything from backups.
>