Best practices for using gjournal with gmirror?

I have a few questions for pjd (or anyone else) about using gjournal,
particularly when used with gmirror.

1) I'm running 6-STABLE and plan to test with gjournal6_20061030.patch (from
the mailing list; updated version of 20061024 that applies cleanly). Is
there a better/newer version for -STABLE that I should use instead?

2) When using gjournal and for a gmirror volume, does the journal need to be
mirrored as well to maintain redundancy? If so, when storing the journal on
the same physical disks as the mirror, is it better to mirror at the slice
level (journal and fs on different partitions in the same mirror) or at the
partition level (journal and fs each have their own mirror) or does it
matter?

3) I remember reading where pjd said that gjournal plus gmirror or graid3
would eliminate the need to re-sync the array after a crash. While clearly
a design goal, is that actually the case with the version of the patch
mentioned above? If so, are any config changes needed or will it just
happen automagically?

4) In the same vein as 3)--does a gjournal volume need to be fsck'ed after a
crash? If not, will it just work (e.g. fsck -p sees that the filesystem is
clean) or does it need to be disabled somehow?

5) Finally, how dangerous is this code? I realize it's experimental and only
plan to use it with data that has recent backups, but how much should I
worry about it blowing up my system or corrupting my files?

Thanks!

JN
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Best practices for using gjournal with gmirror?
    ... particularly when used with gmirror. ... the same physical disks as the mirror, is it better to mirror at the slice ... level (journal and fs on different partitions in the same mirror) or at the ... last few seconds before the crash, gmirror will not resync them on boot, ...
    (freebsd-hackers)
  • Re: gjournal: journaled slices vs. journaled partitions
    ... I didn't want to only put gmirror and have full drives rebuild ... I went with this setup anyway and I made some reset tests to see what ... provider is directly on the mirror provider for all mirrored filesystems ... the ill-advised journaled small partition issue been successfully overcome ...
    (freebsd-questions)
  • Unrecoverable UFS error but only with gmirror
    ... gmirror and/or ufs got into an odd state after a panic, where fsck could not fix errors on the mirror device, but each member filesystem was fine. ... Even after destroying the mirror, fixing all three member file systems with fsck, and recreating the mirror with just a single member fsck found the same errors on the mirror device. ...
    (freebsd-current)
  • Re: gmirror disk fail questions...
    ... mirror/gm0 DEGRADED ad4 ... I am guessing that a failing disk is responsible for the data ... the mirror is marked clean ad there's no warnings about ... I believe the kernel hides individual labels for a gmirror volume. ...
    (freebsd-questions)
  • Re: gmirror problem on 5.3-R i386
    ... > I'm having a problem with gmirror. ... > first disk to the mirror after booting off the second drive. ... You probably destroyed your slice table here. ...
    (freebsd-questions)