Date: Wed, 10 Jun 2009 13:46:59 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Dmitry Morozovsky <marck@rinet.ru> Cc: freebsd-hackers@freebsd.org, dan.naumov@gmail.com, freebsd-current@freebsd.org, sthaug@nethelp.no, snb@freebsd.org, =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Subject: Re: sysinstall, GJOURNAL and ZFS Message-ID: <alpine.BSF.2.00.0906101346040.16323@wojtek.tensor.gdynia.pl> In-Reply-To: <alpine.BSF.2.00.0906101428591.49870@woozle.rinet.ru> References: <alpine.BSF.2.00.0906091632430.6551@wojtek.tensor.gdynia.pl> <cf9b1ee00906090757v7d589dfch978076a97be724a9@mail.gmail.com> <20090609172142.GA92146@ebi.local> <20090609.195750.41709103.sthaug@nethelp.no> <86hbyowgj6.fsf@ds4.des.no> <alpine.BSF.2.00.0906101428591.49870@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> to be more precise): inappropriate time of file system lock on snapshot > creation. On not-too-big 300G ufs2 not-too-heavy loaded snapshot creation time > is 20+ minutes, and 5+ from that file system blocked even on reads. This looks > unacceptable for me for any real use. that's why i disable it. If you sum up time of total blocked and time of almost-blocked you will end with much more than fsck normally use with foreground check.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0906101346040.16323>