Date: Thu, 13 Sep 2012 18:07:13 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Eugene Grosbein <egrosbein@rdtc.ru> Cc: stable@FreeBSD.org, re@FreeBSD.org Subject: Re: GEOM_RAID in GENERIC is harmful Message-ID: <5051F6A1.50900@FreeBSD.org> In-Reply-To: <5051AEE3.7010907@rdtc.ru> References: <50516F96.1020905@rdtc.ru> <5051ACBD.1090207@FreeBSD.org> <5051AEE3.7010907@rdtc.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13.09.2012 13:01, Eugene Grosbein wrote: > 13.09.2012 16:51, Alexander Motin wrote: > >>> That's makes users very angry when production server fails to boot >>> with GENERIC kernel after correctly performed upgrade. >>> >>> GEOM_RAID compiled in GENERIC should be deactivated and require activation >>> with some loader knob. Also, we need distinct RELEASE NOTES warning about the issue. >> >> Problem of on-disk metadata garbage is not limited to GEOM_RAID. For >> example, I had case where remainders of old UFS file system were found >> by GEOM_LABEL and ZFS incorrectly attached to it instead of proper GPT >> partition, making other partitions inaccessible. Does it mean we should >> remove GEOM_LABEL also? I don't think so. All what GEOM_RAID is guilty >> in is that it was not in place for 9.0 release. If we remove it now, it >> will just postpone the problem for later time or will never be able to >> add it again because of the same reasons. > > We must be ready for lots of angry users of 9.1-RELEASE then > and have BIG RED WARNING in RELEASE NOTES. Warning is good, but I don't think it will be "lots". It is enabled in 9-STABLE for some time now and I haven't seen many complains. If re@ permit to MFC r240465 in few days, solution for those who may need it will be simple: kern.geom.raid.enable=0. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5051F6A1.50900>