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

On Mon, Feb 28, 2011 at 06:23:10PM +0200, Marin Atanasov Nikolov wrote:
2011/2/28 Andrey V. Elsukov <bu7cher@xxxxxxxxx>:
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

And that's where I got kernel panic.

gpart'ing the disk and the mirroring the partitions works just as
fine, but not when you mirror the whole disk.

I think this only ever worked accidentally at best. It would work
fine with the older fdisk-style disk partition because that doesn't
touch the end of the disk, but any time you tell two different programs
that they both have absolute control over the last sector on the disk
and can write critical data there - which is what this is doing -
that's begging for trouble.

Something cleaner than a kernel panic would be *nice* however... And
your point about warnings in the documentation is a good one.

-- Clifton

--
Clifton Royston -- cliftonr@xxxxxxxxxxxxxxxxxx / cliftonr@xxxxxxxx
President - I and I Computing * http://www.iandicomputing.com/
Custom programming, network design, systems and network consulting services
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • 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. ... > status is a degraded mirror and I cannot see any of the partitions on ...
    (freebsd-questions)
  • Re: gmirror disks vs partitions
    ... Apart from potentially avoiding a whole disk from being copied ... You divide a couple of identical drives proportionally ... in two partitions each, place a couple of the first ... partitions into gmirror and a couple of the second ...
    (freebsd-stable)
  • LVM on SW RAID for sarge - success
    ... I've just had success migrating Debian Sarge to root on LVM on RAID. ... First make sure the SCSI BIOS boots from the first disk. ... I made reiserfs on all the filesystem partitions and completed the ... The remaining two disks were partitioned and used to create RAID arrays ...
    (Debian-User)
  • Re: Replace SCSI Drive
    ... from there you can manipulate other hard drives attached to the machine. ... It should 'just work' but watch out that you keep disk devices ... vi-a) Write a BSD partition table into the slice, then set up your required FreeBSD partitions: ... items under the 'Custom Install' to achieve the desired result. ...
    (freebsd-questions)
  • Re: New BSD Installer
    ... I have a lot of machines booting from gmirror, ... Am I the only one person on the whole earth seeing the big difference in easy setup of mirroring two drives instead of many individual partitions? ... Freddie Cash already write about disk thrashing on rebuild after power failure, but initial setup or repair after disk replacement is also pain with mirroring individual partitions. ...
    (freebsd-stable)