Date: Sat, 06 Jun 2009 23:10:48 -0300 From: Sergio de Almeida Lenzi <lenzi.sergio@gmail.com> To: freebsd-questions <questions@freebsd.org> Subject: Re: fsck on 1.5TB drive Message-ID: <1244340648.8936.7.camel@localhost> In-Reply-To: <alpine.BSF.2.00.0906062312520.93574@wojtek.tensor.gdynia.pl> References: <56942.76.25.231.251.1244295367.squirrel@webmail.wcubed.net> <1244306366.5333.8.camel@localhost> <alpine.BSF.2.00.0906062312520.93574@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Em Sáb, 2009-06-06 às 23:13 +0200, Wojciech Puchar escreveu: > > try to use journaling on the backup partition, (if you do not want to > > use ZFS...) > > is it THAT a problem to wait 5-10 minutes for fsck? > > on OS that really crash RARELY. Most cases not at all. You are right Puchar, but sometimes (2 in 100 on powerfailure) the filesystem gets corrupted (database files opened, and being extended)... so when the fsck enters, the database get corrupted.. by using zfs or journaling I never have anothter database problem.... People can say it is better to use a no-break in the server, Right again but in my case of about 1000 servers, after 2 years the batteries does not function any more... and I can rely only in the filesystem... a shell script that moves the partition to another HD previously formatted with ZFS (on amd64) or journaling (i386) solves my problem.... Sérgio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1244340648.8936.7.camel>