From owner-freebsd-current@FreeBSD.ORG Fri Jul 15 09:25:34 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97AF816A41F for ; Fri, 15 Jul 2005 09:25:34 +0000 (GMT) (envelope-from john@basicnets.co.uk) Received: from mail.basicnets.co.uk (huber1-3.dsl.easynet.co.uk [217.204.222.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDC8743D48 for ; Fri, 15 Jul 2005 09:25:28 +0000 (GMT) (envelope-from john@basicnets.co.uk) Received: from [195.224.14.210] (helo=UKBIM1117) by mail.basicnets.co.uk with esmtp (Exim 4.51 (FreeBSD)) id 1DtMQu-000Ays-Ta for freebsd-current@freebsd.org; Fri, 15 Jul 2005 10:24:40 +0100 From: "John Sullivan" To: Date: Fri, 15 Jul 2005 10:25:19 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcWI4WaVzz20e9aNQkizmFB/fvTe0AANaBNg X-Scanned-by: ClamAV X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "server19.basicnets.co.uk", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Ver=FreeBSD 5.4 In my nightly security report I get a number of "Bad file descriptors" error messages in my ports directory: Checking setuid files and devices: find: /usr/ports/mail/masqmail-devel/pkg-descr: Bad file descriptor find: /usr/ports/mail/masqmail-devel/pkg-plist: Bad file descriptor find: /usr/ports/mail/masqmail-devel/files: Bad file descriptor ... [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- Message-Id: <20050715092528.CDC8743D48@mx1.FreeBSD.org> Subject: howto for fsck on a snapshot - Bad file descriptor X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 09:25:34 -0000 Ver=FreeBSD 5.4 In my nightly security report I get a number of "Bad file descriptors" error messages in my ports directory: Checking setuid files and devices: find: /usr/ports/mail/masqmail-devel/pkg-descr: Bad file descriptor find: /usr/ports/mail/masqmail-devel/pkg-plist: Bad file descriptor find: /usr/ports/mail/masqmail-devel/files: Bad file descriptor ... I note that in section 16.13 of the FreeBSD handbook that a snapshot can be taken, repaired and replaced while the server is running. I am having trouble working out how to do this :-(. Searches on Google and the FreeBSD web site have left me with no further insight. I can mount the snapshot and run fsck against it - it corrects all of the errors but I am still left with the problems on the real partition. Does any one have a 'howto' for recovering from this situation? John Sullivan