From mboxrd@z Thu Jan 1 00:00:00 1970 From: Justin Piszcz Subject: Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5) Date: Tue, 23 Jan 2007 06:59:19 -0500 (EST) Message-ID: References: <45B5261B.1050104@redhat.com> <17845.13256.284461.992275@notabene.brown> <45B5ECAA.6000100@tls.msk.ru> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: <45B5ECAA.6000100@tls.msk.ru> Sender: linux-raid-owner@vger.kernel.org To: Michael Tokarev Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org, xfs@oss.sgi.com, Alan Piszcz List-Id: linux-raid.ids On Tue, 23 Jan 2007, Michael Tokarev wrote: > Justin Piszcz wrote: > [] > > Is this a bug that can or will be fixed or should I disable pre-emption on > > critical and/or server machines? > > Disabling pre-emption on critical and/or server machines seems to be a good > idea in the first place. IMHO anyway.. ;) > > /mjt > So for a server system, the following options should be as follows: Preemption Model (No Forced Preemption (Server)) ---> [ ] Preempt The Big Kernel Lock Also, my mobo has HPET timer support in the BIOS, is there any reason to use this on a server? I do run X on it via the Intel 965 chipset video. So bottom line is make sure not to use preemption on servers or else you will get weird spinlock/deadlocks on RAID devices--GOOD To know! Thanks! Justin.