From owner-freebsd-questions@FreeBSD.ORG Mon Apr 11 21:09:11 2005 Return-Path: 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 4139016A4CE; Mon, 11 Apr 2005 21:09:11 +0000 (GMT) Received: from smtpgate.tsgincorporated.com (ns1.tsgincorporated.com [67.66.242.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id A497543D31; Mon, 11 Apr 2005 21:09:08 +0000 (GMT) (envelope-from micheal@tsgincorporated.com) Received: from localhost (localhost.tsgincorporated.com [127.0.0.1]) by smtpgate.tsgincorporated.com (Postfix) with ESMTP id 059AA3CD70B; Mon, 11 Apr 2005 16:09:08 -0500 (CDT) Received: from smtpgate.tsgincorporated.com ([127.0.0.1])port 10024) with ESMTP id 29371-06; Mon, 11 Apr 2005 16:09:05 -0500 (CDT) Received: from mail.tsgincorporated.com (lanmail.tsgincorporated.com [67.66.242.29]) by smtpgate.tsgincorporated.com (Postfix) with ESMTP id 30DDC3CD702; Mon, 11 Apr 2005 16:09:05 -0500 (CDT) Received: from micheal (micheal.tsgincorporated.com [67.66.242.77]) by mail.tsgincorporated.com (Postfix) with SMTP id A0DB795282D; Mon, 11 Apr 2005 16:09:05 -0500 (CDT) Message-ID: <019e01c53eda$ffc461e0$4df24243@tsgincorporated.com> From: "Micheal Patterson" To: "NMH" , "hardware" , "questions" References: <20050411193037.40627.qmail@web41827.mail.yahoo.com> Date: Mon, 11 Apr 2005 16:11:15 -0500 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.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: amavisd-new at tsgincorporated.com Subject: Re: Hard drive fullness limits information help request X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 21:09:11 -0000 ----- Original Message ----- From: "NMH" To: "hardware" ; "questions" Sent: Monday, April 11, 2005 2:30 PM Subject: Hard drive fullness limits information help request > Hi all > I know hard drives tend to not run well when near > full. They have trouble performing self adjustments > (hardware), self defragging(unix/FFS) etc.. (as I can > express it) However, I need to find some documentation > or some help in explaining this better. > I am working with some people who store loads of > files, on many drives and tend to fill the drives to > 95% and more and then can't understand why they become > unstable. I need to be able to explain it better and > I would also like to know more to be able to > factually/sanely set a percent full safe limit. > > Any help would be appreciatted > > Thanks! > > NMH. > > > > The Large Print Giveth And The Small Print Taketh Away > -- Anon NMH, If these people are old enough to remember LP records, explain it to them in this fashion. A hard drive is much like an older LP record. Multiple songs, in sequencial order. You can play them in any order that you wish by moving the tone arm to a different song on the album. Now, say that you don't like track 3 and wish to delete it (if you could). You would end up with 3 minutes of blank space in the album. So, you want to add another song that you do like, but it's 3 minutes 30 seconds long and won't fit into a 3 minute time slot. A hard drive is able to place this 30 seconds at the end of the current space and be able to jump to that 30 extra seconds and you never know the difference. Now, if this happens a lot, meaning removing data, adding larger data, removing data, adding smaller chunks of data, etc, the actual data will get scattered throughout the disk. This is known as data fragmentation. Hard drives are able to deal with to a considerable degree however the more fragmented a drive is, the harder the drive has to work in order to make that unnoticed jump. As the drive works harder, access times grow longer and there is a higher potential for data loss. When drives get to a higher usage (90%+ utilization), there isn't much room to left to handle those scattered chuncks of data. That's the analogy that I used to use and it worked pretty well for me. Your mileage may vary. -- Micheal Patterson Senior Communications Systems Engineer 405-917-0600 Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.