From owner-freebsd-fs@FreeBSD.ORG Wed Apr 21 08:05:03 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 701951065670 for ; Wed, 21 Apr 2010 08:05:03 +0000 (UTC) (envelope-from davidn04@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 21EF88FC08 for ; Wed, 21 Apr 2010 08:05:02 +0000 (UTC) Received: by qyk11 with SMTP id 11so7810431qyk.13 for ; Wed, 21 Apr 2010 01:05:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=81z+bp8ZEj9mWszAysV7zT9s9n5E1CoJ/TrBN3EsTlQ=; b=cKgFV5PrcLtucG8TIeReIz3AU9w8/KHVa5Um6Y+RLZVcISq/PHmY4RnTYUfO06CKua 4/xGhkiKTvMzseuJ5D8Se2y1liSKXxvWvwkSfKDMsRaalXPh5u8cJf0pa2piKioUsERu W6FTco79yBpPiXOpkuY5z+rHFRNA8I7+W6qDw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=NQV3QNKSmABZiOQR60L4adPXDGJu45+sjSZ5COuZmWPJf2RWLwUwt4opIiLOWuC2JK VnpIJT8ispZs6Dg5IY6nIp07BnuAAlS3DSIm8bqEienARDweNPBgRkoi1WQsYrX39eQJ h2Fab76DpITMBwnDt/MTpiBL5yOUNPt8HjaUs= MIME-Version: 1.0 Received: by 10.229.87.142 with HTTP; Wed, 21 Apr 2010 01:05:02 -0700 (PDT) In-Reply-To: <20100421024803.GA25701@duncan.reilly.home> References: <20100418235428.GC4620@duncan.reilly.home> <20100420234447.GB1737@garage.freebsd.pl> <20100421011834.GA24928@duncan.reilly.home> <20100421024803.GA25701@duncan.reilly.home> Date: Wed, 21 Apr 2010 18:05:02 +1000 Received: by 10.229.227.5 with SMTP id iy5mr5224063qcb.29.1271837102301; Wed, 21 Apr 2010 01:05:02 -0700 (PDT) Message-ID: From: David N To: Andrew Reilly Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: gjournal: what is it good for? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2010 08:05:03 -0000 On 21 April 2010 12:48, Andrew Reilly wrote: > Hi David, > > On Wed, Apr 21, 2010 at 12:20:46PM +1000, David N wrote: >> Gjournal on my systems are pretty quick on startup after a power outtage= . > > Great to hear! > >> What kind of disks are you using? Or what hardware are you using? > > Several: main /usr is on a gjournal on top of a gmirror over a > pair of Samsung 1TB 3.5" SATA drives, but I have other gjournals > on a 750G WD SATA, a 1.5T Seagate and another 1TB WD MyBook > firewire unit. =A0There is brokenness in the firewire connection > that results in me always coming up manually through single-user > mode, at the moment. =A0In single user mode pilot error is > sufficient to account for the problems that I was having with > mount vs fsck of the gjournalled drives, I'm fairly sure. > > The firewire issue is strange: at boot-up the fw stack (this > is 9-current) doesn't reset the bus well enough or for long > enough for the drive to be fully recognised and show up in /dev, > but a post-boot "fwcontrol -r" does the job nicely. =A0It's a bit > inconvenient that fwcontrol is in /usr/sbin, rather than /sbin, > so it's not available until the rest of the mounts are complete. > USB "works" but is sufficiently slower that I'm prepared to > hand-hold the boot process in order to have my backups finish in > reasonable time. > >> Might be the disks are ignoring the BIO_FLUSH. > > Not sure: how could I tell? > > Thanks for the support and suggestions. > > Cheers, > > -- > Andrew > Wow, thats a setup. I have a few more questions. Your first email, you mentioned gjournal overflow panics. Have you fixed th= at? I see you are gmirroring the slices, when you did the gmirror + gjournal slice, did you check the bsdlabel? sometimes it doesn't report the right block size, and the disk + journal overlap. I had this happen to me on my first setup which resulted in the overflow panics. Its not as easy as a gmirror label ... gjournal label ... You gotta check the bsdlabel each time to make sure the c slice and additional slices are the correct size. If you do decide to do it again, gpt made it really easy. Did you use newfs -J to format the slices/journal? Regards David N