From dnaeon at gmail.com Thu Oct 1 06:27:04 2009 From: dnaeon at gmail.com (Marin Atanasov) Date: Thu Oct 1 06:27:34 2009 Subject: gmirror issue? In-Reply-To: <4AC3E432.9010603@gmail.com> References: <4AC3E432.9010603@gmail.com> Message-ID: <4AC44BD6.9090308@gmail.com> Marin Atanasov wrote: > Hi, > > I was doing some tests under 8.0-RC1 and noticed that when I set-up a > root partition with gmirror, after the first reboot with the new > mirrored root partition the system is not able to continue the boot > process. > > The error message that is being printed is this: > > pid 63 (swapon), uid 0: exited on signal 11 > .... > pid 65: (fsck), uid 0: exited on signal 11 > Segmentation fault > Unknown error; help! > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > > > The full details about the implementation setup I'm using with > gmirror/gvinum are described here: > http://www.daemonforums.org/showthread.php?p=27010#post27010 > > Regards, > Marin > Forgot to mention that this error only occurs the first time you boot into your 8.0-RC1 system, after when you have set-up root with the new mirror filesystem. This does not apply for 7.2 Also the real issue for this is that /etc/fstab contains one new line at the end of the file like this: ^@^@^@^@ Removing that line fixes this. Another thing that I've noticed is that /boot/loader.conf content it missing. Needs to be re-created again. And then you can boot into your mirrored root partition. Does anyone know why these happen - I mean the strange entry in fstab and the empty loader.conf files? Regards, Marin From infjb at yahoo.de Sat Oct 3 14:09:44 2009 From: infjb at yahoo.de (Frank Beckmann) Date: Sat Oct 3 14:09:50 2009 Subject: Virstor provider lost metadata. Rescue possible? Message-ID: <469001.5449.qm@web28202.mail.ukl.yahoo.com> Hello, one of my virstor providers lost its metadata. It looks like the sector got filled with random data. it is the second last filled sector in that virstor. Executing the command "gvirstor list", "gvirstor status" or "sysctl -a" resulted in a kernel panic. I handcrafted the destroyed sector assuming that all chunks of that provider were used and setting the flags to 0. Now the kernel doesn't panic anymore but I get the error message: GEOM_VIRSTOR[1]: virstor_check_and_run: Invalid entry 100542 in map for vs3 GEOM_VIRSTOR[1]: virstor_check_and_run: provider_no: 25, n_components: 33 provider_chunk: 512, chunk_count 512 Provider 25 is the one which lost its metadata. The version of FreeBSD is: 7.2-RC1 Is it possible to revive that virstor to rescue some of its data? Thanks for any help. Frank From quakerdoomer at fmguy.com Sun Oct 4 11:51:54 2009 From: quakerdoomer at fmguy.com (Azim) Date: Sun Oct 4 11:52:01 2009 Subject: Issue with Device file /dev/ad4s5 Message-ID: <1254656112.2148.1337954375@webmail.messagingengine.com> I'm unsure whether this query belongs here but I would request some of you to have a look at this situation : I am facing problems with FreeBSD 8.0-RC1. It doesn't seem to be finding /dev/ad4s5 (which is my NTFS D Drive, according to Windows and DesktopBSD FreeBSD 7.1 PRE-RELEASE LiveCD) FreeBSD 8.0-RC1 does find /dev/ad4s3 which is my NTFS E Drive but just doesn't read my D Drive. I have 4 primary partitions : 1. C 78 MB (FAT32) 2. FreeBSD 10 GB (UFS) 3. E 56 GB (NTFS) 4. D 46 GB (NTFS) A more detailed Thread about the above discussion is available here : http://forums.freebsd.org/showthread.php?t=3369 ( I have been facing this problem only with 8.0 since last year (even in Test releases) All Drives are read properly on FreeBSD 7x. This could be a critical bug.) -- Azim -- http://www.fastmail.fm - Email service worth paying for. Try it for free From bugmaster at FreeBSD.org Mon Oct 5 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 5 11:07:57 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200910051106.n95B6qij088671@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/135898 geom [geom] Severe filesystem corruption - large files or l o kern/134922 geom [gmirror] [panic] kernel panic when use fdisk on disk o kern/134113 geom [geli] Problem setting secondary GELI key o kern/134044 geom [geom] gmirror(8) overwrites fs with stale data from r o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o kern/132273 geom glabel(8): [patch] failing on journaled partition f kern/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131353 geom [geom] gjournal(8) kernel lock p docs/130548 geom [patch] gjournal(8) man page is missing sysctls o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid f kern/128276 geom [gmirror] machine lock up when gmirror module is used f kern/126902 geom [geom] geom_label: kernel panic during install boot o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s f kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/122738 geom [geom] gmirror list "losts consumers" after gmirror de f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120091 geom [geom] [geli] [gjournal] geli does not prompt for pass o kern/120021 geom [geom] [panic] net-p2p/qbittorrent crashes system when o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/115856 geom [geli] ZFS thought it was degraded when it should have o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o kern/89546 geom [geom] GEOM error o kern/88601 geom [geli] geli cause kernel panic under heavy disk usage o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. s kern/73177 geom kldload geom_* causes panic due to memory exhaustion 51 problems total. From scf at FreeBSD.org Mon Oct 5 15:37:15 2009 From: scf at FreeBSD.org (Sean C. Farley) Date: Mon Oct 5 15:37:22 2009 Subject: gmirror issue? In-Reply-To: <4AC44BD6.9090308@gmail.com> References: <4AC3E432.9010603@gmail.com> <4AC44BD6.9090308@gmail.com> Message-ID: On Thu, 1 Oct 2009, Marin Atanasov wrote: > Marin Atanasov wrote: >> Hi, >> >> I was doing some tests under 8.0-RC1 and noticed that when I set-up a >> root partition with gmirror, after the first reboot with the new >> mirrored root partition the system is not able to continue the boot >> process. >> > Forgot to mention that this error only occurs the first time you boot > into your 8.0-RC1 system, after when you have set-up root with the new > mirror filesystem. This does not apply for 7.2 > > Also the real issue for this is that /etc/fstab contains one new line > at the end of the file like this: > ^@^@^@^@ While I cannot help with the other issues, I wanted to state I have seen this too. I see these characters when installing via a serial connection (using VirtualBox). They appear after every line I paste into the telnet connection (mode character). Are you doing something similar? Sean -- scf@FreeBSD.org From quakerdoomer at fmguy.com Tue Oct 6 11:21:31 2009 From: quakerdoomer at fmguy.com (Azim) Date: Tue Oct 6 11:21:53 2009 Subject: Issue with Device file /dev/ad4s5 In-Reply-To: <1254656112.2148.1337954375@webmail.messagingengine.com> References: <1254656112.2148.1337954375@webmail.messagingengine.com> Message-ID: <1254828090.26893.1338335551@webmail.messagingengine.com> Solved. I deleted the D DRIVE PARTITION completely. Now I again had free space. I Recreated the same partition with the same amount of size and now I do see /dev/ad4s5. Thanks. -- Azim -- http://www.fastmail.fm - Email service worth paying for. Try it for free From ivoras at freebsd.org Mon Oct 12 07:44:45 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Mon Oct 12 07:44:56 2009 Subject: Virstor provider lost metadata. Rescue possible? In-Reply-To: <469001.5449.qm@web28202.mail.ukl.yahoo.com> References: <469001.5449.qm@web28202.mail.ukl.yahoo.com> Message-ID: Frank Beckmann wrote: > Hello, > > one of my virstor providers lost its metadata. It looks like the sector got filled with random data. it is the second last filled sector in that virstor. Executing the command "gvirstor list", "gvirstor status" or "sysctl -a" resulted in a kernel panic. > > I handcrafted the destroyed sector assuming that all chunks of that provider were used and setting the flags to 0. Now the kernel doesn't panic anymore but I get the error message: > > GEOM_VIRSTOR[1]: virstor_check_and_run: Invalid entry 100542 in map for vs3 > GEOM_VIRSTOR[1]: virstor_check_and_run: provider_no: 25, n_components: 33 provider_chunk: 512, chunk_count 512 > > Provider 25 is the one which lost its metadata. > > The version of FreeBSD is: 7.2-RC1 > > Is it possible to revive that virstor to rescue some of its data? This is a serious problem, but as long as the first component of the virstor is alive and, as you say, only the metadata is damaged on component 25 (of 33), there is a chance. It looks like chunk_count is wrong for provider 25 - it holds the number of chunks (of default 4 MiB) on the device. You could calculate device_size/4194304 and write it in the chunk_count field of the reconstructed metadata - see if that helps (reference /sys/geom/virstor/g_virstor_md.h). You should make a backup of the first couple of chunks on the first components (the actual number depends on your virstor virtual size - 16 MiB should be enough for most) and the metadata of all other components before experimenting like this. Do you have any idea how the metadata got damaged? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20091012/c9d99873/signature.pgp From bugmaster at FreeBSD.org Mon Oct 12 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 12 11:08:07 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200910121106.n9CB6qtA036394@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/135898 geom [geom] Severe filesystem corruption - large files or l o kern/134922 geom [gmirror] [panic] kernel panic when use fdisk on disk o kern/134113 geom [geli] Problem setting secondary GELI key o kern/134044 geom [geom] gmirror(8) overwrites fs with stale data from r o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o kern/132273 geom glabel(8): [patch] failing on journaled partition f kern/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131353 geom [geom] gjournal(8) kernel lock p docs/130548 geom [patch] gjournal(8) man page is missing sysctls o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid f kern/128276 geom [gmirror] machine lock up when gmirror module is used f kern/126902 geom [geom] geom_label: kernel panic during install boot o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s f kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/122738 geom [geom] gmirror list "losts consumers" after gmirror de f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120091 geom [geom] [geli] [gjournal] geli does not prompt for pass o kern/120021 geom [geom] [panic] net-p2p/qbittorrent crashes system when o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/115856 geom [geli] ZFS thought it was degraded when it should have o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o kern/89546 geom [geom] GEOM error o kern/88601 geom [geli] geli cause kernel panic under heavy disk usage o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. s kern/73177 geom kldload geom_* causes panic due to memory exhaustion 51 problems total. From linimon at FreeBSD.org Mon Oct 12 21:22:40 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon Oct 12 21:22:51 2009 Subject: kern/139510: [geom] [2tb] gmirror disappears after boot on 2T disks Message-ID: <200910122122.n9CLMeG5090067@freefall.freebsd.org> Old Synopsis: gmirror disappears after boot on 2T disks New Synopsis: [geom] [2tb] gmirror disappears after boot on 2T disks Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Mon Oct 12 21:22:15 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=139510 From pjd at FreeBSD.org Tue Oct 13 05:48:50 2009 From: pjd at FreeBSD.org (pjd@FreeBSD.org) Date: Tue Oct 13 05:48:57 2009 Subject: kern/139510: [geom] [2tb] gmirror disappears after boot on 2T disks Message-ID: <200910130548.n9D5mnPE023375@freefall.freebsd.org> Synopsis: [geom] [2tb] gmirror disappears after boot on 2T disks State-Changed-From-To: open->feedback State-Changed-By: pjd State-Changed-When: wto 13 pa¼ 2009 05:44:07 UTC State-Changed-Why: Please add kern.geom.mirrror.debug=2 to your /boot/loader.conf and send the additional output from the boot process. I'd also need the following: # gmirror dump /dev/ad1[48] # diskinfo -v /dev/ad1[48] Responsible-Changed-From-To: freebsd-geom->pjd Responsible-Changed-By: pjd Responsible-Changed-When: wto 13 pa¼ 2009 05:44:07 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=139510 From ml at infosec.pl Thu Oct 15 21:13:11 2009 From: ml at infosec.pl (Michal) Date: Thu Oct 15 21:13:17 2009 Subject: how does geli interact with ZFS? Message-ID: <4AD79809.6010508@infosec.pl> Hello, I'm using root ZFS on geli encrypted partition (with /boot on UFS usb dongle). Does adding this extra layer between ZFS and disk can get me into troubles in case of a system crash? I mean, does it affects zfs's robustness and features like Copy-On-Write, checksumming or anything else? Or it can only get as bad as with plain ZFS and geom_eli has nothing to do with that. Michal -- "It is only when they go wrong that machines remind you how powerful they are." -Clive James From maciej at suszko.eu Fri Oct 16 05:36:05 2009 From: maciej at suszko.eu (Maciej Suszko) Date: Fri Oct 16 05:36:11 2009 Subject: how does geli interact with ZFS? In-Reply-To: <4AD79809.6010508@infosec.pl> References: <4AD79809.6010508@infosec.pl> Message-ID: <20091016070917.27e39584@suszko.eu> Michal wrote: > Hello, > > I'm using root ZFS on geli encrypted partition (with /boot on UFS usb > dongle). Does adding this extra layer between ZFS and disk can get me > into troubles in case of a system crash? > I mean, does it affects zfs's robustness and features like > Copy-On-Write, checksumming or anything else? Or it can only get as > bad as with plain ZFS and geom_eli has nothing to do with that. I use ZFS on top of geli encrypted slice for at least a year and never had problems related to such setup. In my case it's not root partition (however / is ZFS as well), it's my laptop, so I can't tell you how does it behave during long uptimes. -- regards, Maciej Suszko. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20091016/c6001e93/signature.pgp From ac at belngo.info Fri Oct 16 13:20:27 2009 From: ac at belngo.info (Alaksiej C) Date: Fri Oct 16 13:20:34 2009 Subject: how does geli interact with ZFS? In-Reply-To: <4AD79809.6010508@infosec.pl> References: <4AD79809.6010508@infosec.pl> Message-ID: <5709ce310910160620n3d3301c0x48e8ebcbe48e4931@mail.gmail.com> GELI will do its work, and ZFS will do its work. Apart from natural loss of speed, there's no difference in functioning of ZFS on bare disk or GELI provider. On Fri, Oct 16, 2009 at 12:45 AM, Michal wrote: > Hello, > > I'm using root ZFS on geli encrypted partition (with /boot on UFS usb > dongle). Does adding this extra layer between ZFS and disk can get me into > troubles in case of a system crash? > I mean, does it affects zfs's robustness and features like Copy-On-Write, > checksumming or anything else? Or it can only get as bad as with plain ZFS > and geom_eli has nothing to do with that. > > Michal > -- > "It is only when they go wrong that machines remind you how powerful they > are." -Clive James > > _______________________________________________ > freebsd-geom@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-geom > To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" > From bugmaster at FreeBSD.org Mon Oct 19 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 19 11:08:14 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200910191106.n9JB6rQI063444@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/135898 geom [geom] Severe filesystem corruption - large files or l o kern/134922 geom [gmirror] [panic] kernel panic when use fdisk on disk o kern/134113 geom [geli] Problem setting secondary GELI key o kern/134044 geom [geom] gmirror(8) overwrites fs with stale data from r o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o kern/132273 geom glabel(8): [patch] failing on journaled partition f kern/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131353 geom [geom] gjournal(8) kernel lock p docs/130548 geom [patch] gjournal(8) man page is missing sysctls o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid f kern/128276 geom [gmirror] machine lock up when gmirror module is used f kern/126902 geom [geom] geom_label: kernel panic during install boot o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s f kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/122738 geom [geom] gmirror list "losts consumers" after gmirror de f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120091 geom [geom] [geli] [gjournal] geli does not prompt for pass o kern/120021 geom [geom] [panic] net-p2p/qbittorrent crashes system when o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/115856 geom [geli] ZFS thought it was degraded when it should have o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o kern/89546 geom [geom] GEOM error o kern/88601 geom [geli] geli cause kernel panic under heavy disk usage o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. s kern/73177 geom kldload geom_* causes panic due to memory exhaustion 51 problems total. From petefrench at ticketswitch.com Tue Oct 20 15:39:44 2009 From: petefrench at ticketswitch.com (Pete French) Date: Tue Oct 20 15:39:51 2009 Subject: problems with gmirror on ggate over slow link Message-ID: I am using 7.1-STABLE from a few days ago on all amchines, but this has been going on a while. Very simply I am mirroring together a pair of discs, one local, one remote. The remote disc is accessed using ggate. If the remote diisc is actually on a very close machine - e.g. a server plugged into the same ether net - then all works fine. If I make the remote disc somewhere actually substantially further away on the nbetwork, however, then when I attach the disc it starts to rebuild the mirror but then fails a fraction of a second later thus: GEOM_MIRROR: Device mysql0: rebuilding provider ggate1a. GEOM_MIRROR: Synchronization request failed (error=5). ggate1a[WRITE(offset=1310720, length=131072)] GEOM_MIRROR: Device mysql0: provider ggate1a disconnected. GEOM_MIRROR: Device mysql0: rebuilding provider ggate1a stopped. The interesting this is that the problem is only with gmirror, not with the underlying ggate disc which remains attached and accessible. I tested this by adding a second partition (ggate1b in the example above) and mounting a UFS filesystem on that. My conjecture would be that a buffer somewhere is filling up, and instead of gmirror waiting for it, instead it just fails the write. Any ideas ? Is this actually a bug ? -pete. From nonsolosoft at diff.org Wed Oct 21 16:41:16 2009 From: nonsolosoft at diff.org (Ferruccio Zamuner) Date: Wed Oct 21 16:41:22 2009 Subject: gvirstor over gmirror Message-ID: <4ADF3455.9070905@diff.org> Hello, I'm trying to get a virstor over gmirrored slices from different devices: free# gmirror list gmir1 Geom name: gmir1 State: COMPLETE Components: 2 Balance: split Slice: 4096 Flags: NOFAILSYNC GenID: 0 SyncID: 1 ID: 1104038309 Providers: 1. Name: mirror/gmir1 Mediasize: 237291069952 (221G) Sectorsize: 512 Mode: r0w0e0 Consumers: 1. Name: ad6s1 Mediasize: 237291070464 (221G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: NONE GenID: 0 SyncID: 1 ID: 2917203718 2. Name: ad7s1 Mediasize: 237291070464 (221G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 1 Flags: NONE GenID: 0 SyncID: 1 ID: 756437562 I thought to create a gvirstor with gmir1 at start and to connect in next future more mirrored disks but: geom virstor seems to loose metadata at reboot even with -h. gvirstor label -v myvirstor /dev/ad4 /dev/ad6 Is geom virstor stable? disklabel -w /dev/virstor/myvirstor I would like to add over gvirstor also a gjournal: gjournal label -h /dev/virstor/myvirstora newfs -J /dev/virstor/myvirstora.journal mount /dev/virstor/myvirstora.journal /mnt Everything seems to work but for example cpdup of large partition (200Gb) on /mnt makes cpdup to hang in suspfs state after 40Gb. I'm using it on a FreeBSD 7.1-stable and I'll upgrade as soon at possible at 8-RC. Bye, \ferz PS: using it in remote seems a pain yet. From ivoras at freebsd.org Thu Oct 22 09:32:34 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Thu Oct 22 09:32:40 2009 Subject: gvirstor over gmirror In-Reply-To: <4ADF3455.9070905@diff.org> References: <4ADF3455.9070905@diff.org> Message-ID: Ferruccio Zamuner wrote: > Hello, > > I'm trying to get a virstor over gmirrored slices from different devices: > > free# gmirror list gmir1 > Geom name: gmir1 > State: COMPLETE > Components: 2 > Balance: split > Slice: 4096 > Flags: NOFAILSYNC > GenID: 0 > SyncID: 1 > ID: 1104038309 > Providers: > 1. Name: mirror/gmir1 > Mediasize: 237291069952 (221G) > Sectorsize: 512 > Mode: r0w0e0 > Consumers: > 1. Name: ad6s1 > Mediasize: 237291070464 (221G) > Sectorsize: 512 > Mode: r1w1e1 > State: ACTIVE > Priority: 0 > Flags: NONE > GenID: 0 > SyncID: 1 > ID: 2917203718 > 2. Name: ad7s1 > Mediasize: 237291070464 (221G) > Sectorsize: 512 > Mode: r1w1e1 > State: ACTIVE > Priority: 1 > Flags: NONE > GenID: 0 > SyncID: 1 > ID: 756437562 > > I thought to create a gvirstor with gmir1 at start and to connect in > next future more mirrored disks but: > geom virstor seems to loose metadata at reboot even with -h. > > gvirstor label -v myvirstor /dev/ad4 /dev/ad6 Is this command above within the same setup as the mirror creation above? Are you really trying to use the ad6 device twice? From gavin at FreeBSD.org Thu Oct 22 21:31:31 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Thu Oct 22 21:31:44 2009 Subject: kern/139847: [geom_mbr] load/unload causes system to hang Message-ID: <200910222131.n9MLVVJf069205@freefall.freebsd.org> Old Synopsis: gem_mbr load/unload causes system to hang New Synopsis: [geom_mbr] load/unload causes system to hang Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: gavin Responsible-Changed-When: Thu Oct 22 21:20:59 UTC 2009 Responsible-Changed-Why: Over to maintainer(s) http://www.freebsd.org/cgi/query-pr.cgi?pr=139847 From admin at lissyara.su Fri Oct 23 05:30:03 2009 From: admin at lissyara.su (Alex Keda) Date: Fri Oct 23 05:30:09 2009 Subject: kern/113885: [gmirror] [patch] improved gmirror balance algorithm Message-ID: <200910230530.n9N5U2cM076154@freefall.freebsd.org> The following reply was made to PR kern/113885; it has been noted by GNATS. From: Alex Keda To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/113885: [gmirror] [patch] improved gmirror balance algorithm Date: Fri, 23 Oct 2009 09:20:00 +0400 so, where is maintainer? may be somebody commit it? very useful feature. From mwisnicki+freebsd at gmail.com Sun Oct 25 01:00:10 2009 From: mwisnicki+freebsd at gmail.com (Marcin Wisnicki) Date: Sun Oct 25 01:00:18 2009 Subject: Infinite loop in GEOM_JOURNAL when device dies Message-ID: Hello, My system looks like this: FreeBSD 7.2-STABLE #3: Sat Oct 17 20:50:32 CEST 2009 da1 at umass-sim1 bus 1 target 0 lun 0 da1: Fixed Direct Access SCSI-4 device da1: 40.000MB/s transfers da1: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) GEOM_JOURNAL: Journal 584260361: da1p1 contains data. GEOM_JOURNAL: Journal 584260361: da1p1 contains journal. GEOM_JOURNAL: Journal da1p1 consistent. /dev/ufs/tank1u on /vol/store/tank1 (ufs, asynchronous, local, noatime, acls, gjournal) Device da1 is an external WD Passport hdd connected to a powered usb hub. UFS filesystem on da1p1.journal is labeled "tank1u". Unfortunately from time to time (1 day to many weeks after startup) it stops working: umass1: BBB reset failed, IOERROR umass1: BBB bulk-in clear stall failed, IOERROR umass1: BBB bulk-out clear stall failed, IOERROR umass1: BBB reset failed, IOERROR umass1: BBB bulk-in clear stall failed, IOERROR umass1: BBB bulk-out clear stall failed, IOERROR umass1: BBB reset failed, IOERROR umass1: at uhub4 port 2 (addr 4) disconnected GEOM_JOURNAL: Error while reading data from da1p1 (error=22). At this point I usually get: panic: ufs_dirbad: /vol/store/tank1: bad dir ino 2 at offset 0: mangled entry Which is unfortunate but at least system will recover itself. However today it didn't panic but instead following happened: (da1:umass-sim1:1:0:0): lost device GEOM_JOURNAL: Lost provider da1p1. GEOM_JOURNAL: Cannot destroy journal da1p1 (error=16). Destroy it manually after last close. System was still working but when I've tried doing "ls /vol/store", I got this on serial console: (da1:umass-sim1:1:0:0): lost device GEOM_JOURNAL: Lost provider da1p1. GEOM_JOURNAL: Cannot destroy journal da1p1 (error=16). Destroy it manually after last close. GEOM_JOURNAL: Error while reading data from da1p1 (error=6). GEOM_JOURNAL: Error while reading data from da1p1 (error=6). GEOM_JOURNAL: Error while reading data from da1p1 (error=6). GEOM_JOURNAL: Error while reading data from da1p1 (error=6). GEOM_JOURNAL: Error while reading data from da1p1 (error=6). GEOM_JOURNAL: Error while reading data from da1p1 (error=6). GEOM_JOURNAL: Error while reading data from da1p1 (error=6). GEOM_JOURNAL: Error while reading data from da1p1 (error=6). g_vfs_done():ufs/tank1u[READ(offset=254163107960586240, length=16384)]error = 5 bad block 9261869914, ino 432515 g_vfs_done():ufs/tank1u[READ(offset=7447739922700238848, length=16384)]error = 5 g_vfs_done():ufs/tank1u[READ(offset=-9220267016017932288, length=16384)]error = 5 [skip] g_vfs_done():ufs/tank1u[READ(offset=-9220267016017932288, length=16384)]error = 5 g_vfs_done():ufs/tank1u[READ(offset=-9220267016017932288, length=16384)]error = 5 g_vfs_done():ufs/tank1u[READ(o g_vfs_done():ufs/tank1u[READ(offset=-9220267016017932288, length=16384)]error = 5 [skip] g_vfs_done():ufs/tank1u[READ(offset=-9220267016017932288, length=16384)]error = 5 g_vfs_done():ufs/tank1u[READ(o 17932288, length=16384)]error = 5 g_vfs_done():ufs/tank1u[READ(offset=-9220267016017932288, length=16384)]error = 5 [skip many pages] g_vfs_done():ufs/tank1u[READ(offset=-9220267016017932288, length=16384)]error = 5 g_vfs_done():ufs/tank1u[READ(of ength=16384)]error = 5 g_vfs_done():ufs/tank1u[READ(offset=18968309645312, length=16384)]error = 5 [infinite loop ?] (I have unmangled and reformatted output for readability) While I could ping the machine nothing in userland worked and console was constantly printing geom errors and wouldn't accept any input, so I had to press reset button. I think that gjournal should somehow destroy itself if underlying provider dies - just like a provider of unplugged disk. UFS is supposed to handle disappearing devices for some time now and even while this does not really work yet a panic is better than an infinite loop. SMART log shows some READ DMA EXT errors but no permanent damage - I have smartd doing periodic testing and it completes without failure and all error counters remain at 0. BTW the drive worked fine in Windows, it just "stalled" for a moment sometimes. From gavin at FreeBSD.org Sun Oct 25 20:07:16 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Sun Oct 25 20:07:27 2009 Subject: bin/139970: gpart(8): WARNS=6 cleanups in bin/geom/class/part Message-ID: <200910252007.n9PK7G8Z033584@freefall.freebsd.org> Old Synopsis: sbin/geom/class/part: WARNS6 cleanup New Synopsis: gpart(8): WARNS=6 cleanups in bin/geom/class/part Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: gavin Responsible-Changed-When: Sun Oct 25 20:05:41 UTC 2009 Responsible-Changed-Why: Over to maintainer(s) http://www.freebsd.org/cgi/query-pr.cgi?pr=139970 From lulf at FreeBSD.org Mon Oct 26 07:49:48 2009 From: lulf at FreeBSD.org (lulf@FreeBSD.org) Date: Mon Oct 26 07:49:54 2009 Subject: bin/139970: gpart(8): WARNS=6 cleanups in bin/geom/class/part Message-ID: <200910260749.n9Q7nlbi066838@freefall.freebsd.org> Synopsis: gpart(8): WARNS=6 cleanups in bin/geom/class/part State-Changed-From-To: open->closed State-Changed-By: lulf State-Changed-When: Mon Oct 26 07:49:14 UTC 2009 State-Changed-Why: - Patch committed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=139970 From dfilter at FreeBSD.ORG Mon Oct 26 07:50:03 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Mon Oct 26 07:50:09 2009 Subject: bin/139970: commit references a PR Message-ID: <200910260750.n9Q7o2a9066902@freefall.freebsd.org> The following reply was made to PR bin/139970; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/139970: commit references a PR Date: Mon, 26 Oct 2009 07:43:56 +0000 (UTC) Author: lulf Date: Mon Oct 26 07:43:41 2009 New Revision: 198478 URL: http://svn.freebsd.org/changeset/base/198478 Log: - Initialize variable in order to avoid GCC warning and enable WARNS=6. PR: bin/139970 Submitted by: Ulrich Spörlein Modified: head/sbin/geom/class/part/Makefile head/sbin/geom/class/part/geom_part.c Modified: head/sbin/geom/class/part/Makefile ============================================================================== --- head/sbin/geom/class/part/Makefile Mon Oct 26 06:51:20 2009 (r198477) +++ head/sbin/geom/class/part/Makefile Mon Oct 26 07:43:41 2009 (r198478) @@ -6,6 +6,4 @@ CLASS= part LDADD= -lutil -WARNS?= 4 - .include Modified: head/sbin/geom/class/part/geom_part.c ============================================================================== --- head/sbin/geom/class/part/geom_part.c Mon Oct 26 06:51:20 2009 (r198477) +++ head/sbin/geom/class/part/geom_part.c Mon Oct 26 07:43:41 2009 (r198478) @@ -192,6 +192,7 @@ find_provider(struct ggeom *gp, unsigned unsigned long long sector, bestsector; bestpp = NULL; + bestsector = 0; LIST_FOREACH(pp, &gp->lg_provider, lg_provider) { s = find_provcfg(pp, "start"); if (s == NULL) { _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From bugmaster at FreeBSD.org Mon Oct 26 11:06:59 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 26 11:08:12 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200910261106.n9QB6ws7043761@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139847 geom [geom_mbr] load/unload causes system to hang o kern/135898 geom [geom] Severe filesystem corruption - large files or l o kern/134922 geom [gmirror] [panic] kernel panic when use fdisk on disk o kern/134113 geom [geli] Problem setting secondary GELI key o kern/134044 geom [geom] gmirror(8) overwrites fs with stale data from r o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o kern/132273 geom glabel(8): [patch] failing on journaled partition f kern/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131353 geom [geom] gjournal(8) kernel lock p docs/130548 geom [patch] gjournal(8) man page is missing sysctls o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid f kern/128276 geom [gmirror] machine lock up when gmirror module is used f kern/126902 geom [geom] geom_label: kernel panic during install boot o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s f kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/122738 geom [geom] gmirror list "losts consumers" after gmirror de f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120091 geom [geom] [geli] [gjournal] geli does not prompt for pass o kern/120021 geom [geom] [panic] net-p2p/qbittorrent crashes system when o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/115856 geom [geli] ZFS thought it was degraded when it should have o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o kern/89546 geom [geom] GEOM error o kern/88601 geom [geli] geli cause kernel panic under heavy disk usage o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. s kern/73177 geom kldload geom_* causes panic due to memory exhaustion 52 problems total. From hsu at bbnetworks.net Wed Oct 28 18:47:38 2009 From: hsu at bbnetworks.net (Heikki Suonsivu) Date: Wed Oct 28 18:47:45 2009 Subject: kern/139510: [geom] [2tb] gmirror disappears after boot on 2T disks In-Reply-To: <200910130548.n9D5mnPE023375@freefall.freebsd.org> References: <200910130548.n9D5mnPE023375@freefall.freebsd.org> Message-ID: <4AE88925.4020302@bbnetworks.net> pjd@FreeBSD.org wrote: > Synopsis: [geom] [2tb] gmirror disappears after boot on 2T disks > > State-Changed-From-To: open->feedback > State-Changed-By: pjd > State-Changed-When: wto 13 pa? 2009 05:44:07 UTC > State-Changed-Why: > Please add kern.geom.mirrror.debug=2 to your /boot/loader.conf and send > the additional output from the boot process. See below for boot messages > I'd also need the following: > > # gmirror dump /dev/ad1[48] gmirror dump /dev/ad1[48] Can't read metadata from /dev/ad14: Invalid argument. Can't read metadata from /dev/ad18: Invalid argument. gmirror: Not fully done. > # diskinfo -v /dev/ad1[48] diskinfo -v /dev/ad1[48] /dev/ad14 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:WD-WCAVY0207680 # Disk ident. /dev/ad18 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:WD-WCAVY0226353 # Disk ident. > > Responsible-Changed-From-To: freebsd-geom->pjd > Responsible-Changed-By: pjd > Responsible-Changed-When: wto 13 pa? 2009 05:44:07 UTC > Responsible-Changed-Why: > I'll take this one. Blow the boot messages: Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-STABLE #0: Fri Aug 21 20:00:56 EEST 2009 root@news.bbnetworks.net:/usr/obj/usr/src/sys/BBNETWORKS7NEWS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (1809.28-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20ff2 Stepping = 2 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 usable memory = 2133803008 (2034 MB) avail memory = 2057379840 (1962 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7fef0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xdc004000-0xdc004fff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfeb00000-0xfeb000ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: on usb1 uhub1: 10 ports with 10 removable, self powered pci0: at device 4.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xdc002000-0xdc002fff irq 21 at device 7.0 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xdc001000-0xdc001fff irq 22 at device 8.0 on pci0 atapci2: [ITHREAD] ata4: on atapci2 ata4: [ITHREAD] ata5: on atapci2 ata5: [ITHREAD] pcib1: at device 9.0 on pci0 pci5: on pcib1 atapci3: port 0x8000-0x8007,0x8400-0x8403,0x8800-0x8807,0x8c00-0x8c03,0x9000-0x900f mem 0xdb008000-0xdb0083ff irq 19 at device 10.0 on pci5 atapci3: [ITHREAD] ata6: on atapci3 ata6: [ITHREAD] ata7: on atapci3 ata7: [ITHREAD] ata8: on atapci3 ata8: [ITHREAD] ata9: on atapci3 ata9: [ITHREAD] fwohci0: mem 0xdb009000-0xdb0097ff,0xdb000000-0xdb003fff irq 16 at device 11.0 on pci5 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:11:d8:00:00:5e:cf:a9 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x7c314000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:11:d8:5e:cf:a9 fwe0: Ethernet address: 02:11:d8:5e:cf:a9 fwip0: on firewire0 fwip0: Firewire address: 00:11:d8:00:00:5e:cf:a9 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode skc0: port 0x9400-0x94ff mem 0xdb004000-0xdb007fff irq 17 at device 12.0 on pci5 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: on skc0 sk0: Ethernet address: 00:13:d4:b8:48:56 miibus0: on sk0 e1000phy0: PHY 0 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto skc0: [ITHREAD] nfe0: port 0xb000-0xb007 mem 0xdc000000-0xdc000fff irq 23 at device 10.0 on pci0 miibus1: on nfe0 e1000phy1: PHY 1 on miibus1 e1000phy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nfe0: Ethernet address: 00:13:d4:b8:3c:b8 nfe0: [FILTER] pcib2: at device 11.0 on pci0 pci4: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 pcib4: at device 13.0 on pci0 pci2: on pcib4 pcib5: at device 14.0 on pci0 pci1: on pcib5 vgapci0: port 0xa000-0xa0ff mem 0xd0000000-0xd7ffffff,0xd9000000-0xd900ffff irq 18 at device 0.0 on pci1 vgapci1: mem 0xd9010000-0xd901ffff at device 0.1 on pci1 acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] cpu0: on acpi0 powernow0: on cpu0 device_attach: powernow0 attach returned 6 orm0: at iomem 0xc0000-0xcffff,0xd0000-0xd3fff,0xd4000-0xd8fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1809281102 Hz quality 800 Timecounters tick every 1.000 msec IP Filter: v4.1.28 initialized. Default = pass all, Logging = enabled ipfw2 (+ipv6) initialized, divert enabled, nat loadable, rule-based forwarding enabled, default to accept, logging limited to 1000 packets/entry byfirewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) default ad4: 953869MB at ata2-master SATA150 ad6: 239372MB at ata3-master SATA150 GEOM_MIRROR[2]: Tasting ad4. magic: GEOM::MIRROR version: 4 name: overview mid: 1187277655 did: 3503848280 all: 2 genid: 0 syncid: 1 priority: 0 slice: 2048 balance: round-robin mediasize: 1000204885504 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: NONE hcprovider: provsize: 1000204886016 MD5 hash: cd509d68698df4e4ecf090074f95e1b1 GEOM_MIRROR[1]: Creating device overview (id=1187277655). GEOM_MIRROR[1]: Device overview created (2 components, id=1187277655). GEOM_MIRROR[1]: root_mount_hold 0xffffff0001715140 GEOM_MIRROR[1]: Adding disk ad4 to overview. GEOM_MIRROR[2]: Adding disk ad4. GEOM_MIRROR[2]: Disk ad4 connected. GEOM_MIRROR[1]: Disk ad4 state changed from NONE to NEW (device overview). GEOM_MIRROR[1]: Device overview: provider ad4 detected. GEOM_MIRROR[2]: Tasting ad4s1. ad8: 239372MB at ata4-master SATA150 GEOM_MIRROR[2]: Tasting ad6. magic: GEOM::MIRROR version: 4 name: boot mid: 1589248060 did: 3950302506 all: 2 genid: 0 syncid: 1 priority: 0 slice: 2048 balance: prefer mediasize: 251000192512 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: NONE hcprovider: provsize: 251000193024 MD5 hash: 0ff0b87201e3ff9332d004523c6a7d87 GEOM_MIRROR[1]: Creating device boot (id=1589248060). GEOM_MIRROR[1]: Device boot created (2 components, id=1589248060). GEOM_MIRROR[1]: root_mount_hold 0xffffff000169c840 GEOM_MIRROR[1]: Adding disk ad6 to boot. GEOM_MIRROR[2]: Adding disk ad6. GEOM_MIRROR[2]: Disk ad6 connected. GEOM_MIRROR[1]: Disk ad6 state changed from NONE to NEW (device boot). GEOM_MIRROR[1]: Device boot: provider ad6 detected. GEOM_MIRROR[2]: Tasting ad6s1. GEOM_MIRROR[2]: Tasting ad8. magic: GEOM::MIRROR version: 4 name: boot mid: 1589248060 did: 2432525573 all: 2 genid: 0 syncid: 1 priority: 0 slice: 2048 balance: prefer mediasize: 251000192512 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: NONE hcprovider: provsize: 251000193024 MD5 hash: 9209d0183abf207e563c699edf7b2755 GEOM_MIRROR[1]: Adding disk ad8 to boot. GEOM_MIRROR[2]: Adding disk ad8. GEOM_MIRROR[2]: Disk ad8 connected. GEOM_MIRROR[1]: Disk ad8 state changed from NONE to NEW (device boot). GEOM_MIRROR[1]: Device boot: provider ad8 detected. GEOM_MIRROR[1]: Device boot state changed from STARTING to RUNNING. GEOM_MIRROR[1]: Disk ad8 state changed from NEW to ACTIVE (device boot). GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Device boot: provider ad8 activated. GEOM_MIRROR[1]: Disk ad6 state changed from NEW to ACTIVE (device boot). GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Device boot: provider ad6 activated. GEOM_MIRROR[0]: Device mirror/boot launched (2/2). GEOM_MIRROR[1]: root_mount_rel[2379] 0xffffff000169c840 GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Tasting mirror/boot. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Tasting ad8s1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Tasting mirror/boots1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. ad10: 953869MB at ata5-master SATA150 GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Tasting mirror/boots1a. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. ad12: 1907729MB at ata6-master SATA150 GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Tasting mirror/boots1b. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Tasting mirror/boots1c. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Tasting mirror/boots1d. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-2. GEOM_MIRROR[2]: Tasting ufsid/4aa483631b551094. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-3. GEOM_MIRROR[2]: Tasting ufsid/4aa483acdab38651. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-3. ad14: 1907729MB at ata7-master SATA150 GEOM_MIRROR[2]: Tasting ad10. magic: GEOM::MIRROR version: 4 name: overview mid: 1187277655 did: 3458568220 all: 2 genid: 0 syncid: 1 priority: 1 slice: 2048 balance: round-robin mediasize: 1000204885504 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: NONE hcprovider: provsize: 1000204886016 MD5 hash: 1cb0842fd09935edb9b881430bb0a8af GEOM_MIRROR[1]: Adding disk ad10 to overview. GEOM_MIRROR[2]: Adding disk ad10. GEOM_MIRROR[2]: Disk ad10 connected. GEOM_MIRROR[1]: Disk ad10 state changed from NONE to NEW (device overview). GEOM_MIRROR[1]: Device overview: provider ad10 detected. GEOM_MIRROR[1]: Device overview state changed from STARTING to RUNNING. GEOM_MIRROR[1]: Disk ad10 state changed from NEW to ACTIVE (device overview). GEOM_MIRROR[2]: Metadata on ad10 updated. GEOM_MIRROR[1]: Device overview: provider ad10 activated. GEOM_MIRROR[1]: Disk ad4 state changed from NEW to ACTIVE (device overview). GEOM_MIRROR[2]: Metadata on ad4 updated. GEOM_MIRROR[1]: Device overview: provider ad4 activated. GEOM_MIRROR[0]: Device mirror/overview launched (2/2). GEOM_MIRROR[1]: root_mount_rel[2379] 0xffffff0001715140 GEOM_MIRROR[2]: Tasting ad12. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Tasting mirror/overview. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Tasting ad10s1. GEOM_MIRROR[2]: Tasting ad12s1. GEOM_MIRROR[2]: Tasting ad14. GEOM_MIRROR[2]: Tasting ufsid/4aa14bd1691027ec. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. ad16: 1907729MB at ata8-master SATA150 GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Tasting mirror/overviews1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Tasting ad12s1c. GEOM_MIRROR[2]: Tasting ad12s1d. GEOM_MIRROR[2]: Tasting ad14s1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Tasting ufsid/4aa14bd1691027ecs1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Tasting mirror/overviews1c. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Tasting mirror/overviews1d. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Tasting ufsid/4a8df25801f4e1a4. GEOM_MIRROR[2]: Tasting ad14s1c. GEOM_MIRROR[2]: Tasting ad14s1d. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Tasting ufsid/4aa14bd1691027ecs1c. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Tasting ufsid/4aa14bd1691027ecs1d. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Tasting ad16. GEOM_MIRROR[2]: Tasting ufsid/4aa14ee7e70e19a6. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. ad18: 1907729MB at ata9-master SATA150 GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Tasting ufsid/4ac0c89000c1a133. GEOM_MIRROR[2]: Tasting ad16s1. GEOM_MIRROR[2]: Tasting ad16s1c. GEOM_MIRROR[2]: Tasting ad16s1d. GEOM_MIRROR[2]: Tasting ad18. GEOM_MIRROR[2]: Tasting ufsid/4a8df299752d8b2f. GEOM_MIRROR[2]: Tasting ad18s1. GEOM_MIRROR[2]: Tasting ad18s1c. GEOM_MIRROR[2]: Tasting ad18s1d. Trying to mount root from ufs:/dev/mirror/boots1a GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/boot: r0w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[1]: Kernel dump will go to ad8. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w1e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r0w1e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r0w-1e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Tasting mirror/boots1a. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Tasting ufsid/4aa483631b551094. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r0w1e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r0w-1e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r0w1e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Tasting mirror/boots1d. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e0. GEOM_MIRROR[2]: Tasting ufsid/4aa483acdab38651. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/boot: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r0w-1e-2. GEOM_MIRROR[2]: Tasting ad12. GEOM_MIRROR[2]: Tasting ad12s1. GEOM_MIRROR[2]: Tasting ad12s1d. GEOM_MIRROR[2]: Tasting ad16. GEOM_MIRROR[2]: Tasting ad16s1. GEOM_MIRROR[2]: Tasting ad16s1d. GEOM_MIRROR[2]: Tasting ad14. GEOM_MIRROR[2]: Tasting ad14s1. GEOM_MIRROR[2]: Tasting ad14s1d. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Tasting mirror/overview. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Tasting mirror/overviews1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e0. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Tasting mirror/overviews1d. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Tasting ufsid/4a8df25801f4e1a4. GEOM_MIRROR[2]: Tasting ufsid/4a8df299752d8b2f. GEOM_MIRROR[2]: Tasting ufsid/4ac0c89000c1a133. GEOM_MIRROR[2]: Tasting ufsid/4aa14bd1691027ec. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e1. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-1. GEOM_MIRROR[2]: Tasting ufsid/4aa14ee7e70e19a6. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Tasting ufsid/4aa14bd1691027ecs1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e2. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-2. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Tasting ufsid/4aa14bd1691027ecs1c. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Tasting ufsid/4aa14bd1691027ecs1d. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/overview: r1w0e3. GEOM_MIRROR[2]: Access request for mirror/overview: r-1w0e-3. GEOM_MIRROR[2]: Access request for mirror/boot: r0w1e1. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[2]: Access request for mirror/boot: r1w1e1. GEOM_MIRROR[2]: Access request for mirror/overview: r1w1e3. GEOM_MIRROR[1]: Disk ad10 (device overview) marked as dirty. GEOM_MIRROR[2]: Metadata on ad10 updated. GEOM_MIRROR[1]: Disk ad4 (device overview) marked as dirty. GEOM_MIRROR[2]: Metadata on ad4 updated. GEOM_MIRROR[2]: Access request for mirror/boot: r1w1e0. GEOM_MIRROR[2]: Access request for mirror/boot: r-1w-1e0. sk0: link state changed to UP GEOM_MIRROR[1]: Disk ad10 (device overview) marked as clean. GEOM_MIRROR[2]: Metadata on ad10 updated. GEOM_MIRROR[1]: Disk ad4 (device overview) marked as clean. GEOM_MIRROR[2]: Metadata on ad4 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as clean. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[1]: Disk ad8 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad8 updated. GEOM_MIRROR[1]: Disk ad6 (device boot) marked as dirty. GEOM_MIRROR[2]: Metadata on ad6 updated. From thomas.e.zander at googlemail.com Sat Oct 31 14:10:04 2009 From: thomas.e.zander at googlemail.com (Thomas Zander) Date: Sat Oct 31 14:10:10 2009 Subject: kern/134113: [geli] Problem setting secondary GELI key Message-ID: <200910311410.n9VEA3Hb029673@freefall.freebsd.org> The following reply was made to PR kern/134113; it has been noted by GNATS. From: Thomas Zander To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/134113: [geli] Problem setting secondary GELI key Date: Sat, 31 Oct 2009 15:04:55 +0100 I can confirm that this pr applies to 8.0RC2 as well. Is anyone working on this? I am happy to test patches. Riggs From gavin at FreeBSD.org Sat Oct 31 15:30:05 2009 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Sat Oct 31 15:30:14 2009 Subject: kern/139847: [geom_mbr] load/unload causes system to hang Message-ID: <200910311530.n9VFU40T099853@freefall.freebsd.org> The following reply was made to PR kern/139847; it has been noted by GNATS. From: Gavin Atkinson To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/139847: [geom_mbr] load/unload causes system to hang Date: Sat, 31 Oct 2009 15:28:11 +0000 (GMT) I can (accidentally) confirm that this bug exists. :-( FreeBSD rho.york.ac.uk 9.0-CURRENT FreeBSD 9.0-CURRENT #5: Mon Oct 19 20:34:46 BST 2009 root@rho.york.ac.uk:/usr/obj/usr/src/sys/RHO i386 "kldunload geom_mbr" hangs, with the backtrace below. It hangs while holding the GEOM topology lock and the kernel linker lock, which is presumably the cause of the hang reported by the original submitter (which I haven't witnessed yet but expect to soon...) KDB: enter: manual escape to debugger [thread pid 12 tid 100024 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> tr 54907 Tracing pid 54907 tid 100193 td 0xc5666690 sched_switch(c5666690,0,104,191,7439752a,...) at sched_switch+0x418 mi_switch(104,0,c0cb4ff6,1d6,4c,...) at mi_switch+0x200 sleepq_switch(c5666690,0,c0cb4ff6,26e,0,...) at sleepq_switch+0x15f sleepq_timedwait(cac08280,4c,c0ca78f4,0,0,...) at sleepq_timedwait+0x6b _sleep(cac08280,0,4c,c0ca78f4,3e8,...) at _sleep+0x339 g_waitfor_event(c08413f0,c5105090,2,0,ca656980,...) at g_waitfor_event+0x9c g_modevent(ca656980,1,cb8a6440,109,0,...) at g_modevent+0x14f module_unload(ca656980,c0cad345,274,271,c0884be6,...) at module_unload+0x43 linker_file_unload(c62b4000,0,c0cad345,42c,cb8a3000,...) at linker_file_unload+0x15e kern_kldunload(c5666690,a,0,e79dcd2c,c0be0953,...) at kern_kldunload+0xd5 kldunloadf(c5666690,e79dccf8,8,c0cb7d91,c0d9f210,...) at kldunloadf+0x2b syscall(e79dcd38) at syscall+0x2d3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 0x280d62fb, esp = 0xbfbfe48c, ebp = 0xbfbfecd8 --- db> db> sh alllocks Process 58972 (procstat) thread 0xc53ee8c0 (100089) shared sx sysctl lock (sysctl lock) r = 0 (0xc0e25844) locked @ /usr/src/sys/kern/kern_sysctl.c:1521 Process 54907 (kldunload) thread 0xc5666690 (100193) exclusive sx kernel linker (kernel linker) r = 0 (0xc0e23f98) locked @ /usr/src/sys/kern/kern_linker.c:1068 Process 2 (g_event) thread 0xc4e07000 (100011) exclusive sx GEOM topology (GEOM topology) r = 0 (0xc0e23508) locked @ /usr/src/sys/geom/geom_event.c:185 Process 12 (intr) thread 0xc4e07d20 (100024) exclusive sleep mutex Giant (Giant) r = 1 (0xc0e25130) locked @ /usr/src/sys/dev/usb/usb_transfer.c:2954 db> (Giant held by USB due to escaping to debugger via USB keyboard. The sysctl lock is held because I ran "procstat -kk" on the kldunload process, which also wedged waiting for the kernel linker lock.) Gavin