From owner-freebsd-questions@FreeBSD.ORG Sun Oct 2 16:03:29 2005 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 5905A16A41F for ; Sun, 2 Oct 2005 16:03:29 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id C630243D45 for ; Sun, 2 Oct 2005 16:03:27 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id z31so163070nzd for ; Sun, 02 Oct 2005 09:03:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XHDf2ObXSr9YkAOLyKjJspZN7L5sDa2SJsjO40bcDVkhgyHt6SKv6QCGqwI2XEEnerxrKD8YppHU90nVmVa0zgySuMz32lUeXCC9ugH8uCtREN7rQ7Fgnz6GfeY0CjD6/noYo8KkobOq1kroY016mXW2LN10aFkAX+Vr/blLzuc= Received: by 10.36.3.19 with SMTP id 19mr461487nzc; Sun, 02 Oct 2005 09:03:27 -0700 (PDT) Received: by 10.37.20.34 with HTTP; Sun, 2 Oct 2005 09:03:27 -0700 (PDT) Message-ID: Date: Sun, 2 Oct 2005 20:03:27 +0400 From: "Andrew P." To: Kiffin Gish In-Reply-To: <1128268728.704.2.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1128254897.26048.11.camel@localhost> <20051002121454.3D1C643D45@mx1.FreeBSD.org> <1128268728.704.2.camel@localhost> Cc: "Tamouh H." , freebsd-questions@freebsd.org Subject: Re: Defragmentation needed with FreeBSD ... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Andrew P." List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2005 16:03:29 -0000 On 10/2/05, Kiffin Gish wrote: > On Sun, 2005-10-02 at 17:11 +0400, Andrew P. wrote: > > On 10/2/05, Tamouh H. wrote: > > > > > > > > > > > I was just wondering if like in Windows disk fragmentation > > > > arises, and if so then how should one go about defragmenting it? > > > > > > There is no fragmentation in the BSD file systems, that is something = related > > > to Windows only. You might want to add the line: > > > > > > fsck_y_enable=3D"YES" > > > > > > to your /etc/rc.conf in the event fsck finds errors on your disks. > > > > > > > > > _______________________________________________ > > > freebsd-questions@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freeb= sd.org" > > > > > > > Of course there is fragmentation. > > > > UFS, particularly its implementation in FreeBSD is > > more intelligent than NTFS/FAT32. When there is > > enough free space on the disk (typically more than > > 15%, see tunefs(8) for details), I/O is automatically > > optimized to minimize fragmentation. > > > > When your win32 box is idle, but the hdd is scratching > > it's very annoying, because you know that windows > > is swapping something. > > > > When your bsd box is idle, but the hdd is scratching > > it's quite pleasant, 'cuz that's some hard-working > > daemons make sure that you don't loose any data, > > and always can enjoy the maximum performance. > > _______________________________________________ > > 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" > > So if I understand you correctly, this means that the disk is > defragmented automatically in the background during idle use, e.g. I do > not have to do anything else to enable it because it is already enabled. > > Correct? > > -- > Kiffin Gish > Gouda, The Netherlands > > It's not that simple, but the fact is that you don't need to worry about fragmentation at all. Just make sure that your drives have at least 15-20% free space for maximum performance.