Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 9 Mar 2014 17:35:21 +0100
From:      Polytropon <freebsd@edvax.de>
To:        "John L. Templer" <green_tiger@comcast.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Unlistable, Undeletable File in old-jailed clientmqueue folder
Message-ID:  <20140309173521.6bc5e31a.freebsd@edvax.de>
In-Reply-To: <1394347240.5144.8.camel@muffin.localdomain>
References:  <531B18B1.6030305@dracyrys.com> <531B4290.8090903@gmail.com> <1394347240.5144.8.camel@muffin.localdomain>

next in thread | previous in thread | raw e-mail | index | archive | help
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, ...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140309173521.6bc5e31a.freebsd>