Date: Wed, 22 Oct 2008 22:44:58 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Marcel Moolenaar <xcllnt@mac.com> Cc: Marcel Moolenaar <marcel@freebsd.org>, freebsd-geom@freebsd.org Subject: Re: gpart oddity Message-ID: <48FF82BA.3020309@icyb.net.ua> In-Reply-To: <63F8346D-0116-4F41-BCAA-C235E9657BD8@mac.com> References: <48FF2607.10807@icyb.net.ua> <63F8346D-0116-4F41-BCAA-C235E9657BD8@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] on 22/10/2008 20:28 Marcel Moolenaar said the following: > > On Oct 22, 2008, at 6:09 AM, Andriy Gapon wrote: > >> >> I have the following geom options in my kernel config: >> GEOM_LABEL >> GEOM_PART_BSD >> GEOM_PART_GPT >> GEOM_PART_MBR >> >> The last three are recent addition that I want to report about. >> >> Also, geom_mirror and geom_journal are loaded as modules and I use both >> gmirror and gjournal, independently. >> >> This is a i386 7.1-PRERELEASE system, kernel is built from svn rev. >> 184137. >> Here's a diff between new kernel verbose dmesg and old kernel verbose >> dmesg (only geom specific lines, old kernel was built from sources from >> around Sep 24): >> >> -GEOM: new disk ad4 >> +GEOM: ad4s1: invalid disklabel. > > Your BSD disklabel is considered invalid. I've seen reports where > the recorded number of sectors is larger than the media size. > >> +GEOM: ad4s1b: invalid disklabel. >> +GEOM: ad4s1c: invalid disklabel. > > This is a problem with your configuration. You have not disabled > GEOM_BSD (nor GEOM_MBR) by adding "nooption GEOM_BSD" (and > "nooption GEOM_MBR"). For now it's best to keep it, because the > old BSD slicer does not check your disklabel and accepts it. Yes, this is exactly what happened. I was about to reboot to a kernel built with those nooptions when I got your email - thanks a lot for saving me from being puzzled! > Can you send me the output of dd for ad4s1, like: > > dd if=/dev/ad0s1 of=/tmp/dump count=16 > > As well as the output of sysctl kern.geom.conftxt. > > That allows me see in what way your BSD disklabel is invalid. Requested data follows (dd dump is in attachment). 0 DISK cd0 3548774400 2048 hd 0 sc 0 1 LABEL iso9660/KORABL 3548774400 2048 i 0 o 0 0 DISK ad4 320072933376 512 hd 16 sc 63 1 MBR ad4s2 19428111360 512 i 1 o 300642209280 ty 165 2 BSD ad4s2f 14059385856 512 i 5 o 5368717312 ty 7 3 LABEL ufs/xtra 14059385856 512 i 0 o 0 2 BSD ad4s2e 2147483648 512 i 4 o 3221233664 ty 1 3 JOURNAL ad4s1e.journal 271651147264 512 2 BSD ad4s2d 2147483648 512 i 3 o 1073750016 ty 1 3 JOURNAL ad4s1d.journal 26843545088 512 2 BSD ad4s2c 19428111360 512 i 2 o 0 ty 0 3 PART ad4s2cf 14059385856 512 i 6 o 5368717312 ty freebsd-ufs xs BSD xt 7 3 PART ad4s2ce 2147483648 512 i 5 o 3221233664 ty freebsd-swap xs BSD xt 1 3 PART ad4s2cd 2147483648 512 i 4 o 1073750016 ty freebsd-swap xs BSD xt 1 3 PART ad4s2ca 1073741824 512 i 1 o 8192 ty freebsd-swap xs BSD xt 1 2 BSD ad4s2a 1073741824 512 i 0 o 8192 ty 1 3 MIRROR mirror/rootfs 1073741312 512 1 MBR ad4s1 300642177024 512 i 0 o 32256 ty 165 2 BSD ad4s1e 271651147776 512 i 4 o 28991029248 ty 7 3 LABEL ufs/export 271651147776 512 i 0 o 0 3 JOURNAL ad4s1e.journal 271651147264 512 2 BSD ad4s1d 26843545600 512 i 3 o 2147483648 ty 7 3 JOURNAL ad4s1d.journal 26843545088 512 2 BSD ad4s1c 300642177024 512 i 2 o 0 ty 0 2 BSD ad4s1b 1073741824 512 i 1 o 0 ty 1 2 BSD ad4s1a 1073741824 512 i 0 o 1073741824 ty 7 3 MIRROR mirror/rootfs 1073741312 512 -- Andriy Gapon [-- Attachment #2 --] <
