Date: Wed, 21 Apr 2010 18:05:02 +1000 From: David N <davidn04@gmail.com> To: Andrew Reilly <areilly@bigpond.net.au> Cc: freebsd-fs@freebsd.org Subject: Re: gjournal: what is it good for? Message-ID: <r2q4d7dd86f1004210105o1ab574b7g350822e9bed99b82@mail.gmail.com> In-Reply-To: <20100421024803.GA25701@duncan.reilly.home> References: <20100418235428.GC4620@duncan.reilly.home> <20100420234447.GB1737@garage.freebsd.pl> <20100421011834.GA24928@duncan.reilly.home> <k2q4d7dd86f1004201920s2139647aja783e86e266153ca@mail.gmail.com> <20100421024803.GA25701@duncan.reilly.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 April 2010 12:48, Andrew Reilly <areilly@bigpond.net.au> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?r2q4d7dd86f1004210105o1ab574b7g350822e9bed99b82>