From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Layton Subject: Re: IOzone testing Date: Sat, 26 Sep 2009 12:32:04 -0400 Message-ID: <4ABE4204.70704@att.net> References: <4ABE0553.3090502@att.net> <4ABE0AD7.7000904@att.net> <4ABE13D3.2080809@att.net> <4ABE2704.6030607@att.net> <4ABE2E86.5010708@att.net> Reply-To: NILFS Users mailing list Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: users-bounces-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org Errors-To: users-bounces-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org To: NILFS Users mailing list Byron Guernsey wrote: > Be aware that garbage collection will take quite a while on a full > drive to go back to 0 unless you also increase the segments cleaned > per run and if you accidentally leave it high it will impact > performance. > > This is why I had asked about a way to force a full GC with a > protection period other than that in the conf file. It seems like > quick forced cleanup when a user deletes a lot of files is a common > need... > That is a good feature to add - quick full GC with a different protection period. +1 on that option. I think I might just to a mkfs in between runs to make sure that the checkpoints are eliminated. That works for my testing but it doesn't work for real, live, working file systems. Jeff