From owner-freebsd-questions@FreeBSD.ORG Sun Mar 9 16:35:53 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7397FB8 for ; Sun, 9 Mar 2014 16:35:53 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 354FFC04 for ; Sun, 9 Mar 2014 16:35:52 +0000 (UTC) Received: from r56.edvax.de (port-92-195-67-138.dynamic.qsc.de [92.195.67.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 23A063CBB5; Sun, 9 Mar 2014 17:35:44 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s29GZLlj001938; Sun, 9 Mar 2014 17:35:21 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Sun, 9 Mar 2014 17:35:21 +0100 From: Polytropon To: "John L. Templer" 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> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2014 16:35:53 -0000 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, ...