Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Mar 2010 12:26:00 +0100
From:      krad <kraduk@googlemail.com>
To:        Matthew Seaman <m.seaman@infracaninophile.co.uk>
Cc:        freebsd-questions@freebsd.org, =?KOI8-R?B?5M3J1NLJyiDixcjUxdLF1w==?= <dbehterev@gmail.com>
Subject:   Re: Create GMIRROR only one slice
Message-ID:  <d36406631003300426q1d85d211ud6d6b80c764ea5a7@mail.gmail.com>
In-Reply-To: <4BB1A290.2090802@infracaninophile.co.uk>
References:  <7aaa60421003250703hf24d3c1icae624982210c094@mail.gmail.com> <7aaa60421003291119s53e21ff6reb2b39e0690b65c3@mail.gmail.com> <d36406631003291310x15025173l5cb34e7aee9371ba@mail.gmail.com> <4BB1A290.2090802@infracaninophile.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
2010/3/30 Matthew Seaman <m.seaman@infracaninophile.co.uk>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 29/03/2010 21:10:42, krad wrote:
> > You will need to newfs the gmirror device
> > after that so backup the data currently on /, then copy it back
> afterwards.
>
> This is counter to all my experience of dealing with gmirror -- it's
> carefully designed so that the metadata it writes to the drive
> *doesn't* interfere with the filesystem.  While it is always a good
> idea to have backups, I do not believe that destroying and recreating
> the filesystem should be necessary.
>
>        Cheers,
>
>        Matthew
>
> - --
> Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
>                                                  Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
>                                                  Kent, CT11 9PW
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkuxopAACgkQ8Mjk52CukIxvZwCaAgTijPzbHoL5whM6F3GQax2N
> eN4An3/HZSRgUml7jy+IpYRyK0rEfGRr
> =e+4T
> -----END PGP SIGNATURE-----
>

Im pretty sure that it will nick the last sector from the slice, so you will
at least need to fsck it. If its a production system i would always go for
the cleaner approach as well and newfs is about as clean as it gets.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d36406631003300426q1d85d211ud6d6b80c764ea5a7>