From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Layton Subject: Re: IOzone testing Date: Sat, 26 Sep 2009 09:14:59 -0400 Message-ID: <4ABE13D3.2080809@att.net> References: <4ABE0553.3090502@att.net> <4ABE0AD7.7000904@att.net> Reply-To: NILFS Users mailing list Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 J=E9r=F4me Poulin wrote: > On Sat, Sep 26, 2009 at 8:13 AM, Jeff Layton wrote: > = >> It will only stop the clean up of checkpoints outside of policy - correc= t? >> So it won't stop them from being created but it will stop the cleaning >> process. >> >> = > It will completely stop cleaning checkpoints, which is what is > consuming drive I/O. Checkpoints in themselve don't use much > ressources, cleaning them however does. > = Got it - thanks. At the same time, I also hit an out of space message. Why would I get this message? If the checkpoints are just creating a small maker then it shouldn't take much space. Unless of course, a huge number of checkpoints are created. Thanks!