From owner-freebsd-current Fri Feb 28 11:40:24 2003 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 3C83437B401 for ; Fri, 28 Feb 2003 11:40:23 -0800 (PST) Received: from c001.snv.cp.net (h000.c001.snv.cp.net [209.228.32.114]) by mx1.FreeBSD.org (Postfix) with SMTP id 1B71044008 for ; Fri, 28 Feb 2003 11:40:14 -0800 (PST) (envelope-from kutulu@kutulu.org) Received: (cpmta 4534 invoked from network); 28 Feb 2003 11:40:13 -0800 Received: from 64.212.128.3 (HELO kutulu) by smtp.register-admin.com (209.228.32.114) with SMTP; 28 Feb 2003 11:40:13 -0800 X-Sent: 28 Feb 2003 19:40:13 GMT Message-ID: <00ce01c2df61$364fb3d0$29330f0a@lcapps.educate.com> From: "Mike Edenfield" To: "James Satterfield" , References: <3E5FB785.6000704@uberduper.com> Subject: Re: SCHED_ULE oddities Date: Fri, 28 Feb 2003 14:40:07 -0500 Organization: KutuluWare Software Services MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: "James Satterfield" Sent: Friday, February 28, 2003 2:24 PM > First off, I found SCHED_ULE to be very slow. More importantly, the two > times that I rebooted while running it, shutdown failed to sync the > disks. On the second reboot, I had just installed a new kernel. The > results of this were ugly. /boot/kernel and /boot/kernel.old > disappeared. I've since gotten the box back up and running using a > SCHED_4BSD kernel and I no longer have these sync problems. I haven't been able to pin it down to SCHED_ULE, but three times since I switched schedulers, I have noticed that doing a clean "shutdown -r" after a buildworld resulted in the filesystems failing to unmount. A background fsck was forced on all of them at reboot, but no problems were found and I haven't noticed any data loss. I just switched back to SCHED_4BSD, to see if it continues, but it was only once every 3 or 4 reboots. --Mike Edenfield To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message