8.2-RELEASE - gmirror and gpart issue. Metadata overlap?

Freddie Cash fjwcash at gmail.com
Mon Feb 28 16:55:42 UTC 2011

On Mon, Feb 28, 2011 at 8:23 AM, Marin Atanasov Nikolov
<dnaeon at gmail.com> wrote:
> 2011/2/28 Andrey V. Elsukov <bu7cher at yandex.ru>:
>> On 28.02.2011 11:54, Johan Hendriks wrote:
>>> I opened a discussion on this before the release.
>>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/061184.ht
>>> ml
>>> On my 8.1 system, i get this message about the corrupt headers, but it
>>> booted on the 8.2 system it panics...
>>> I think a lot of people are going to get bit by this.
>>> As far as i know there is no warning anywhere that you can not use gpart
>>> and gmirror the whole disk.
> I can confirm as well that I get kernel panic  if I gpart and then
> gmirror a disk on 8.2-RELEASE.
> To reproduce it, I just did the following:
> 1) Boot a system with a Fixit image
> 2) Remove all gpart partitions
> 3) gpart the first disk (ad0)
> 4) Restored my data to the partitions from backups
> 5) Reboot
> 6) gmirror the ad0 disk

The above process is operator error, as both your gpart and gmirror
commands are working on the same GEOM (ad0).  You need to stack /
layer your GEOMs (ie, do one operation on the disk, the other
operations on the sub-parts).

  1)  gmirror the disk (ad0), and then gpart the mirror device
(/dev/mirror/whatever), or
  2)  gpart the disk (ad0), and the mirror the partititons (/dev/gpt/whatever)

The process you list above is the same as partitioning a disk (ad0),
and then newfs-ing the disk (ad0), and wondering where your partitions
went.  :)

(I believe option 1 above is what's causing issues in this thread.)

Freddie Cash
fjwcash at gmail.com

More information about the freebsd-stable mailing list