Date: Mon, 31 Jul 2006 12:10:33 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: "R. B. Riddick" <arne_woerner@yahoo.com> Cc: Brent Hostetler <brenthostetler@gmail.com>, freebsd-geom@freebsd.org Subject: Re: gmirror/gconcat: mkdir causes system reboot Message-ID: <20060731101033.GA842@garage.freebsd.pl> In-Reply-To: <20060731085125.49554.qmail@web30312.mail.mud.yahoo.com> References: <aadbc3580607310119m245c0954l472fdc7e7df16964@mail.gmail.com> <20060731085125.49554.qmail@web30312.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Mon, Jul 31, 2006 at 01:51:25AM -0700, R. B. Riddick wrote: > --- Brent Hostetler <brenthostetler@gmail.com> wrote: > > These errors repeated for about 3meg log file of errors. > > > Hmm... Maybe u mounted ur file system unclean somewhen (e. g. by pressing > CTRL+C during the boot process) and then the errors escalated cataclysmically? > :-) > > Or maybe ur gmirror's where out of sync due to some strange administrative > trick or due to a system crash during synchronization (so that just one half of > the mirror had the new data, while it stayed unmentioned, that the other half > had still the old data (this is something fsck could miss, when it just reads > the new/good half of the mirror (e. g. because those discs r faster or because > of a coincidence))). Gmirror protects against such situations - on power loss or system crash it will resynchronize mirrors. I've heard of problems with growfs(8). Another option is incorrect addition of the new disk to gconcat device. -- Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEzdcZForvXbEpPzQRAq6qAJ0WVq6fLVFbYxse5pUcVMn/P4XO0ACgiEa8 01x8TC4vl3QQs7nYFMqziGQ= =OJy/ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060731101033.GA842>