From owner-freebsd-current@FreeBSD.ORG  Wed Mar 20 17:53:18 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 07E0BA82
 for <freebsd-current@freebsd.org>; Wed, 20 Mar 2013 17:53:18 +0000 (UTC)
 (envelope-from deeptech71@gmail.com)
Received: from mail-ee0-f51.google.com (mail-ee0-f51.google.com [74.125.83.51])
 by mx1.freebsd.org (Postfix) with ESMTP id 801CA919
 for <freebsd-current@freebsd.org>; Wed, 20 Mar 2013 17:53:16 +0000 (UTC)
Received: by mail-ee0-f51.google.com with SMTP id d17so1234838eek.38
 for <freebsd-current@freebsd.org>; Wed, 20 Mar 2013 10:53:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=x-received:message-id:date:from:user-agent:mime-version:to:subject
 :references:in-reply-to:content-type:content-transfer-encoding;
 bh=C4DuI16kVOdB7F8vX9753AgBpqK/UFoXGOsKb+BlTs0=;
 b=S7Apiu/9/qIR4YpxW18OnWf0v+o8zawouFeQTDbc3XNskOK4PTiV3VzghXeu+aWpeB
 +hVW4Mq1HQb5O0V5E++kcs7lLlF90Ms8cr1hGVfThKnqrA8iOvOoQe1f+2dY3LUMzXZR
 9bMbLIVPH2c50VDyrOHr6+5jaZPphMk/vMhSf8+pnZwiAYCu6XO5LGf6cTFkTqr6awsC
 jSLBLVEDiSJCxyLCDQzPPaKT1SkBO+Zt6burVcb+JNm0jaenzEwU/ZGu8ayzBLd8QZ0l
 PTZPBxNVAiCo6UCicL+1iiuVxx9KHN5iLZevgII8VZni0DHJ407N0gHtKZiF4IHiye4O
 vcZg==
X-Received: by 10.14.5.6 with SMTP id 6mr74002027eek.42.1363801989789;
 Wed, 20 Mar 2013 10:53:09 -0700 (PDT)
Received: from [192.168.1.80] (91EC574C.dsl.pool.telekom.hu. [145.236.87.76])
 by mx.google.com with ESMTPS id 3sm3997213eej.6.2013.03.20.10.53.07
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 20 Mar 2013 10:53:08 -0700 (PDT)
Message-ID: <5149F77F.2000900@gmail.com>
Date: Wed, 20 Mar 2013 18:53:03 +0100
From: deeptech71 <deeptech71@gmail.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD i386;
 rv:18.0) Gecko/20100101 SeaMonkey/2.15
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Subject: Re: access to hard drives is "blocked" by writes to a flash drive
References: <201303040301.r2431Rjm008175@gw.catspoiler.org>
 <51341AA6.7080601@gmail.com> <20130319172617.GA44701@blazingdot.com>
In-Reply-To: <20130319172617.GA44701@blazingdot.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 17:53:18 -0000

On 03/19/2013 18:26, Marcus Reid wrote:
> On Mon, Mar 04, 2013 at 04:53:10AM +0100, deeptech71 wrote:
> I use atimes all the time to get to the bottom of lots of common
> problems.

Details !

It sounds like in your case, atime is a debugging feature (which are generally to be turned off on production systems).

> Turning off atime system-wide is a really bad move.

Your bikeshed.

Turning off atime works for me. SUPPORT_ATIME=0 would be an *optional* kernel option. Additionally a DEFAULT_NOATIME=1 may be provided.