Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932869Ab0KRWJu (ORCPT ); Thu, 18 Nov 2010 17:09:50 -0500 Received: from ironport2-out.teksavvy.com ([206.248.154.183]:38091 "EHLO ironport2-out.pppoe.ca" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754056Ab0KRWJs (ORCPT ); Thu, 18 Nov 2010 17:09:48 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApIBAAcz5UxLd/sX/2dsb2JhbAAHgz3OLpBygSKDNnMEhFqLEA X-IronPort-AV: E=Sophos;i="4.59,219,1288584000"; d="scan'208";a="82911240" Message-ID: <4CE5A42A.5080308@teksavvy.com> Date: Thu, 18 Nov 2010 17:09:46 -0500 From: Mark Lord User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: Markus Trippelsdorf CC: Jamie Lokier , Jeff Moyer , James Bottomley , Christoph Hellwig , Matthew Wilcox , Josef Bacik , Lukas Czerner , tytso@mit.edu, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, sandeen@redhat.com Subject: Re: [PATCH 1/2] fs: Do not dispatch FITRIM through separate super_operation References: <1290065809-3976-1-git-send-email-lczerner@redhat.com> <20101118130630.GJ6178@parisc-linux.org> <20101118134804.GN5618@dhcp231-156.rdu.redhat.com> <20101118141957.GK6178@parisc-linux.org> <20101118142918.GA18510@infradead.org> <1290100750.3041.72.camel@mulgrave.site> <20101118180557.GU22787@shareable.org> <20101118193255.GE1594@arch.trippelsdorf.de> <4CE59E86.1080603@teksavvy.com> <20101118215008.GA1556@arch.trippelsdorf.de> In-Reply-To: <20101118215008.GA1556@arch.trippelsdorf.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1614 Lines: 39 On 10-11-18 04:50 PM, Markus Trippelsdorf wrote: > On 2010.11.18 at 16:45 -0500, Mark Lord wrote: >> On 10-11-18 02:32 PM, Markus Trippelsdorf wrote: >>> On 2010.11.18 at 18:05 +0000, Jamie Lokier wrote: >>>> Online trim may be slow, but offline would be awfully inconvenient >>>> when an fs is big and needed for a live system, or when it's your root fs. >>> >>> You can call FITRIM from a running system. Infact I run it once per week >>> as a cron job on my (mounted) root fs. >> >> >> Ditto for wiper.sh. > > But I always thought that wiper has no access to the filesystem > internals. So there is always a chance that you write to a sector that > wiper.sh is currently trimming. FITRIM should be safer in this regard. No, wiper.sh is very safe for online TRIM. It reserves the blocks before trimming them, so nothing else can write to them. The danger with wiper.sh, is that WHILE it is running, it reserves most of the free space of the filesystem. So if there are other apps writing tons of new data to the drive, while not freeing up old data, the system can run low on diskspace for a moment. wiper.sh counters that by not reserving/trimming *everything* when run online, leaving a reasonable amount of scratch space available for other apps during the run. This is where having a fully capable FITRIM, with multi-range TRIMs, would be useful. Cheers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/