From owner-freebsd-questions Tue Mar 18 12:16: 3 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5C0F37B401 for ; Tue, 18 Mar 2003 12:16:01 -0800 (PST) Received: from mx1.clickcom.com (mx2.clickcom.com [209.198.22.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DB0A43F75 for ; Tue, 18 Mar 2003 12:16:01 -0800 (PST) (envelope-from jsmailing@clickcom.com) Received: from aesop (calefaction.clickcom.com [209.198.22.19]) by mx1.clickcom.com (email) with ESMTP id 9B7E38D6DB for ; Tue, 18 Mar 2003 15:16:00 -0500 (EST) From: "John Straiton" To: Subject: Question about background FSCK Date: Tue, 18 Mar 2003 15:11:09 -0500 Message-ID: <00a001c2ed8a$8758d1d0$1916c60a@win2k.clickcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG While I appreciate the background fsck's that 5.0 provides, it appears that there are problems with writing to a drive that is still under the scrutiny of a fsck (tell me if I'm wrong). 'Fer instance, today I brought up a machine that has a 119GB /home partition and then tried to FTP to it. The FTP got to 32kB and hung.... Attempts to reconnect resulted in connections but the inability to STOR. When I do a top, I can see PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 450 root -4 4 632K 376K bufwai 0:01 0.00% 0.00% fsck_ufs So I guess it's still running. Here's the question: I need a solution so that this machine is immediately available when it starts taking connections into inetd. What options have I on this problem? Is there an override to the write-deny (and if so, what risks inclusive to it) or a way to keep the machine from coming up until the fsck is done? (ala 4.X style..) I have a machine at home where the boot drive is 160GB that would benefit from the answer as well. If it has to fsck, I have to currently take it to single-user because if I let it background fsck, the damn thing will hang (still process packets through the NATd but you can't type at all or login for example) a few moments after the login: prompt shows up. Thanks, John Straiton jks@clickcom.com Clickcom, Inc 704-365-9970x101 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message