From owner-freebsd-questions@FreeBSD.ORG Thu Mar 23 15:13:31 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 58E3F16A42A for ; Thu, 23 Mar 2006 15:13:31 +0000 (UTC) (envelope-from ovidiue@unixware.ro) Received: from elgreco.hmdnsgroup.com (elgreco.hmdnsgroup.com [63.247.135.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 720ED43D8F for ; Thu, 23 Mar 2006 15:13:10 +0000 (GMT) (envelope-from ovidiue@unixware.ro) Received: from 86-124-116-144.iasi.cablelink.ro ([86.124.116.144]:54401 helo=[10.0.0.4]) by elgreco.hmdnsgroup.com with esmtp (Exim 4.52) id 1FMRUq-0003aR-Mr; Thu, 23 Mar 2006 10:13:08 -0500 Message-ID: <4422BB30.2040007@unixware.ro> Date: Thu, 23 Mar 2006 17:13:52 +0200 From: ovidiu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050420 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jeays References: <97be9bec0603221420v7ac97162lc55d5f2013d50bdf@mail.gmail.com> <72cf361e0603222250i6084e1aara126fdb3321b7ed1@mail.gmail.com> <1143125645.13828.7.camel@chaucer.jeays.ca> In-Reply-To: <1143125645.13828.7.camel@chaucer.jeays.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-HMDNSGroup-MailScanner-Information: Please contact the ISP for more information X-HMDNSGroup-MailScanner-SpamCheck: X-HMDNSGroup-MailScanner-From: ovidiue@unixware.ro X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - elgreco.hmdnsgroup.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - unixware.ro X-Source: X-Source-Args: X-Source-Dir: Cc: Luiz Eduardo Guida Valmont , freebsd-questions@freebsd.org, Martin Hepworth Subject: Re: Availability of a journaling file system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Mar 2006 15:13:31 -0000 Mike Jeays wrote: >On Thu, 2006-03-23 at 06:50 +0000, Martin Hepworth wrote: > > >>Hi >> >>in freebsd this is called softupdates and can be enables using tunefs (see >>the man page). >> >>If not quite journaling as it does things slightly differently, but achieves >>many of the same effects, like reduced fsck time on boot. >> >>-- >>martin >> >>On 3/22/06, Luiz Eduardo Guida Valmont wrote: >> >> >>>I've had some problems earlier this year due to FreeBSD-6.0 crashing >>>after a few hours of execution (perhaps it's mal-functioning hd's dma, >>>but - simply put - I can't install FreeBSD 2 or 3 times a day to find >>>out! ^^). And so I thought of journaling file systems. >>> >>>I think XFS is being ported to FreeBSD, but last news on the official >>>page (http://people.freebsd.org/~rodrigc/xfs/) dates from December >>>12th, 2005 (and it's still read-only). So... >>> >>>Is there a journaling file system (rw ready) available? Which one? >>> >>>Another question: how can I completly diable hd dma? -.-" >>> >>>-- >>>[]'s, >>>Luiz Eduardo >>> >>>_______________________________________________ >>>freebsd-questions@freebsd.org mailing list >>>http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>>To unsubscribe, send any mail to " >>>freebsd-questions-unsubscribe@freebsd.org" >>> >>> >>> >>> >>_______________________________________________ >>freebsd-questions@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >> >> > >You can disable DMA with the atacontrol command: for example > >atacontrol mode ad0 pio4 > >I have a Maxtor 40GB which won't work in DMA mode with FreeBSD, although >it seems fine with other OSes. There is a hefty perfomance hit, of >course! > > > > Did you tried with different ATA cable? I've solved this kind of issues every time by changing the cable or by lower-ing the settings for ATA, like instead of ATA133 to use ATA100, or ATA66. #atacontrol list #atacontrol mode ad0 ATA66 Try that, if it works, try ATA100. Your hard drive, motherboard and your cable, all must be ATA100 to support that speed.