Date: Wed, 5 Nov 2008 11:29:07 +0000 (UTC) From: Vadim Goncharov <vadim_nuclight@mail.ru> To: freebsd-geom@freebsd.org Subject: Re: gpart oddity Message-ID: <slrngh30s2.1o13.vadim_nuclight@server.filona.x88.info> References: <48FF2607.10807@icyb.net.ua> <63F8346D-0116-4F41-BCAA-C235E9657BD8@mac.com> <48FF82BA.3020309@icyb.net.ua> <48FF913A.9070700@icyb.net.ua> <7334715F-FAE1-40EE-92EB-468041587410@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Marcel Moolenaar! On Wed, 22 Oct 2008 14:03:27 -0700; Marcel Moolenaar wrote about 'Re: gpart oddity': >> Then I remembered that I labeled ad4s1 purely through sysinstall and >> never touched it with disklabel(8), on the other hand I used >> disklabel to label ad4s2. > That's good to know; not that there's a lot we can do about all > those existing installations... >> My personal conclusions: >> 1. sysinstall seems to have handled those fields incorrectly, somehow. >> 2. those fields do not seem to be of any particular use/importance, >> so g_part_bsd might be overly strict here. > Being strict is not a bad thing, but given that we put an > invalid label on all new installations I think it's better > gpart doesn't check it or otherwise detect and corrects it. > (we know the absolute sector offset of the label, so if > secperunit is mediasize + offset, we know the not to flag > the label as invalid, patch it up and move on). The question is, how much strict it is? Currently I have an 6.2-S system with gmirror(8)'ed slices, not disks, as it was converted from existing system with different sizes of disks. I have had edit their labels that partition 'c' doesn't cover entire unit (and last partition was reformatted to be not truncated, too). This is needed to be sure that last sector gets not overwritten by gmirror(8) metadata, but bsdlabel(8) always complains about it that it doesn't cover bla-bla-bla. Moreover, labeled partitions and slices exist on their own, despite of gmirror(8). And yet more, if I try to do a bsdlabel(8) on a gm0, it will complain about 63 sectors boot offset, while on ad0s1 it will not, so I need to hack a lot if I need to resize partitions. What is the cause of the trouble? And, will I have any troubles with that setup when the system will be upgraded to newer major FreeBSD version in a year or two? -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?slrngh30s2.1o13.vadim_nuclight>