From jh at FreeBSD.org Sun Nov 1 08:30:05 2009 From: jh at FreeBSD.org (Jaakko Heinonen) Date: Sun Nov 1 08:30:12 2009 Subject: kern/139847: [geom_mbr] load/unload causes system to hang Message-ID: <200911010830.nA18U4ko012329@freefall.freebsd.org> The following reply was made to PR kern/139847; it has been noted by GNATS. From: Jaakko Heinonen To: Gavin Atkinson , yuri@tsoft.com Cc: bug-followup@FreeBSD.org Subject: Re: kern/139847: [geom_mbr] load/unload causes system to hang Date: Sun, 1 Nov 2009 10:29:29 +0200 Hi, On 2009-10-31, Gavin Atkinson wrote: > "kldunload geom_mbr" hangs, with the backtrace below. It hangs while > holding the GEOM topology lock and the kernel linker lock, which is I have described this GEOM problem here: http://docs.freebsd.org/cgi/mid.cgi?20081216210311.GA5229 (You are seeing the deadlock described in section 2.) There's also a link to a patch you could try. -- Jaakko From bugmaster at FreeBSD.org Mon Nov 2 11:06:55 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 2 11:08:09 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200911021106.nA2B6stQ033591@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 lucas at wingedleopard.net Tue Nov 3 03:31:10 2009 From: lucas at wingedleopard.net (Lucas Reddinger) Date: Tue Nov 3 03:31:17 2009 Subject: kern/120231: [geom] GEOM_CONCAT error adding second drive Message-ID: http://www.freebsd.org/cgi/query-pr.cgi?pr=120231 I'm having the same problem, but I'm wondering about an alternative workaround. Is it possible to remove all partitions, only leaving ``c'', so that geom will only attempt to add the whole disk and not any other partition as well? For example, I have: atlas% sudo bsdlabel /dev/stripe/gs9 # /dev/stripe/gs9: 8 partitions: #??????? size?? offset??? fstype?? [fsize bsize bps/cpg] ? a: 2500527423?????? 16??? 4.2BSD???? 2048 16384 28552 ? c: 2500527439??????? 0??? unused??????? 0???? 0???????? # "raw" part, don't edit Can I remove the ``a'' partition, only leaving ``c'', so that geom only tries to add /dev/stripe/gs9 to /dev/concat/gc9, and not /dev/stripe/gs9a as well? GEOM_CONCAT: Device gc9 created (id=3563333761). GEOM_CONCAT: Disk stripe/gs9 attached to gc9. GEOM_CONCAT: Device gc9 activated. GEOM_LABEL: Label for provider stripe/gs9 is ufsid/4aece8d6fd9650d6. GEOM_LABEL: Label for provider stripe/gs9a is ufsid/4aeceb954b2a81d6. GEOM_CONCAT: Cannot add disk ufsid/4aece8d6fd9650d6 to gc9 (error=17). I appreciate any responses. Thank you! Lucas Reddinger From lucas at wingedleopard.net Tue Nov 3 03:40:05 2009 From: lucas at wingedleopard.net (Lucas Reddinger) Date: Tue Nov 3 03:40:11 2009 Subject: kern/120231: [geom] GEOM_CONCAT error adding second drive Message-ID: <200911030340.nA33e4nw098443@freefall.freebsd.org> The following reply was made to PR kern/120231; it has been noted by GNATS. From: Lucas Reddinger To: freebsd-geom@freebsd.org, bug-followup@freebsd.org, taosecurity@gmail.com Cc: wlw-atlas Subject: Re: kern/120231: [geom] GEOM_CONCAT error adding second drive Date: Mon, 2 Nov 2009 20:01:06 -0700 http://www.freebsd.org/cgi/query-pr.cgi?pr=3D120231 I'm having the same problem, but I'm wondering about an alternative workaround. Is it possible to remove all partitions, only leaving ``c'', so that geom will only attempt to add the whole disk and not any other partition as well? For example, I have: atlas% sudo bsdlabel /dev/stripe/gs9 # /dev/stripe/gs9: 8 partitions: #=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 size=C2=A0=C2=A0 offset=C2=A0= =C2=A0=C2=A0 fstype=C2=A0=C2=A0 [fsize bsize bps/cpg] =C2=A0 a: 2500527423=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 16=C2=A0=C2=A0=C2= =A0 4.2BSD=C2=A0=C2=A0=C2=A0=C2=A0 2048 16384 28552 =C2=A0 c: 2500527439=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0=C2= =A0=C2=A0 unused=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2= =A0=C2=A0 0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 # "raw" part, don't edit Can I remove the ``a'' partition, only leaving ``c'', so that geom only tries to add /dev/stripe/gs9 to /dev/concat/gc9, and not /dev/stripe/gs9a as well? GEOM_CONCAT: Device gc9 created (id=3D3563333761). GEOM_CONCAT: Disk stripe/gs9 attached to gc9. GEOM_CONCAT: Device gc9 activated. GEOM_LABEL: Label for provider stripe/gs9 is ufsid/4aece8d6fd9650d6. GEOM_LABEL: Label for provider stripe/gs9a is ufsid/4aeceb954b2a81d6. GEOM_CONCAT: Cannot add disk ufsid/4aece8d6fd9650d6 to gc9 (error=3D17). I appreciate any responses. Thank you! Lucas Reddinger From nonsolosoft at diff.org Wed Nov 4 23:32:59 2009 From: nonsolosoft at diff.org (Ferruccio Zamuner) Date: Wed Nov 4 23:33:06 2009 Subject: gjournal and disklabel Message-ID: <4AF20F24.6070501@diff.org> Hello, thank you for gjournal, but I've just following trouble: t1# gjournal list Geom name: gjournal 2411630194 ID: 2411630194 Providers: 1. Name: mirror/gmir0.journal Mediasize: 127774752256 (119G) Sectorsize: 512 Mode: r0w0e0 Consumers: 1. Name: mirror/gmir0 Mediasize: 128848494592 (120G) Sectorsize: 512 Mode: r1w1e1 Jend: 128848494080 Jstart: 127774752256 Role: Data,Journal Then I've not changed any data in disklabel: t1# disklabel -e /dev/mirror/gmir0.journal # /dev/mirror/gmir0.journal: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 251657200 16 unused 0 0 c: 251657216 0 unused 0 0 # "raw" part, don't edit partition a: partition extends past end of unit partition c: partition extends past end of unit disklabel: partition c doesn't cover the whole unit! disklabel: An incorrect partition c may cause problems for standard system utilities re-edit the label? [y]: But it cannot let me save for its own numbers. How to fix? Thank you in advance, \ferz From nonsolosoft at diff.org Wed Nov 4 23:42:36 2009 From: nonsolosoft at diff.org (Ferruccio Zamuner) Date: Wed Nov 4 23:42:42 2009 Subject: gjournal and disklabel In-Reply-To: <4AF20F24.6070501@diff.org> References: <4AF20F24.6070501@diff.org> Message-ID: <4AF21167.2040301@diff.org> Fixed: 127774752256 / 512 = 249560063 then: # /dev/mirror/gmir0.journal: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2097154 16 4.2BSD 2048 16384 28552 b: 6094304 2097170 swap c: 249560063 0 unused 0 0 # "raw" part, don't edit d: 12582912 8191474 4.2BSD 2048 16384 28552 e: 20971525 20774386 4.2BSD 2048 16384 28552 f: 16777220 41745911 4.2BSD 2048 16384 28552 g: 191036932 58523131 4.2BSD 2048 16384 28552 Ferruccio Zamuner wrote: > Hello, > > thank you for gjournal, but I've just following trouble: > > t1# gjournal list > Geom name: gjournal 2411630194 > ID: 2411630194 > Providers: > 1. Name: mirror/gmir0.journal > Mediasize: 127774752256 (119G) > Sectorsize: 512 > Mode: r0w0e0 > [...] > Thank you in advance, \ferz > > _______________________________________________ > 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 nonsolosoft at diff.org Thu Nov 5 10:36:49 2009 From: nonsolosoft at diff.org (Ferruccio Zamuner) Date: Thu Nov 5 10:36:55 2009 Subject: gjournal no valid label found Message-ID: <4AF2AAB7.8000308@diff.org> t1# gjournal list Geom name: gjournal 2411630194 ID: 2411630194 Providers: 1. Name: mirror/gmir0.journal Mediasize: 127774752256 (119G) Sectorsize: 512 Mode: r6w6e11 Consumers: 1. Name: mirror/gmir0 Mediasize: 128848494592 (120G) Sectorsize: 512 Mode: r1w1e1 Jend: 128848494080 Jstart: 127774752256 Role: Data,Journal Geom name: gjournal 1864804998 ID: 1864804998 Providers: 1. Name: stripe/gs0.journal Mediasize: 61312859648 (57G) Sectorsize: 512 Mode: r0w0e0 Consumers: 1. Name: stripe/gs0 Mediasize: 62386601984 (58G) Sectorsize: 512 Mode: r1w1e1 Jend: 62386601472 Jstart: 61312859648 Role: Data,Journal t1# disklabel -e /dev/stripe/gs0.journal disklabel: /dev/stripe/gs0.journal: no valid label found t1# disklabel -e stripe/gs0.journal disklabel: /dev/stripe/gs0.journal: no valid label found How can I partition this disks? Best regards, \ferz From linimon at FreeBSD.org Sat Nov 7 15:01:52 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sat Nov 7 15:02:03 2009 Subject: kern/140352: [geom] gjournal + glabel not working Message-ID: <200911071501.nA7F1q4T031812@freefall.freebsd.org> Old Synopsis: gjournal + glabel not working New Synopsis: [geom] gjournal + glabel not working Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Sat Nov 7 15:01:19 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=140352 From ross at grinz.com Sun Nov 8 05:14:36 2009 From: ross at grinz.com (Ross Gohlke) Date: Sun Nov 8 05:14:43 2009 Subject: gjournal questions and observations Message-ID: <4AF64F7D.8020802@grinz.com> KUDOS Congratulations to all GEOM contributors. While I am new to GEOM, so far I am very impressed with the way it is designed and the capabilities (both realized and anticipated) the design offers. QUESTIONS 1. What is the best way to journal whole disks whose slices (without partitions) are used by gconcat and gmirror? Does the same apply for gvinum? The ultimate scenario seems to be journaling another GEOM class such as gmirror because gjournal handles the synchronization of all mirror consumers. You can turn off autosync on the mirror, thus saving CPU cycles and improving disk access. (Am I right?) 2. How should gjournal and gmirror be configured when the journal is outside, instead of inside, the mirror? The above scenario only seems possible if a) you are willing to journal slices, which is not best practice [1] [2] or b) you use whole disks in your mirrors, which is not very realistic. Further I am on PowerPC and don't even have bsdlabel, so journaling slices and mirroring partitions is not an option anyway. My thought was to journal each disk separately, outside the mirror, and keep autosynchronization on for the mirror. [1] http://lists.freebsd.org/pipermail/freebsd-questions/2008-April/173501.html [2] http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-11/msg00247.html 3. What is the best way to completely remove a whole disk journal such that re-issuing % gjournal label /dev/ad0 does not require -f? I have tried gpart destroy/create and newfs -E. I have not tried blanking the whole disk with dd, nor have I tried newfs -E on the whole disk. 4. Does it matter whether gjournal is loaded when gjournal label is issued? Originally I was journaling slices, and I was unable to properly stop a particular slice. % gjournal stop ad0s6.journal % gjournal list Showed the slice still loaded, but under a different name: ie, ufsid/48x6x1bxc39394x7 I don't know if it was related to the originally issued gjournal label command or that gjournal was loaded before the slice was labeled. I believe what fixed it was: % dd if=/dev/zero of=/dev/ad0s6 OBSERVATIONS GJOURNAL These may seem obvious to you but were hard won by me. 1. Never try to store a whole disk's journal on a slice of the same disk. 2. When journaling a whole disk and keeping the journal on the same disk, not only must the very last sector of the disk be reserved, but also the last gig (or whatever the size of your journal). Just leave it as free space when you create slices with gpart. While gjournal man page states journaling an existing file system REQUIRES a separate device for storing the journal, it appears to work without specifying a second device. At least % gjournal label -f /dev/ad0 seems to work, using the end of /dev/ad0 to store the journal whether a slice occupies those sectors or not. (Consequently, trying to gmirror the last slice when it occupies journal sectors will fail.) Regards, Ross Gohlke From bugmaster at FreeBSD.org Mon Nov 9 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 9 11:08:08 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200911091106.nA9B6qci078994@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/140352 geom [geom] gjournal + glabel not working 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 53 problems total. From 000.fbsd at quip.cz Mon Nov 9 16:24:42 2009 From: 000.fbsd at quip.cz (Miroslav Lachman) Date: Mon Nov 9 16:24:53 2009 Subject: gjournal and calculation of the size of journal provider Message-ID: <4AF84245.7070108@quip.cz> What is the right rule for journal size calculation? There are two sources stating different things. 1] journal size depends on disk write speed http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/002016.html "For example your disk can write at 60MB/s. Journal switch time is 10 seconds. The journal provider has to have place to keep two journals (active and inactive). So bascially you need 60*10*2MB + gjournal headers." 2] journal size depends on RAM size http://www.freebsd.org/doc/en/articles/gjournal-desktop/article.html#UNDERSTANDING-JOURNALING "Your RAM size should fit in 30% of the journal provider's space. For example, if your system has 1 GB RAM, create an approximately 3.3 GB journal provider. (Multiply your RAM size with 3.3 to obtain the size of the journal)." What's the right size for journal on 143GB 15k rpm SAS disks on machine with 16GB of RAM? Based on second case, it will be more than 50 GB - one third of the size of disk. This is insane vasting. I have gjournal on few of our machines with size of journal set to 2GB on SATA disks in gmirror. Miroslav Lachman From ivoras at freebsd.org Tue Nov 10 10:24:20 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Tue Nov 10 10:24:26 2009 Subject: gjournal and calculation of the size of journal provider In-Reply-To: <4AF84245.7070108@quip.cz> References: <4AF84245.7070108@quip.cz> Message-ID: Miroslav Lachman wrote: > What is the right rule for journal size calculation? > There are two sources stating different things. > > 1] journal size depends on disk write speed > http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/002016.html > > "For example your disk can write > at 60MB/s. Journal switch time is 10 seconds. The journal provider has > to have place to keep two journals (active and inactive). So bascially > you need 60*10*2MB + gjournal headers." > > > 2] journal size depends on RAM size > http://www.freebsd.org/doc/en/articles/gjournal-desktop/article.html#UNDERSTANDING-JOURNALING > > > "Your RAM size should fit in 30% of the journal provider's space. For > example, if your system has 1 GB RAM, create an approximately 3.3 GB > journal provider. (Multiply your RAM size with 3.3 to obtain the size of > the journal)." > > > What's the right size for journal on 143GB 15k rpm SAS disks on machine > with 16GB of RAM? Based on second case, it will be more than 50 GB - one > third of the size of disk. This is insane vasting. It really does depend on the speed of drives but it could be approximated by saying there will not be more data to write than the size of memory (which is probably wrong since you can write from /dev/zero indefinitely). The first advice is sufficient, but you should probably extend the result by 20% to be safer. From ross at grinz.com Tue Nov 10 13:26:23 2009 From: ross at grinz.com (Ross Gohlke) Date: Tue Nov 10 13:26:29 2009 Subject: gjournal questions and observations In-Reply-To: <4AF64F7D.8020802@grinz.com> References: <4AF64F7D.8020802@grinz.com> Message-ID: <4AF96A13.8080306@grinz.com> > QUESTIONS > 3. What is the best way to completely remove a whole disk journal such > that re-issuing > % gjournal label /dev/ad0 > does not require -f? Blanking the beginning of the drive did the trick. % dd if=/dev/zero of=/dev/ad0 bs=1m count=600 > 1. What is the best way to journal whole disks whose slices (without > partitions) are used by gconcat and gmirror? Does the same apply for > gvinum? % gjournal label /dev/ad0 % gjournal load (Don't newfs the journal; wait for concat) % gconcat load % gconcat label ports ad0.journals11 % newfs /dev/concat/ports % mount /dev/concat/ports /mnt/ports Add new slices to the journal, not the disk. % gpart add -i 12 ad0.journal Setting up a gmirrored gconcat did not work. Another guy tried gconcatted gmirrors and had a similar result [1]. He was able to fix the problem with fsck, which did not work for me: [1] http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2006/freebsd-geom/20060806.freebsd-geom This was the result when trying to rsync /usr/ports to /mnt/ports (/dev/mirror/ports). #/var/log/messages ... Nov 9 17:00:51 rorty kernel: GEOM_CONCAT: Device ports created (id=1362796578). Nov 9 17:00:51 rorty kernel: GEOM_CONCAT: Disk ad0s11 attached to ports. Nov 9 17:00:51 rorty kernel: GEOM_CONCAT: Device ports activated. Nov 9 17:00:51 rorty kernel: GEOM_MIRROR: Device ports: provider concat/ports marked as inactive, skipping. Nov 9 17:00:51 rorty kernel: GEOM_MIRROR: Device ports: provider ufsid/4af8442b031fbe48 marked as inactive, skipping. Nov 9 17:00:59 rorty kernel: GEOM_MIRROR: Device mirror/ports launched (1/1). Nov 9 17:01:57 rorty kernel: ad1: TIMEOUT - READ_MUL retrying (1 retry left) LBA=116413904 Nov 9 17:02:50 rorty kernel: ad1: TIMEOUT - READ_MUL retrying (1 retry left) LBA=115497232 Nov 9 17:02:50 rorty kernel: ad0: TIMEOUT - WRITE_MUL retrying (1 retry left) LBA=19936658 Nov 9 17:02:55 rorty kernel: ad1: TIMEOUT - READ_MUL retrying (1 retry left) LBA=115498352 Nov 9 17:03:10 rorty kernel: g_vfs_done():mirror/ports[WRITE(offset=1073758208, length=2048)]error = 5 Nov 9 17:03:10 rorty kernel: g_vfs_done():mirror/ports[WRITE(offset=1073760256, length=2048)]error = 5 Nov 9 17:03:10 rorty kernel: g_vfs_done():mirror/ports[WRITE(offset=1073762304, length=2048)]error = 5 Nov 9 17:03:41 rorty kernel: initiate_write_filepage: already started Nov 9 17:03:41 rorty kernel: initiga_tvef_sw_rdiotnee_(f)i:lmeiprargoer:/ paolrrtesa[dWyR IsTtEa(rotfefdset Nov 9 17:03:41 rorty kernel: =1i0n7i3t7i6a2t3e0_4w,r ilteen_gftihl=e2p0a4g8e):] earlrroera d=y 5st Nov 9 17:03:41 rorty kernel: artedg_v Nov 9 17:03:41 rorty kernel: fs_done():mirror/ports[WRITE(offset=1073760256, length=2048)]error = 5 Nov 9 17:03:41 rorty kernel: g_vfs_done():mirror/ports[WRITE(offset=1073758208, length=2048)]error = 5 Nov 9 17:03:42 rorty kernel: initiate_write_filepage: already started Nov 9 17:03:42 rorty kernel: initiate_write_filepage: already started Nov 9 17:03:42 rorty kernel: initiate_wgr_ivtfes__fdiolneep(a)g:em:i rarlorre/apdoyr tsst[aWrRtIeTdE(o Nov 9 17:03:42 rorty kernel: ffset=1073758208, length=2048)]error = 5 Nov 9 17:03:42 rorty kernel: g_vfs_done():mirror/ports[WRITE(offset=1073760256, length=2048)]error = 5 Nov 9 17:03:42 rorty kernel: g_vfs_done():mirror/ports[WRITE(offset=1073762304, length=2048)]error = 5 Nov 9 17:04:12 rorty kernel: initiate_write_filepage: already started Nov 9 17:04:12 rorty kernel: ingit_ivaftse__dworniet(e)_:fmiilrerpoarg/ep:o ratlsr[eWaRdIyT Es(toafrftseedt=1 Nov 9 17:04:12 rorty kernel: 073i7n6i2t3i0a4t,e _lwernigtteh_=fi2l0e4p8a)g]ee:r raolrr e=a d5y Nov 9 17:04:12 rorty kernel: startge_dvf Nov 9 17:04:12 rorty kernel: s_done():mirror/ports[WRIiTnEi(toifaftsee_tw=ri1t0e7_3f7i6l0e2p5a6g,e :l eanlgrteha=d2y0 4s8t)$ Nov 9 17:04:12 rorty kernel: = 5 Nov 9 17:04:12 rorty kernel: g_vfs_done():mirror/ports[WRIT ... I have ruled out the disk being bad because it works fine with gmirror OR gconcat, just not both. Regards, Ross From pjd at FreeBSD.org Tue Nov 10 19:02:20 2009 From: pjd at FreeBSD.org (Pawel Jakub Dawidek) Date: Tue Nov 10 19:02:27 2009 Subject: gjournal questions and observations In-Reply-To: <4AF64F7D.8020802@grinz.com> References: <4AF64F7D.8020802@grinz.com> Message-ID: <20091110190213.GB3194@garage.freebsd.pl> On Sat, Nov 07, 2009 at 10:56:29PM -0600, Ross Gohlke wrote: > KUDOS > Congratulations to all GEOM contributors. While I am new to GEOM, so far > I am very impressed with the way it is designed and the capabilities > (both realized and anticipated) the design offers. > > QUESTIONS > 1. What is the best way to journal whole disks whose slices (without > partitions) are used by gconcat and gmirror? Does the same apply for gvinum? > The ultimate scenario seems to be journaling another GEOM class such as > gmirror because gjournal handles the synchronization of all mirror > consumers. You can turn off autosync on the mirror, thus saving CPU > cycles and improving disk access. (Am I right?) You should always gjournal top-most provider, so you always put UFS on top of .journal provider. Don't do anything with .journal besides of file system configuration. > 2. How should gjournal and gmirror be configured when the journal is > outside, instead of inside, the mirror? > The above scenario only seems possible if a) you are willing to journal > slices, which is not best practice [1] [2] or b) you use whole disks in > your mirrors, which is not very realistic. > Further I am on PowerPC and don't even have bsdlabel, so journaling > slices and mirroring partitions is not an option anyway. > My thought was to journal each disk separately, outside the mirror, and > keep autosynchronization on for the mirror. > > [1] > http://lists.freebsd.org/pipermail/freebsd-questions/2008-April/173501.html > [2] > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-11/msg00247.html See above. You can safely gmirror disks, slices or partition and put gjournal on top of gmirror and file system on top of gjournal. > 3. What is the best way to completely remove a whole disk journal such > that re-issuing > % gjournal label /dev/ad0 > does not require -f? > I have tried gpart destroy/create and newfs -E. I have not tried > blanking the whole disk with dd, nor have I tried newfs -E on the whole > disk. gjournal stop .journal (or ); gjournal clear > 4. Does it matter whether gjournal is loaded when gjournal label is issued? > Originally I was journaling slices, and I was unable to properly stop a > particular slice. > % gjournal stop ad0s6.journal > % gjournal list > Showed the slice still loaded, but under a different name: > ie, ufsid/48x6x1bxc39394x7 You provider is accessible by few different names. This ufsid/ thing (which I don't like) is one of them. Once you stop gjournal on one name it is recreated using another name. Besides of using -h option to gjournal label and hardcoding provider name there is not much we can do. > While gjournal man page states journaling an existing file system > REQUIRES a separate device for storing the journal, it appears to work > without specifying a second device. At least > % gjournal label -f /dev/ad0 > seems to work, using the end of /dev/ad0 to store the journal whether a > slice occupies those sectors or not. (Consequently, trying to gmirror > the last slice when it occupies journal sectors will fail.) It will eventually work until your UFS will start to use space gjournal is using for journal. Absolutely don't do that. Its like creating 4GB file system on 3GB provider - at some point you will need the missing 1GB.. -- Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20091110/a07a404b/attachment.pgp From 000.fbsd at quip.cz Wed Nov 11 15:59:11 2009 From: 000.fbsd at quip.cz (Miroslav Lachman) Date: Wed Nov 11 15:59:17 2009 Subject: gjournal and calculation of the size of journal provider In-Reply-To: References: <4AF84245.7070108@quip.cz> Message-ID: <4AFADF4A.80404@quip.cz> Ivan Voras wrote: > Miroslav Lachman wrote: >> What is the right rule for journal size calculation? >> There are two sources stating different things. >> >> 1] journal size depends on disk write speed >> http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/002016.html >> >> "For example your disk can write >> at 60MB/s. Journal switch time is 10 seconds. The journal provider has >> to have place to keep two journals (active and inactive). So bascially >> you need 60*10*2MB + gjournal headers." >> >> >> 2] journal size depends on RAM size >> http://www.freebsd.org/doc/en/articles/gjournal-desktop/article.html#UNDERSTANDING-JOURNALING >> >> >> "Your RAM size should fit in 30% of the journal provider's space. For >> example, if your system has 1 GB RAM, create an approximately 3.3 GB >> journal provider. (Multiply your RAM size with 3.3 to obtain the size >> of the journal)." >> >> >> What's the right size for journal on 143GB 15k rpm SAS disks on >> machine with 16GB of RAM? Based on second case, it will be more than >> 50 GB - one third of the size of disk. This is insane vasting. > > It really does depend on the speed of drives but it could be > approximated by saying there will not be more data to write than the > size of memory (which is probably wrong since you can write from > /dev/zero indefinitely). The first advice is sufficient, but you should > probably extend the result by 20% to be safer. So is it safe to use 4GB on PERC6 array, which is capable of 150MB/s write speed by dd test? dd if=/dev/zero of=/dev/mfid0s2e bs=1m count=10000 (150 * 10 * 2 * 1.2) = 3600 150 is write speed in MB/s 10 is journal switch time 2 is active + inactive journal 1.2 is +20% to base safer And next question about journal. I saw following message in log after reboot: GEOM_JOURNAL: Journal 1933335573: mfid0s2d contains journal. GEOM_JOURNAL: Journal 1933335573: mfid0s2e contains data. GEOM_JOURNAL: Journal mfid0s2e clean. GEOM_JOURNAL: BIO_FLUSH not supported by mfid0s2d. GEOM_JOURNAL: BIO_FLUSH not supported by mfid0s2e. "BIO_FLUSH not supported" - is it OK to use gjournal on top of the Dell PERC (LSI MegaRAID) with battery backup unit? I think so, but rather ask somebody... :) Miroslav Lachman From ivoras at freebsd.org Wed Nov 11 16:07:09 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Wed Nov 11 16:07:15 2009 Subject: gjournal and calculation of the size of journal provider In-Reply-To: <4AFADF4A.80404@quip.cz> References: <4AF84245.7070108@quip.cz> <4AFADF4A.80404@quip.cz> Message-ID: Miroslav Lachman wrote: > Ivan Voras wrote: >> Miroslav Lachman wrote: >>> What is the right rule for journal size calculation? >>> There are two sources stating different things. >>> >>> 1] journal size depends on disk write speed >>> http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/002016.html >>> >>> "For example your disk can write >>> at 60MB/s. Journal switch time is 10 seconds. The journal provider has >>> to have place to keep two journals (active and inactive). So bascially >>> you need 60*10*2MB + gjournal headers." >>> >>> >>> 2] journal size depends on RAM size >>> http://www.freebsd.org/doc/en/articles/gjournal-desktop/article.html#UNDERSTANDING-JOURNALING >>> >>> >>> >>> "Your RAM size should fit in 30% of the journal provider's space. For >>> example, if your system has 1 GB RAM, create an approximately 3.3 GB >>> journal provider. (Multiply your RAM size with 3.3 to obtain the size >>> of the journal)." >>> >>> >>> What's the right size for journal on 143GB 15k rpm SAS disks on >>> machine with 16GB of RAM? Based on second case, it will be more than >>> 50 GB - one third of the size of disk. This is insane vasting. >> >> It really does depend on the speed of drives but it could be >> approximated by saying there will not be more data to write than the >> size of memory (which is probably wrong since you can write from >> /dev/zero indefinitely). The first advice is sufficient, but you should >> probably extend the result by 20% to be safer. > > > So is it safe to use 4GB on PERC6 array, which is capable of 150MB/s > write speed by dd test? > dd if=/dev/zero of=/dev/mfid0s2e bs=1m count=10000 > > (150 * 10 * 2 * 1.2) = 3600 > > 150 is write speed in MB/s > 10 is journal switch time > 2 is active + inactive journal > 1.2 is +20% to base safer This looks fine! > And next question about journal. I saw following message in log after > reboot: > > GEOM_JOURNAL: Journal 1933335573: mfid0s2d contains journal. > GEOM_JOURNAL: Journal 1933335573: mfid0s2e contains data. > GEOM_JOURNAL: Journal mfid0s2e clean. > GEOM_JOURNAL: BIO_FLUSH not supported by mfid0s2d. > GEOM_JOURNAL: BIO_FLUSH not supported by mfid0s2e. > > "BIO_FLUSH not supported" - is it OK to use gjournal on top of the Dell > PERC (LSI MegaRAID) with battery backup unit? I think so, but rather ask > somebody... :) I think you are safe if the controller has the BBU working and enabled. From tony at crosswinds.net Thu Nov 12 15:17:25 2009 From: tony at crosswinds.net (Tony Holmes) Date: Thu Nov 12 15:17:32 2009 Subject: GJournal too Small? Message-ID: <20091112151753.GA20087@crosswinds.net> I have a 894GB gstripe that I've put gjournal on top of. Since it was an unused stripe I placed the data+journal into the same partition. The server is fairly heavily used and hung suddenly. On reboot I got this in the dmesg: GEOM_JOURNAL: Journal 3472355975: mirror/gm0s1e contains journal. GEOM_STRIPE: Device st0 created (id=2649322337). GEOM_STRIPE: Disk mirror/gm0s1f attached to st0. GEOM_MIRROR: Device mirror/gm1 launched (1/1). GEOM_STRIPE: Disk mirror/gm1s1f attached to st0. GEOM_STRIPE: Device st0 activated. GEOM_JOURNAL: Journal 2630378703: stripe/st0 contains data. GEOM_JOURNAL: Journal 2630378703: stripe/st0 contains journal. GEOM_JOURNAL: Journal stripe/st0 clean. GEOM_JOURNAL: Timeout. Journal gjournal 3472355975 cannot be completed. That last line worries me. >From a quick google, it appears that the gjournal is too small. Since I created it with the single partition, I would have expected the journal to be autosized correctly. I know the OS is a little out of date but has been working very well until the past couple months. I have 1 hang approximately every month. Information about system: FreeBSD fs.cwahi.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Mon Dec 1 09:12:42 EST 2008 root@app.cwahi.com:/usr/obj/usr/src/sys/CWahi amd64 fs# gjournal list Geom name: gjournal 1493846988 ID: 1493846988 Providers: 1. Name: stripe/st0.journal Mediasize: 958334500352 (893G) Sectorsize: 512 Mode: r1w1e1 Consumers: 1. Name: stripe/st0 Mediasize: 959408242688 (894G) Sectorsize: 512 Mode: r1w1e1 Jend: 959408242176 Jstart: 958334500352 Role: Data,Journal Newfs'd with: newfs -J -b 16384 -f 2048 -m 4 /dev/stripe/st0.journal -- Tony Holmes Ph: (416) 993-1219 Founder and Senior Systems Architect Crosswinds Internet Communications Inc. From ivoras at freebsd.org Thu Nov 12 21:18:33 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Thu Nov 12 21:18:40 2009 Subject: GJournal too Small? In-Reply-To: <20091112151753.GA20087@crosswinds.net> References: <20091112151753.GA20087@crosswinds.net> Message-ID: Tony Holmes wrote: > I have a 894GB gstripe that I've put gjournal on top of. Since it was > an unused stripe I placed the data+journal into the same partition. > The server is fairly heavily used and hung suddenly. On reboot I got > this in the dmesg: > > GEOM_JOURNAL: Journal 3472355975: mirror/gm0s1e contains journal. > GEOM_STRIPE: Device st0 created (id=2649322337). > GEOM_STRIPE: Disk mirror/gm0s1f attached to st0. > GEOM_MIRROR: Device mirror/gm1 launched (1/1). > GEOM_STRIPE: Disk mirror/gm1s1f attached to st0. > GEOM_STRIPE: Device st0 activated. > GEOM_JOURNAL: Journal 2630378703: stripe/st0 contains data. > GEOM_JOURNAL: Journal 2630378703: stripe/st0 contains journal. > GEOM_JOURNAL: Journal stripe/st0 clean. > GEOM_JOURNAL: Timeout. Journal gjournal 3472355975 cannot be completed. > > That last line worries me. > >>From a quick google, it appears that the gjournal is too small. Since > I created it with the single partition, I would have expected the journal > to be autosized correctly. The message "Timeout. Journal %s cannot be completed." is printed when the gjournal composite device is created with data and journal on separate providers. It means that a timeout occurred while gjournal waited for both providers to come online. Your message contains something that looks like a journal ID (3472355975) which isn't in the code in 7-stable and 8-stable/head. How did you get that line? Assuming magic has happened and the journal ID (3472355975) is correct then it means you have two gjournal devices, one of those created on the stripe st0 (2630378703). It could mean that somehow, there is still recognizable metadata on your drives and/or partitions which confuses gjournal. > I know the OS is a little out of date but has been working very well until > the past couple months. I have 1 hang approximately every month. > > Information about system: > > FreeBSD fs.cwahi.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Mon Dec 1 09:12:42 EST 2008 root@app.cwahi.com:/usr/obj/usr/src/sys/CWahi amd64 > > fs# gjournal list > Geom name: gjournal 1493846988 > ID: 1493846988 This, on the other hand, is a third gjournal ID. Assuming that somehow all this information is correct, you should probably send the output of sysctl -b kern.geom.confxml before anyone can unravel what has happened :) From bzeeb-lists at lists.zabbadoz.net Sun Nov 15 20:45:08 2009 From: bzeeb-lists at lists.zabbadoz.net (Bjoern A. Zeeb) Date: Sun Nov 15 20:45:14 2009 Subject: gjournal + gptid/ un"stop"able Message-ID: <20091115203253.R37440@maildrop.int.zabbadoz.net> Hi, I just read the previous thread via the list archive. As of late on HEAD something changed that doesn't allow one to "stop" gjournal anymore and get rid of it. I have been using this same setup for months if not more than a year without problems. Whatever was added introduced an architectural problem. Either /dev/da*.journal exists or when that is stopped a journal etc. shows up with the "cryptic" names in /dev/gptid/....journal. If you stop that, the /dev/da*.journal is back. This essentially means that once gjournal is loaded, one is unable to unload it again, unless ones force a "detach"/"stop" on all lower providers. This essentially means that one can no longer safely shut down without the risk of losing/scrambling data. I guess the "ufsid/" things mentioned formerly has the same problem. What are the possible solutions to that? /bz -- Bjoern A. Zeeb It will not break if you know what you are doing. From bugmaster at FreeBSD.org Mon Nov 16 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 16 11:08:10 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200911161106.nAGB6quW011166@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/140352 geom [geom] gjournal + glabel not working 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 53 problems total. From bugmaster at FreeBSD.org Mon Nov 23 11:06:55 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 23 11:08:10 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200911231106.nANB6sTn070127@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/140352 geom [geom] gjournal + glabel not working 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 53 problems total. From korvus at comcast.net Tue Nov 24 17:53:31 2009 From: korvus at comcast.net (Steve Polyack) Date: Tue Nov 24 17:53:40 2009 Subject: Panic possibly related to glabel/geom and siis(4) Message-ID: <4B0C1A72.3000301@comcast.net> I have a system running 8.0-PRERELEASE with multiple drives and SATA port multipliers (siis controllers and PMPs). All of the attached drives are labeled via glabel(8) and then included into a ZFS pool. During some testing to determine how the system would react to a dead drive (simulated by physically removing a drive during operation), I was able to produce a panic. Now, I know that the SATA PMP and siis(4) code to handle and recover from device errors is incomplete, but I believe the crash may be particular to using glabel'd drives. Basically, after removing a drive while the zpool is in use and issues 'camcontrol reset' and 'rescan' on the appropriate bus, the physical device associated with the drive disappears. In this case: (pass5:siisch7:0:15:0): lost device (pass5:siisch7:0:15:0): removing device entry (ada2:siisch7:0:0:0): lost device and /dev/ada2 disappears. However, the associated glabel /dev/label/bigdisk07 remains. Since my ZFS pool is created based on the drive glabels, I believe this is why ZFS never notices the drives disappear either. Do glabels typically go away after a physical device is lost? Should this not be the case? After some runtime with the physical device missing, a kernel panic is produced: ada2:siisch7:0:0:0): Synchronize cache failed (ada2:siisch7:0:0:0): removing device entry Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 14 fault virtual address = 0x48 fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff8035f375 stack pointer = 0x28:0xffffff800006db60 frame pointer = 0x28:0xffffff800006db70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2 (g_event) [thread pid 2 tid 100014 ] Stopped at _mtx_lock_flags+0x15: lock cmpxchgq %rsi,0x18(%rdi) db> bt Tracing pid 2 tid 100014 td 0xffffff00014d4ab0 _mtx_lock_flags() at _mtx_lock_flags+0x15 vdev_geom_release() at vdev_geom_release+0x33 vdev_geom_orphan() at vdev_geom_orphan+0x15c g_run_events() at g_run_events+0x104 g_event_procbody() at g_event_procbody+0x55 fork_exit() at fork_exit+0x118 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff800006dd30, rbp = 0 --- I'm open to try patches and other suggestions. Thanks.