On Wed, 10 Feb 2010 10:18:49 +0100 Marius Nünnerich <mar...@nuenneri.ch> wrote about Re: zpool vdev vs. glabel:
MN> It seems there is some kind of race condition with zfs either picking MN> up the disk itself or the label device for the same disk. I guess it's MN> which ever it probes first. This could explain it. However, it seems that zfs sticks to the da device once it changed it's mind. Meanwhile I discovered one more system where is obviously has happened (although I cannot say when: luna# zpool status pool: tank state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz1 ONLINE 0 0 0 label/disk-1 ONLINE 0 0 0 da0 ONLINE 0 0 0 label/disk-2 ONLINE 0 0 0 label/disk-3 ONLINE 0 0 0 errors: No known data errors MN> I wrote the GPT part of glabel for using MN> it in situations like this, I had not a single report of this kind of MN> problem with the gpt labels. Maybe you can try them too? Yeah, I just have to look into how gpt labels work. I did not use them at all up to now. cu Gerrit _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"