From owner-freebsd-stable@FreeBSD.ORG Thu Jul 4 20:48:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0390721B for ; Thu, 4 Jul 2013 20:48:41 +0000 (UTC) (envelope-from mike.jakubik@intertainservices.com) Received: from mail.intertainservices.com (mail.intertainservices.com [69.77.177.114]) by mx1.freebsd.org (Postfix) with ESMTP id D31401E2B for ; Thu, 4 Jul 2013 20:48:40 +0000 (UTC) Received: from freebsd.local (unknown [172.16.10.114]) by mail.intertainservices.com (Postfix) with ESMTPSA id C52525643A for ; Thu, 4 Jul 2013 16:48:38 -0400 (EDT) Message-ID: <51D5DFA6.6010202@intertainservices.com> Date: Thu, 04 Jul 2013 16:48:38 -0400 From: Mike Jakubik User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130703 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: UFS Trim wont stay set References: <51D5CEF8.9000504@intertainservices.com> <20130704203342.GA98181@icarus.home.lan> In-Reply-To: <20130704203342.GA98181@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-intertainservices-MailScanner-Information: Please contact the ISP for more information X-intertainservices-MailScanner-ID: C52525643A.AED7D X-intertainservices-MailScanner: Found to be clean X-intertainservices-MailScanner-From: mike.jakubik@intertainservices.com X-Spam-Status: No X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jul 2013 20:48:41 -0000 On 07/04/13 16:33, Jeremy Chadwick wrote: > Yup, experienced this myself many times over. The reasons are > understood (it's not limited to just the TRIM bits, it's related to > anything adjusting the superblock -- it gets cached in memory in > certain situations and not flushed back to disk). Hint: are you > booting into single user and then issuing a "mount" command before > doing your tunefs stuff? If so, this is probably what's causing it (at > least it was in my case). Instead just boot into single-user, do not > mount anything, and use /sbin/tunefs (if available -- depends on your > filesystem setup) or /rescue/tunefs. I booted in to single user mode and the system mounted the only file system there, which is mounted at /. What i did now however is boot off a Live CD and run tunefs, this did the trick! Thank You!