From linimon at FreeBSD.org Mon May 5 01:56:27 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon May 5 01:56:29 2008 Subject: kern/89546: [geom] GEOM error Message-ID: <200805050156.m451uQGK099715@freefall.freebsd.org> Synopsis: [geom] GEOM error Responsible-Changed-From-To: freebsd-amd64->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 5 01:56:00 UTC 2008 Responsible-Changed-Why: Reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=89546 From bugmaster at FreeBSD.org Mon May 5 11:07:05 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 5 11:07:10 2008 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200805051107.m45B74M0070693@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/73177 geom kldload geom_* causes panic due to memory exhaustion o kern/76538 geom [gbde] nfs-write on gbde partition stalls and continue o kern/83464 geom [geom] [patch] Unhandled malloc failures within libgeo o kern/84556 geom [geom] GBDE-encrypted swap causes panic at shutdown o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/89546 geom [geom] GEOM error o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/113419 geom [geom] geom fox multipathing not failing back o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/115572 geom [gbde] [patch] gbde partitions fail at 28bit/48bit LBA o kern/120021 geom net-p2p/qbittorrent crashes system when it works thoug o kern/120231 geom [geom] GEOM_CONCAT error adding second drive f kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/122067 geom [panic]: Geom crashed during boot f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/123122 geom GEOM / gjournal kernel lock 20 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/78131 geom gbde "destroy" not working. o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/121559 geom [patch] [geom] geom label class allows to create inacc f kern/121907 geom [request] [geom] geom output to console obscures other 13 problems total. From christian.baer at uni-dortmund.de Fri May 9 17:04:59 2008 From: christian.baer at uni-dortmund.de (Christian Baer) Date: Fri May 9 17:05:02 2008 Subject: Keeping gmirror and geli after a reinstall Message-ID: Hello folks! I have really done it! I managed to absolutely screw up the FreeBSD installation on my Sun. That happens if you don't watch what you are doing and install stuff via the ports *without* portupgrade. Now several apps won't start anymore and give really strange errors when they try. :-) That makes a real mess of your system. :-) Thankfully, mutt and slrn are not among these apllications. Ok, this is FreeBSD not Windows, so it would probably be possible to fix the installtion. However, it would probably be less work to reinstall the whole thing (first I have to *find* the stuff causing the problems) and besides, this is a good excuse to upgrade to 7.0. :-) Now, to the actual question... This machine has 2 gmirrors and both are encrypted with geli. Setting these up and blanking them is a real pain, so I was wondering if I could just leave them as they are and keep using them after the reinstall. The partitions on the drives will not need to be changed, so there is no reason to clear them. Needless to say, I *will* be making a backup of the data on the mirror before I start with this. However, if I know in advance that this will not work (for example because geli and/or gmirror changed too much since 6.3), I won't bother trying to reuse them but will just recreate them as well. Has anyone tried this before? Regards, Chris From bsd at fluffles.net Fri May 9 22:42:36 2008 From: bsd at fluffles.net (fluffles.net) Date: Fri May 9 22:42:41 2008 Subject: Keeping gmirror and geli after a reinstall In-Reply-To: References: Message-ID: <4824CF57.5030404@fluffles.net> Christian Baer wrote: > Now, to the actual question... > This machine has 2 gmirrors and both are encrypted with geli. Setting > these up and blanking them is a real pain, so I was wondering if I could > just leave them as they are and keep using them after the reinstall. The > partitions on the drives will not need to be changed, so there is no > reason to clear them. > Yes, you can just use your existing software arrays and geom providers under 7.0. Since the configuration of geom modules is stored on the disks themselves (the last sector of the consumer). Simply install FreeBSD on a medium, load gmirror and you should have devices in your /dev/mirror/ tree. geli should work with geli attach . FreeBSD 7 should have no problem detecting the arrays you made with FreeBSD 6.x. As long as you seperated your data from your operating system, there is no problem. If FreeBSD is (partly) installed on a gstripe,graid3 or graid5 array, with or without geli encryption, it becomes a different story. Note that it is not possible to boot from such a device. I'm using this kind of configuration with a small flash device which contains / and /boot, and the /usr, /var, /tmp and storage devices on a geom_raid5 provider with GELI encryption. Without geom_journal, crashes could easily cause your box to boot in single user mode, which is quite a pain if you rely on the machine. That is why i'm using geom_journal now. > Has anyone tried this before? > Many times. =) Fine regards, Veronica Fluffles.net From bugmaster at FreeBSD.org Mon May 12 11:06:57 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 12 11:07:02 2008 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200805121106.m4CB6uDQ037997@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/73177 geom kldload geom_* causes panic due to memory exhaustion o kern/76538 geom [gbde] nfs-write on gbde partition stalls and continue o kern/83464 geom [geom] [patch] Unhandled malloc failures within libgeo o kern/84556 geom [geom] GBDE-encrypted swap causes panic at shutdown o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/89546 geom [geom] GEOM error o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/113419 geom [geom] geom fox multipathing not failing back o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/115572 geom [gbde] [patch] gbde partitions fail at 28bit/48bit LBA o kern/120021 geom net-p2p/qbittorrent crashes system when it works thoug o kern/120231 geom [geom] GEOM_CONCAT error adding second drive f kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/122067 geom [panic]: Geom crashed during boot f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/123122 geom GEOM / gjournal kernel lock 20 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/78131 geom gbde "destroy" not working. o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/121559 geom [patch] [geom] geom label class allows to create inacc f kern/121907 geom [request] [geom] geom output to console obscures other 13 problems total. From vwe at FreeBSD.org Mon May 12 20:54:39 2008 From: vwe at FreeBSD.org (vwe@FreeBSD.org) Date: Mon May 12 20:54:42 2008 Subject: kern/123606: [geli] Executing files on encrypted usb stick fails with g_vfs_done() error = 22 Message-ID: <200805122054.m4CKsd8o093131@freefall.freebsd.org> Synopsis: [geli] Executing files on encrypted usb stick fails with g_vfs_done() error = 22 State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Mon May 12 20:52:25 UTC 2008 State-Changed-Why: Christian: Can you please send output of `geom eli list`, `geom disk list` and a dmesg output? Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: vwe Responsible-Changed-When: Mon May 12 20:52:25 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=123606 From avg at icyb.net.ua Tue May 13 07:56:21 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Tue May 13 07:56:24 2008 Subject: handling of EGAIN from softdep_check_suspend (gjournal) Message-ID: <4829499B.6080007@icyb.net.ua> As being reported from time to time, sometimes there is a following error message produced by gjournal activity: kernel: fsync: giving up on dirty kernel: 0xc32b8bb0: tag devfs, type VCHR kernel: usecount 1, writecount 0, refcount 50 mountedhere 0xc323d200 kernel: flags () kernel: v_object 0xc10499b0 ref 0 pages 451 kernel: lock type devfs: EXCL (count 1) by thread 0xc3208000 (pid 39) kernel: dev ad4s1e.journal kernel: GEOM_JOURNAL: Cannot suspend file system /export (error=35). errno 35 is EAGAIN/EWOULDBLOCK and it is returned from vfs_write_suspend on FFS. The only place where this return code is present in the whole FFS/UFS code is softdep_check_suspend. Comment in the function says the following (for non-softupdates case): /* * Reasons for needing more work before suspend: * - Dirty buffers on devvp. * - Secondary writes occurred after start of vnode sync loop */ I wonder what is recommended handling of this return code? Maybe we should try 'AGAIN' instead of just giving up immediately? -- Andriy Gapon From pjd at FreeBSD.org Tue May 13 12:00:12 2008 From: pjd at FreeBSD.org (Pawel Jakub Dawidek) Date: Tue May 13 12:00:20 2008 Subject: kern/123606: Executing files on encrypted usb stick fails with g_vfs_done() error = 22 Message-ID: <200805131200.m4DC0Ajr095174@freefall.freebsd.org> The following reply was made to PR kern/123606; it has been noted by GNATS. From: Pawel Jakub Dawidek To: Christian =?iso-8859-1?Q?Kr=E4mer?= Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/123606: Executing files on encrypted usb stick fails with g_vfs_done() error = 22 Date: Tue, 13 May 2008 13:38:13 +0200 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 12, 2008 at 09:19:29AM +0000, Christian Kr=E4mer wrote: >=20 > >Number: 123606 > >Category: kern > >Synopsis: Executing files on encrypted usb stick fails with g_vfs_= done() error =3D 22 > >Confidential: no > >Severity: non-critical > >Priority: medium > >Responsible: freebsd-bugs > >State: open > >Quarter: =20 > >Keywords: =20 > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Mon May 12 09:30:01 UTC 2008 > >Closed-Date: > >Last-Modified: > >Originator: Christian Kr=E4mer > >Release: Release 6.2 > >Organization: > >Environment: > FreeBSD humbert 6.2-RELEASE FreeBSD 6.2-RELEASE #2: Sun Apr 20 07:40:27 C= EST 2008 root@humbert:/usr/src/sys/i386/compile/MYKERNEL i386 >=20 > >Description: > I tried to create an encrypted memory stick using geli. When I try to exe= cute files the following error message shows up in dmesg: > May 6 22:17:33 kernel: g_vfs_done():da0s1b.eli[READ(offset=3D3748950016,= l > ength=3D8192)]error =3D 22 > May 6 22:17:33 kernel: vnode_pager_getpages: I/O read error >=20 > - The file itself is readable and correctly copied > MD5 (/bin/ls) =3D d8360b60978850cb2821b1e742ea4723 > MD5 (/mnt/usb/ls) =3D d8360b60978850cb2821b1e742ea4723 > - I am using via epia padlock for encryption, but this happens too when s= oftware crypto is enabled. > - After reading the file into memory for examples by md5 summing it file = execution works. > - This might be the same problem as pr-id: 98742 > - I tried ufs block sizes of 4096 and 16384 bytes > - I tried various geli sector sizes (-s) I don't think that you actually tried various sector sizes. At least you didn't try secor sizes less than page size. I'm quite sure geli(8) warns about using sector sizes bigger than page size. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFIKX2kForvXbEpPzQRAlBdAJ9+jG7bqWo8hGdGCa6GdBcrBRBJgwCdEQjb OPDUheEq3G3oTGnQCuVvgVE= =2rCh -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From christian.baer at uni.dortmund.de Tue May 13 16:16:13 2008 From: christian.baer at uni.dortmund.de (Christian Baer) Date: Tue May 13 16:16:18 2008 Subject: Kernel with GELI und crypto won't mount / Message-ID: Hi there, people! I have a little problem here that is bringing me some headaches. :-( Yesterday I set up a new FreeBSD 7.0 system (sparc64). This is a Sun U60 and worked fine for me for ages under 6.3. Installing went without any problems. The problems started, when I updated the sources (due to a security issue) to RELENG_7. I made a new world and a new kernel. I did change the kernel-config by adding two lines: options GEOM_ELI device crypto Well, technically I did a fair bit more than that, but when the problems started, I went back to a generic kernel with just these two extra lines, because I need those two. What this boils down to is that adding GEOM_ELI and crypto to the kernel seems to make my / unmountable (see dmesg after my sig). The generic kernel works fine but that isn't quite good enough because I habe two encrypted providers on the drives. One other thing might be worth mentioning: The system has two configured gmirrors. These are not needed at boot time though and AFAIK no atempts to configure them are being made. Did I mess up somewhere or am I missing the point. Regards Chris Here the dmesg: Booting [/boot/kernel/kernel]... nothing to autoload yet. jumping to kernel entry at 0xc0078000. stray vector interrupt 2029 Copyright (c) 1992-2008 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.0-STABLE #3: Tue May 13 09:32:42 CEST 2008 root@sunny.rz1.convenimus.net:/usr/obj/usr/src/sys/SUNNY real memory = 2147483648 (2048 MB) avail memory = 2080759808 (1984 MB) cpu0: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) cpu1: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413, REGOPS_FUNC) nexus0: cryptosoft1: mem 0x1fe00004000-0x1fe00005fff,0x1fe01000000-0x1fe010000ff,0x1fe00000000-0x1fe0000cfff irq 2033,2030,2031,2021,2024,2034 on nexus0 cryptosoft2: mem 0x1fe00002000-0x1fe00003fff,0x1fe01800000-0x1fe018000ff,0x1fe00000000-0x1fe0000cfff irq 2032,2030,2031,2021,2024,2034 on nexus0 cryptosoft3: mem 0x1fc00000000-0x1fc000003ff,0x1fc00400000-0x1fc005fffff,0x1fc00600000-0x1fc007fffff,0x1fc01000000-0x1fc013fffff,0x1fc01400000-0x1fc017fffff,0x1fc01800000-0x1fc01bfffff,0x1fc01c00000-0x1fc01ffffff,0x1fc02000000-0x1fc02ffffff,0x1fc03000000-0x1fc03ffffff,0x1fc04000000-0x1fc043fffff,0x1fc04400000-0x1fc047fffff,0x1fc04800000-0x1fc04bfffff,0x1fc04c00000-0x1fc04ffffff,0x1fc05000000-0x1fc05ffffff,0x1fc06000000-0x1fc07ffffff,0x1fc09000000-0x1fc097fffff,0x1fc09800000-0x1fc09ffffff,0x1fc0a000000-0x1fc0affffff,0x1fc0b000000-0x1fc0b7fffff,0x1fc0b800000-0x1fc0bffffff,0x1fc0c000000-0x1fc0c3fffff,0x1fc0c800000-0x1fc0cffffff,0x1fc0d000000-0x1fc0d7fffff,0x1fc0d800000-0x1fc0dffffff irq 1925 on nexus0 cryptosoft0: on nexus0 nexus0: type unknown (no driver attached) Timecounters tick every 1.000 msec SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/da0a Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroot> From christian.baer at uni-dortmund.de Wed May 14 08:07:17 2008 From: christian.baer at uni-dortmund.de (Christian Baer) Date: Wed May 14 08:07:24 2008 Subject: Kernel with crypto and geli won't mount / Message-ID: Hi there, people! I hope this isn't a double post! I noticed that my eMail-address in the original post was wrong, so I'm guessing it was filtered. I have a little problem here that is bringing me some headaches. :-( I am not sure if this is a GEOM-problem or one caused by the current -STABLE fork, so I'll put this question in here too. Please excuse my haste. The computer I tried to "remake" has been down for several days now and that's never good. Sunday I set up a new FreeBSD 7.0 system (sparc64). This is a Sun U60 and worked fine for me for ages under 6.3. Installing went without any problems. The problems started, when I updated the sources (due to a security issue) to RELENG_7. I made a new world and a new kernel. I did change the kernel-config by adding two lines: options GEOM_ELI device crypto Well, technically I did a fair bit more than that, but when I ran into problems, I went back to a generic kernel with just these two extra lines. What this boils down to is that adding GEOM_ELI and crypto to the kernel seems to make my / unmountable (see dmesg after my sig). The generic kernel works fine but that isn't quite good enough because I have two encrypted providers on the drives - these were created under the old Version though. One other thing might be worth mentioning: The system has two configured gmirrors (the encrypted providers are on top of those). These are not needed at boot time though and AFAIK no atempts to configure them are being made. Although I did back up my data it would be a lot easier to just keep them as they are instead of having to remake them. Did I mess up somewhere or am I missing the point. Regards Chris Here the dmesg: Booting [/boot/kernel/kernel]... nothing to autoload yet. jumping to kernel entry at 0xc0078000. stray vector interrupt 2029 Copyright (c) 1992-2008 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.0-STABLE #3: Tue May 13 09:32:42 CEST 2008 root@sunny.rz1.convenimus.net:/usr/obj/usr/src/sys/SUNNY real memory = 2147483648 (2048 MB) avail memory = 2080759808 (1984 MB) cpu0: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) cpu1: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413, REGOPS_FUNC) nexus0: cryptosoft1: mem 0x1fe00004000-0x1fe00005fff,0x1fe01000000-0x1fe010000ff,0x1fe00000000-0x1fe0000cfff irq 2033,2030,2031,2021,2024,2034 on nexus0 cryptosoft2: mem 0x1fe00002000-0x1fe00003fff,0x1fe01800000-0x1fe018000ff,0x1fe00000000-0x1fe0000cfff irq 2032,2030,2031,2021,2024,2034 on nexus0 cryptosoft3: mem 0x1fc00000000-0x1fc000003ff,0x1fc00400000-0x1fc005fffff,0x1fc00600000-0x1fc007fffff,0x1fc01000000-0x1fc013fffff,0x1fc01400000-0x1fc017fffff,0x1fc01800000-0x1fc01bfffff,0x1fc01c00000-0x1fc01ffffff,0x1fc02000000-0x1fc02ffffff,0x1fc03000000-0x1fc03ffffff,0x1fc04000000-0x1fc043fffff,0x1fc04400000-0x1fc047fffff,0x1fc04800000-0x1fc04bfffff,0x1fc04c00000-0x1fc04ffffff,0x1fc05000000-0x1fc05ffffff,0x1fc06000000-0x1fc07ffffff,0x1fc09000000-0x1fc097fffff,0x1fc09800000-0x1fc09ffffff,0x1fc0a000000-0x1fc0affffff,0x1fc0b000000-0x1fc0b7fffff,0x1fc0b800000-0x1fc0bffffff,0x1fc0c000000-0x1fc0c3fffff,0x1fc0c800000-0x1fc0cffffff,0x1fc0d000000-0x1fc0d7fffff,0x1fc0d800000-0x1fc0dffffff irq 1925 on nexus0 cryptosoft0: on nexus0 nexus0: type unknown (no driver attached) Timecounters tick every 1.000 msec SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/da0a Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroot> From oxy at field.hu Wed May 14 08:28:23 2008 From: oxy at field.hu (oxy) Date: Wed May 14 08:28:34 2008 Subject: Kernel with crypto and geli won't mount / In-Reply-To: References: Message-ID: <482A9F05.1060909@field.hu> in your dmesg i don't see the mirrors.. did you compiled it in the kernel too? (or just load the module) after you load gmirror, geli will work too Christian Baer ?rta: > Hi there, people! > > I hope this isn't a double post! I noticed that my eMail-address in > the original post was wrong, so I'm guessing it was filtered. > > I have a little problem here that is bringing me some headaches. :-( > I am not sure if this is a GEOM-problem or one caused by the current > -STABLE fork, so I'll put this question in here too. Please excuse my > haste. The computer I tried to "remake" has been down for several days > now and that's never good. > > Sunday I set up a new FreeBSD 7.0 system (sparc64). This is a Sun U60 > and worked fine for me for ages under 6.3. Installing went without any > problems. The problems started, when I updated the sources (due to a > security issue) to RELENG_7. I made a new world and a new kernel. I > did change the kernel-config by adding two lines: > > options GEOM_ELI > device crypto > > Well, technically I did a fair bit more than that, but when I ran into > problems, I went back to a generic kernel with just these two extra > lines. What this boils down to is that adding GEOM_ELI and crypto to > the kernel seems to make my / unmountable (see dmesg after my sig). > The generic kernel works fine but that isn't quite good enough because > I have two encrypted providers on the drives - these were created > under the old Version though. > > One other thing might be worth mentioning: The system has two > configured gmirrors (the encrypted providers are on top of those). > These are not needed at boot time though and AFAIK no atempts to > configure them are being made. Although I did back up my data it would > be a lot easier to just keep them as they are instead of having to > remake them. > > Did I mess up somewhere or am I missing the point. > > Regards > Chris > > Here the dmesg: > Booting [/boot/kernel/kernel]... > nothing to autoload yet. > jumping to kernel entry at 0xc0078000. > stray vector interrupt 2029 > Copyright (c) 1992-2008 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.0-STABLE #3: Tue May 13 09:32:42 CEST 2008 > root@sunny.rz1.convenimus.net:/usr/obj/usr/src/sys/SUNNY > real memory = 2147483648 (2048 MB) > avail memory = 2080759808 (1984 MB) > cpu0: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) > cpu1: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > RF5413, REGOPS_FUNC) > nexus0: > cryptosoft1: mem > 0x1fe00004000-0x1fe00005fff,0x1fe01000000-0x1fe010000ff,0x1fe00000000-0x1fe0000cfff > irq 2033,2030,2031,2021,2024,2034 on nexus0 > cryptosoft2: mem > 0x1fe00002000-0x1fe00003fff,0x1fe01800000-0x1fe018000ff,0x1fe00000000-0x1fe0000cfff > irq 2032,2030,2031,2021,2024,2034 on nexus0 > cryptosoft3: mem > 0x1fc00000000-0x1fc000003ff,0x1fc00400000-0x1fc005fffff,0x1fc00600000-0x1fc007fffff,0x1fc01000000-0x1fc013fffff,0x1fc01400000-0x1fc017fffff,0x1fc01800000-0x1fc01bfffff,0x1fc01c00000-0x1fc01ffffff,0x1fc02000000-0x1fc02ffffff,0x1fc03000000-0x1fc03ffffff,0x1fc04000000-0x1fc043fffff,0x1fc04400000-0x1fc047fffff,0x1fc04800000-0x1fc04bfffff,0x1fc04c00000-0x1fc04ffffff,0x1fc05000000-0x1fc05ffffff,0x1fc06000000-0x1fc07ffffff,0x1fc09000000-0x1fc097fffff,0x1fc09800000-0x1fc09ffffff,0x1fc0a000000-0x1fc0affffff,0x1fc0b000000-0x1fc0b7fffff,0x1fc0b800000-0x1fc0bffffff,0x1fc0c000000-0x1fc0c3fffff,0x1fc0c800000-0x1fc0cffffff,0x1fc0d000000-0x1fc0d7fffff,0x1fc0d800000-0x1fc0dffffff > irq 1925 on nexus0 > cryptosoft0: on nexus0 > nexus0: type unknown (no driver attached) > Timecounters tick every 1.000 msec > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/da0a > > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:/dev/da0a > ? List valid disk boot devices > Abort manual input > > mountroot> > _______________________________________________ > 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 christian.baer at uni-dortmund.de Wed May 14 08:50:10 2008 From: christian.baer at uni-dortmund.de (Christian Baer) Date: Wed May 14 08:50:14 2008 Subject: Kernel with crypto and geli won't mount / In-Reply-To: <482A9F05.1060909@field.hu> References: <482A9F05.1060909@field.hu> Message-ID: oxy wrote: > in your dmesg i don't see the mirrors.. > did you compiled it in the kernel too? > (or just load the module) > after you load gmirror, geli will work too No, I did not compile gmirror into the kernel. Normally, the gmirrors are started by gmirror load In case this wasn't clear: There are two gmirrors on the drives and on top of these are two encrypted providers (so basicly, the mirrors are encrypted). Neither are needed at boot time! Here is my fstab: # Device Mountpoint FStype Options Dump Pass# /dev/da0b none swap sw 0 0 /dev/da0a / ufs rw,sync 1 1 /dev/da0h /tmp ufs rw,async 2 2 /dev/da1f /usr ufs rw 2 2 /dev/da0f /usr/obj ufs rw,async 2 2 /dev/da0g /var ufs rw 2 2 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 The mirrors *are* on these two physical drives but only contain data (as in blueprints, letters, project photos, contracts etc.). So basicly, the mirrors and geli aren't needed for FreeBSD itself but only to access the data stored on the system. And my problem is that FreeBSD won't even boot when I compile geli and crypto into the kernel - although neither are needed at boot time. So either there is a code problem somewhere or I need to change something that I couldn't find documented anywhere so far. Regards Chris From pjd at FreeBSD.org Wed May 14 10:36:55 2008 From: pjd at FreeBSD.org (Pawel Jakub Dawidek) Date: Wed May 14 10:37:26 2008 Subject: Kernel with crypto and geli won't mount / In-Reply-To: References: Message-ID: <20080514103643.GA4061@garage.freebsd.pl> On Wed, May 14, 2008 at 10:07:05AM +0200, Christian Baer wrote: > Hi there, people! > > I hope this isn't a double post! I noticed that my eMail-address in the > original post was wrong, so I'm guessing it was filtered. > > I have a little problem here that is bringing me some headaches. :-( > I am not sure if this is a GEOM-problem or one caused by the current > -STABLE fork, so I'll put this question in here too. Please excuse my > haste. The computer I tried to "remake" has been down for several days > now and that's never good. > > Sunday I set up a new FreeBSD 7.0 system (sparc64). This is a Sun U60 > and worked fine for me for ages under 6.3. Installing went without any > problems. The problems started, when I updated the sources (due to a > security issue) to RELENG_7. I made a new world and a new kernel. I did > change the kernel-config by adding two lines: > > options GEOM_ELI > device crypto > > Well, technically I did a fair bit more than that, but when I ran into > problems, I went back to a generic kernel with just these two extra > lines. What this boils down to is that adding GEOM_ELI and crypto to the > kernel seems to make my / unmountable (see dmesg after my sig). The > generic kernel works fine but that isn't quite good enough because I > have two encrypted providers on the drives - these were created under > the old Version though. > > One other thing might be worth mentioning: The system has two configured > gmirrors (the encrypted providers are on top of those). These are not > needed at boot time though and AFAIK no atempts to configure them are > being made. Although I did back up my data it would be a lot easier to > just keep them as they are instead of having to remake them. > > Did I mess up somewhere or am I missing the point. > > Regards > Chris > > Here the dmesg: > Booting [/boot/kernel/kernel]... > nothing to autoload yet. > jumping to kernel entry at 0xc0078000. > stray vector interrupt 2029 > Copyright (c) 1992-2008 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.0-STABLE #3: Tue May 13 09:32:42 CEST 2008 > root@sunny.rz1.convenimus.net:/usr/obj/usr/src/sys/SUNNY > real memory = 2147483648 (2048 MB) > avail memory = 2080759808 (1984 MB) > cpu0: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) > cpu1: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > registered firmware set > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > RF5413, REGOPS_FUNC) > nexus0: > cryptosoft1: mem > 0x1fe00004000-0x1fe00005fff,0x1fe01000000-0x1fe010000ff,0x1fe00000000-0x1fe0000cfff > irq 2033,2030,2031,2021,2024,2034 on nexus0 > cryptosoft2: mem > 0x1fe00002000-0x1fe00003fff,0x1fe01800000-0x1fe018000ff,0x1fe00000000-0x1fe0000cfff > irq 2032,2030,2031,2021,2024,2034 on nexus0 > cryptosoft3: mem > 0x1fc00000000-0x1fc000003ff,0x1fc00400000-0x1fc005fffff,0x1fc00600000-0x1fc007fffff,0x1fc01000000-0x1fc013fffff,0x1fc01400000-0x1fc017fffff,0x1fc01800000-0x1fc01bfffff,0x1fc01c00000-0x1fc01ffffff,0x1fc02000000-0x1fc02ffffff,0x1fc03000000-0x1fc03ffffff,0x1fc04000000-0x1fc043fffff,0x1fc04400000-0x1fc047fffff,0x1fc04800000-0x1fc04bfffff,0x1fc04c00000-0x1fc04ffffff,0x1fc05000000-0x1fc05ffffff,0x1fc06000000-0x1fc07ffffff,0x1fc09000000-0x1fc097fffff,0x1fc09800000-0x1fc09ffffff,0x1fc0a000000-0x1fc0affffff,0x1fc0b000000-0x1fc0b7fffff,0x1fc0b800000-0x1fc0bffffff,0x1fc0c000000-0x1fc0c3fffff,0x1fc0c800000-0x1fc0cffffff,0x1fc0d000000-0x1fc0d7fffff,0x1fc0d800000-0x1fc0dffffff > irq 1925 on nexus0 > cryptosoft0: on nexus0 > nexus0: type unknown (no driver attached) > Timecounters tick every 1.000 msec > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/da0a > > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:/dev/da0a > ? List valid disk boot devices > Abort manual input Is this full dmesg? I don't see your da0 disk beeing detected. Are you sure you have required SCSI driver compiled into your kernel? Are you suggesting that simply removing 'options GEOM_ELI' and 'device crypto' from your kernel configuration makes your system to boot again? -- 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/20080514/0d6561fa/attachment.pgp From vwe at FreeBSD.org Wed May 14 11:38:08 2008 From: vwe at FreeBSD.org (vwe@FreeBSD.org) Date: Wed May 14 11:38:15 2008 Subject: kern/123630: [patch] [gmirror] gmirror doesnt allow the original drive to be preferred Message-ID: <200805141138.m4EBc7SL065797@freefall.freebsd.org> Old Synopsis: gmirror doesnt allow the original drive to be preferred (patch included) New Synopsis: [patch] [gmirror] gmirror doesnt allow the original drive to be preferred Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: vwe Responsible-Changed-When: Wed May 14 11:37:13 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=123630 From vwe at FreeBSD.org Wed May 14 21:02:23 2008 From: vwe at FreeBSD.org (vwe@FreeBSD.org) Date: Wed May 14 21:02:25 2008 Subject: kern/121364: [gmirror] Removing all providers create a "zombie" mirror Message-ID: <200805142102.m4EL2K5v016594@freefall.freebsd.org> Synopsis: [gmirror] Removing all providers create a "zombie" mirror State-Changed-From-To: feedback->open State-Changed-By: vwe State-Changed-When: Wed May 14 21:02:05 UTC 2008 State-Changed-Why: Feedback has been provided. http://www.freebsd.org/cgi/query-pr.cgi?pr=121364 From christian.baer at uni-dortmund.de Wed May 14 23:18:29 2008 From: christian.baer at uni-dortmund.de (Christian Baer) Date: Wed May 14 23:18:33 2008 Subject: Kernel with crypto and geli won't mount / In-Reply-To: <20080514103643.GA4061@garage.freebsd.pl> References: <20080514103643.GA4061@garage.freebsd.pl> Message-ID: Pawel Jakub Dawidek wrote: > Is this full dmesg? Yup. > I don't see your da0 disk beeing detected. Are you > sure you have required SCSI driver compiled into your kernel? This is the GENERIC kernel, so yeah, I'm sure. > Are you suggesting that simply removing 'options GEOM_ELI' and 'device > crypto' from your kernel configuration makes your system to boot again? That is exactly what I am suggesting. As I wrote, I did this: cp GENERIC MYKERNEL vi MYKERNEL (add "options GEOM_ELI" and "device crypto") cd /usr/src make -j 2 buildkernel KERNCONF=MYKERNEL [1] make installkernel KERNCONF=MYKERNEL [1] reboot Then, the system doesn't boot. If I leave them (GEOM_ELI and crypto) out, the system boots again. Just to be sure about this though, I went back to my kernelconf-file (MYKERNEL), which created a non-bootable kernel. I commented GEOM_ELI and crypto out and built a new kernel. A few minutes ago I rebooted the system successfully with that kernel. Putting dmesg in at the end of this post. It's quite long, so don't complain. :-) Complete MYKERNEL can be posted if needed. Have I discovered a major bug here? Regards Chris [1] Actually, I didn't set the config on the command line, but instead set it in /etc/make.conf, which shouldn't make a difference because the system stated that it was finished with MYKERNEL. sunny# dmesg stray vector interrupt 2029 Copyright (c) 1992-2008 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.0-RELEASE #0: Mon Feb 25 09:35:41 UTC 2008 root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC real memory = 2147483648 (2048 MB) avail memory = 2080759808 (1984 MB) cpu0: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) cpu1: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413, REGOPS_FUNC) nexus0: pcib0: mem 0x1fe00004000-0x1fe00005fff,0x1fe01000000-0x1fe010000ff,0x1fe00000000-0x1fe0000cfff irq 2033,2030,2031,2021,2024,2034 on nexus0 pcib0: Psycho, impl 0, version 4, IGN 0x1f, bus B pcib0: [FILTER] pcib0: [FILTER] pcib0: [GIANT-LOCKED] pcib0: [ITHREAD] pcib0: [GIANT-LOCKED] pcib0: [ITHREAD] initializing counter-timer Timecounter "counter-timer" frequency 1000000 Hz quality 100 pcib0 dvma: DVMA map: 0xfc000000 to 0xffffffff pcib0: [FILTER] pci0: on pcib0 ebus0: mem 0x70000000-0x70ffffff,0x71000000-0x717fffff at device 1.0 on pci0 auxio0: addr 0x1400726000-0x1400726003,0x1400728000-0x1400728003,0x140072a000-0x140072a003,0x140072c000-0x140072c003,0x140072f000-0x140072f003 on ebus0 ebus0: addr 0x1400724000-0x1400724003 (no driver attached) ebus0: addr 0x1400504000-0x1400504002 (no driver attached) ebus0: addr 0x1400500000-0x1400500007 (no driver attached) scc0: addr 0x1400400000-0x140040007f irq 43 on ebus0 scc0: [FILTER] uart0: on scc0 uart0: [FILTER] uart0: CTS oflow uart0: console (9600,n,8,1) uart1: on scc0 uart1: [FILTER] uart1: CTS oflow uart2: <16550 or compatible> addr 0x14003083f8-0x14003083ff irq 41 on ebus0 uart2: [FILTER] uart2: keyboard (1200,n,8,1) uart2: keyboard not present uart3: <16550 or compatible> addr 0x14003062f8-0x14003062ff irq 42 on ebus0 uart3: [FILTER] ebus0: addr 0x14003043bc-0x14003043cb,0x1400300398-0x1400300399,0x1400700000-0x140070000f irq 34 (no driver attached) ebus0: addr 0x14003023f0-0x14003023f7,0x1400706000-0x140070600f,0x1400720000-0x1400720003 irq 39 (no driver attached) eeprom0: addr 0x1400000000-0x1400001fff on ebus0 eeprom0: model mk48t59 ebus0: addr 0x1000000000-0x10000fffff (no driver attached) ebus0: addr 0x1400200000-0x14002000ff,0x1400702000-0x140070200f,0x1400704000-0x140070400f,0x1400722000-0x1400722003 irq 35,36 (no driver attached) hme0: mem 0x100000-0x107fff at device 1.1 on pci0 miibus0: on hme0 ukphy0: PHY 1 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto hme0: Ethernet address: 08:00:20:e5:f2:5b hme0: [ITHREAD] sym0: <875> port 0x1000-0x10ff mem 0x108000-0x1080ff,0x10a000-0x10afff at device 3.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym0: [GIANT-LOCKED] sym0: [ITHREAD] sym1: <875> port 0x1400-0x14ff mem 0x10c000-0x10c0ff,0x10e000-0x10efff at device 3.1 on pci0 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: [GIANT-LOCKED] sym1: [ITHREAD] pcib1: mem 0x1fe00002000-0x1fe00003fff,0x1fe01800000-0x1fe018000ff,0x1fe00000000-0x1fe0000cfff irq 2032,2030,2031,2021,2024,2034 on nexus0 pcib1: Psycho, impl 0, version 4, IGN 0x1f, bus A pcib1: [FILTER] pci1: on pcib1 creator0: mem 0x1fc00000000-0x1fc000003ff,0x1fc00400000-0x1fc005fffff,0x1fc00600000-0x1fc007fffff,0x1fc01000000-0x1fc013fffff,0x1fc01400000-0x1fc017fffff,0x1fc01800000-0x1fc01bfffff,0x1fc01c00000-0x1fc01ffffff,0x1fc02000000-0x1fc02ffffff,0x1fc03000000-0x1fc03ffffff,0x1fc04000000-0x1fc043fffff,0x1fc04400000-0x1fc047fffff,0x1fc04800000-0x1fc04bfffff,0x1fc04c00000-0x1fc04ffffff,0x1fc05000000-0x1fc05ffffff,0x1fc06000000-0x1fc07ffffff,0x1fc09000000-0x1fc097fffff,0x1fc09800000-0x1fc09ffffff,0x1fc0a000000-0x1fc0affffff,0x1fc0b000000-0x1fc0b7fffff,0x1fc0b800000-0x1fc0bffffff,0x1fc0c000000-0x1fc0c3fffff,0x1fc0c800000-0x1fc0cffffff,0x1fc0d000000-0x1fc0d7fffff,0x1fc0d800000-0x1fc0dffffff irq 1925 on nexus0 creator0: resolution 1152x900 syscons0: on nexus0 syscons0: Unknown <16 virtual consoles, flags=0x100> Timecounters tick every 1.000 msec Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit) da1: Command Queueing Enabled da1: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit) da0: Command Queueing Enabled da0: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) cd0 at sym0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/da0a hme0: device timeout Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...1 0 1 0 0 0 done All buffers synced. stray vector interrupt 2029 Copyright (c) 1992-2008 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.0-STABLE #1: Wed May 14 18:21:54 CEST 2008 root@sunny.rz1.convenimus.net:/usr/obj/usr/src/sys/SUNNY real memory = 2147483648 (2048 MB) avail memory = 2080759808 (1984 MB) cpu0: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) cpu1: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413, REGOPS_FUNC) nexus0: pcib0: mem 0x1fe00004000-0x1fe00005fff,0x1fe01000000-0x1fe010000ff,0x1fe00000000-0x1fe0000cfff irq 2033,2030,2031,2021,2024,2034 on nexus0 pcib0: Psycho, impl 0, version 4, IGN 0x1f, bus B pcib0: [FILTER] pcib0: [FILTER] pcib0: [GIANT-LOCKED] pcib0: [ITHREAD] pcib0: [GIANT-LOCKED] pcib0: [ITHREAD] initializing counter-timer Timecounter "counter-timer" frequency 1000000 Hz quality 100 pcib0 dvma: DVMA map: 0xfc000000 to 0xffffffff pcib0: [FILTER] pci0: on pcib0 ebus0: mem 0x70000000-0x70ffffff,0x71000000-0x717fffff at device 1.0 on pci0 auxio0: addr 0x1400726000-0x1400726003,0x1400728000-0x1400728003,0x140072a000-0x140072a003,0x140072c000-0x140072c003,0x140072f000-0x140072f003 on ebus0 ebus0: addr 0x1400724000-0x1400724003 (no driver attached) ebus0: addr 0x1400504000-0x1400504002 (no driver attached) ebus0: addr 0x1400500000-0x1400500007 (no driver attached) scc0: addr 0x1400400000-0x140040007f irq 43 on ebus0 scc0: [FILTER] uart0: on scc0 uart0: [FILTER] uart0: CTS oflow uart0: console (9600,n,8,1) uart1: on scc0 uart1: [FILTER] uart1: CTS oflow uart2: <16550 or compatible> addr 0x14003083f8-0x14003083ff irq 41 on ebus0 uart2: [FILTER] uart2: keyboard (1200,n,8,1) uart2: keyboard not present uart3: <16550 or compatible> addr 0x14003062f8-0x14003062ff irq 42 on ebus0 uart3: [FILTER] ebus0: addr 0x14003043bc-0x14003043cb,0x1400300398-0x1400300399,0x1400700000-0x140070000f irq 34 (no driver attached) ebus0: addr 0x14003023f0-0x14003023f7,0x1400706000-0x140070600f,0x1400720000-0x1400720003 irq 39 (no driver attached) eeprom0: addr 0x1400000000-0x1400001fff on ebus0 eeprom0: model mk48t59 ebus0: addr 0x1000000000-0x10000fffff (no driver attached) ebus0: addr 0x1400200000-0x14002000ff,0x1400702000-0x140070200f,0x1400704000-0x140070400f,0x1400722000-0x1400722003 irq 35,36 (no driver attached) hme0: mem 0x100000-0x107fff at device 1.1 on pci0 miibus0: on hme0 ukphy0: PHY 1 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto hme0: Ethernet address: 08:00:20:e5:f2:5b hme0: [ITHREAD] sym0: <875> port 0x1000-0x10ff mem 0x108000-0x1080ff,0x10a000-0x10afff at device 3.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym0: [GIANT-LOCKED] sym0: [ITHREAD] sym1: <875> port 0x1400-0x14ff mem 0x10c000-0x10c0ff,0x10e000-0x10efff at device 3.1 on pci0 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: [GIANT-LOCKED] sym1: [ITHREAD] pcib1: mem 0x1fe00002000-0x1fe00003fff,0x1fe01800000-0x1fe018000ff,0x1fe00000000-0x1fe0000cfff irq 2032,2030,2031,2021,2024,2034 on nexus0 pcib1: Psycho, impl 0, version 4, IGN 0x1f, bus A pcib1: [FILTER] pci1: on pcib1 creator0: mem 0x1fc00000000-0x1fc000003ff,0x1fc00400000-0x1fc005fffff,0x1fc00600000-0x1fc007fffff,0x1fc01000000-0x1fc013fffff,0x1fc01400000-0x1fc017fffff,0x1fc01800000-0x1fc01bfffff,0x1fc01c00000-0x1fc01ffffff,0x1fc02000000-0x1fc02ffffff,0x1fc03000000-0x1fc03ffffff,0x1fc04000000-0x1fc043fffff,0x1fc04400000-0x1fc047fffff,0x1fc04800000-0x1fc04bfffff,0x1fc04c00000-0x1fc04ffffff,0x1fc05000000-0x1fc05ffffff,0x1fc06000000-0x1fc07ffffff,0x1fc09000000-0x1fc097fffff,0x1fc09800000-0x1fc09ffffff,0x1fc0a000000-0x1fc0affffff,0x1fc0b000000-0x1fc0b7fffff,0x1fc0b800000-0x1fc0bffffff,0x1fc0c000000-0x1fc0c3fffff,0x1fc0c800000-0x1fc0cffffff,0x1fc0d000000-0x1fc0d7fffff,0x1fc0d800000-0x1fc0dffffff irq 1925 on nexus0 creator0: resolution 1152x900 syscons0: on nexus0 syscons0: Unknown <16 virtual consoles, flags=0x100> Timecounters tick every 1.000 msec Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit) da1: Command Queueing Enabled da1: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit) da0: Command Queueing Enabled da0: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) cd0 at sym0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/da0a From pjd at FreeBSD.org Sat May 17 03:09:00 2008 From: pjd at FreeBSD.org (pjd@FreeBSD.org) Date: Sat May 17 03:09:02 2008 Subject: kern/123606: [geli] Executing files on encrypted usb stick fails with g_vfs_done() error = 22 Message-ID: <200805170308.m4H38xi5020717@freefall.freebsd.org> Synopsis: [geli] Executing files on encrypted usb stick fails with g_vfs_done() error = 22 State-Changed-From-To: feedback->closed State-Changed-By: pjd State-Changed-When: sob 17 maj 03:08:38 2008 UTC State-Changed-Why: Close per submitter request. http://www.freebsd.org/cgi/query-pr.cgi?pr=123606 From bugmaster at FreeBSD.org Mon May 19 11:06:52 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 19 11:07:05 2008 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200805191106.m4JB6qOW011566@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/73177 geom kldload geom_* causes panic due to memory exhaustion o kern/76538 geom [gbde] nfs-write on gbde partition stalls and continue o kern/83464 geom [geom] [patch] Unhandled malloc failures within libgeo o kern/84556 geom [geom] GBDE-encrypted swap causes panic at shutdown o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/89546 geom [geom] GEOM error o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/113419 geom [geom] geom fox multipathing not failing back o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/115572 geom [gbde] [patch] gbde partitions fail at 28bit/48bit LBA o kern/120021 geom net-p2p/qbittorrent crashes system when it works thoug o kern/120231 geom [geom] GEOM_CONCAT error adding second drive o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/122067 geom [panic]: Geom crashed during boot f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/123122 geom GEOM / gjournal kernel lock 20 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/78131 geom gbde "destroy" not working. o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/121559 geom [patch] [geom] geom label class allows to create inacc f kern/121907 geom [request] [geom] geom output to console obscures other o kern/123630 geom [patch] [gmirror] gmirror doesnt allow the original dr 14 problems total. From linimon at FreeBSD.org Mon May 19 20:00:54 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon May 19 20:00:57 2008 Subject: bin/75632: gvinum(8) commands not consistent with vinum doc Message-ID: <200805192000.m4JK0sAd061465@freefall.freebsd.org> Old Synopsis: gvinum commands not consistent with vinum doc New Synopsis: gvinum(8) commands not consistent with vinum doc Responsible-Changed-From-To: le->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 19 19:59:49 UTC 2008 Responsible-Changed-Why: With bugmeister hat on, reassign as le@ has not been active in a while. http://www.freebsd.org/cgi/query-pr.cgi?pr=75632 From linimon at FreeBSD.org Mon May 19 20:01:18 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon May 19 20:01:20 2008 Subject: kern/79035: [vinum] gvinum unable to create a striped set of mirrored sets/plexes Message-ID: <200805192001.m4JK1IQU061519@freefall.freebsd.org> Synopsis: [vinum] gvinum unable to create a striped set of mirrored sets/plexes Responsible-Changed-From-To: le->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 19 20:01:03 UTC 2008 Responsible-Changed-Why: With bugmeister hat on, reassign as le@ has not been active in a while. http://www.freebsd.org/cgi/query-pr.cgi?pr=79035 From linimon at FreeBSD.org Mon May 19 20:02:17 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon May 19 20:02:19 2008 Subject: kern/89660: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done Message-ID: <200805192002.m4JK2Gho061572@freefall.freebsd.org> Old Synopsis: [patch] [panic] due to g_malloc returning null in gv_drive_done New Synopsis: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done Responsible-Changed-From-To: le->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 19 20:01:32 UTC 2008 Responsible-Changed-Why: With bugmeister hat on, reassign as le@ has not been active in a while. http://www.freebsd.org/cgi/query-pr.cgi?pr=89660 From antik at bsd.ee Tue May 20 11:42:59 2008 From: antik at bsd.ee (Andrei Kolu) Date: Tue May 20 11:43:05 2008 Subject: gjournal misconfiguration Message-ID: <200805201423.56220.antik@bsd.ee> I created geom journal according to this documentation: http://www.freebsd.org/doc/en/books/handbook/geom-gjournal.html I already had partition on second drive (da1s1d) # gjournal label -f /dev/da1s1d # gjournal load # newfs -O 2 -J /dev/da1s1d.journal # mount /dev/da1s1d.journal /data everything worked fine until I rebooted with this fstab: ---------------------------------------------------------- # geom_journaling /dev/da1s1d.journal /data ufs rw 3 3 ---------------------------------------------------------- FreeBSD failed to boot- because it said there is no such a filesystem....bah. then I looked at /dev/da* and found this: crw-r----- 1 root operator 0, 105 May 20 13:52 /dev/da1s1.journal crw-r----- 1 root operator 0, 106 May 20 13:52 /dev/da1s1.journalc crw-r----- 1 root operator 0, 107 May 20 16:52 /dev/da1s1.journald Changed /etc/fstab: ---------------------------------------------------------- # geom_journaling /dev/da1s1.journald /data ufs rw 3 3 ---------------------------------------------------- Now everything works fine except this error message: GEOM_JOURNAL: Journal 2508477697: da1s1 contains data. GEOM_JOURNAL: Journal 2508477697: da1s1 contains journal. GEOM_JOURNAL: Journal da1s1 clean. WARNING: Expected rawoffset 0, found 63 Whats wrong? From 000.fbsd at quip.cz Tue May 20 14:18:29 2008 From: 000.fbsd at quip.cz (Miroslav Lachman) Date: Tue May 20 14:18:34 2008 Subject: gjournal misconfiguration In-Reply-To: <200805201423.56220.antik@bsd.ee> References: <200805201423.56220.antik@bsd.ee> Message-ID: <4832D989.60607@quip.cz> Andrei Kolu wrote: > I created geom journal according to this documentation: > http://www.freebsd.org/doc/en/books/handbook/geom-gjournal.html > > I already had partition on second drive (da1s1d) > > # gjournal label -f /dev/da1s1d > # gjournal load > # newfs -O 2 -J /dev/da1s1d.journal > # mount /dev/da1s1d.journal /data > > everything worked fine until I rebooted with this fstab: > ---------------------------------------------------------- > # geom_journaling > /dev/da1s1d.journal /data ufs rw 3 3 > ---------------------------------------------------------- > > FreeBSD failed to boot- because it said there is no such a filesystem....bah. > > then I looked at /dev/da* and found this: > > crw-r----- 1 root operator 0, 105 May 20 13:52 /dev/da1s1.journal > crw-r----- 1 root operator 0, 106 May 20 13:52 /dev/da1s1.journalc > crw-r----- 1 root operator 0, 107 May 20 16:52 /dev/da1s1.journald > > Changed /etc/fstab: > ---------------------------------------------------------- > # geom_journaling > /dev/da1s1.journald /data ufs rw 3 3 > ---------------------------------------------------- > > Now everything works fine except this error message: > > GEOM_JOURNAL: Journal 2508477697: da1s1 contains data. > GEOM_JOURNAL: Journal 2508477697: da1s1 contains journal. > GEOM_JOURNAL: Journal da1s1 clean. > WARNING: Expected rawoffset 0, found 63 I think I saw this behaviour if slice contains previously created partitions with 0 offset. (bsdlabel /dev/da1s1 will show you). Try create it again, but do bsdlabel -e before journaling, set all offsets to * (asterisk) and save new label. (remember you will lose you data! so do backup before) Miroslav Lachman From antik at bsd.ee Wed May 21 08:21:56 2008 From: antik at bsd.ee (Andrei Kolu) Date: Wed May 21 08:22:07 2008 Subject: gjournal misconfiguration In-Reply-To: <4832D989.60607@quip.cz> References: <200805201423.56220.antik@bsd.ee> <4832D989.60607@quip.cz> Message-ID: <200805211121.53354.antik@bsd.ee> On Tuesday 20 May 2008 17:00:41 Miroslav Lachman wrote: > Andrei Kolu wrote: > > I created geom journal according to this documentation: > > http://www.freebsd.org/doc/en/books/handbook/geom-gjournal.html > > > > I already had partition on second drive (da1s1d) > > > > # gjournal label -f /dev/da1s1d > > # gjournal load > > # newfs -O 2 -J /dev/da1s1d.journal > > # mount /dev/da1s1d.journal /data > > > > everything worked fine until I rebooted with this fstab: > > ---------------------------------------------------------- > > # geom_journaling > > /dev/da1s1d.journal /data ufs rw 3 3 > > ---------------------------------------------------------- > > > > FreeBSD failed to boot- because it said there is no such a > > filesystem....bah. > > > > then I looked at /dev/da* and found this: > > > > crw-r----- 1 root operator 0, 105 May 20 13:52 /dev/da1s1.journal > > crw-r----- 1 root operator 0, 106 May 20 13:52 /dev/da1s1.journalc > > crw-r----- 1 root operator 0, 107 May 20 16:52 /dev/da1s1.journald > > > > Changed /etc/fstab: > > ---------------------------------------------------------- > > # geom_journaling > > /dev/da1s1.journald /data ufs rw 3 3 > > ---------------------------------------------------- > > > > Now everything works fine except this error message: > > > > GEOM_JOURNAL: Journal 2508477697: da1s1 contains data. > > GEOM_JOURNAL: Journal 2508477697: da1s1 contains journal. > > GEOM_JOURNAL: Journal da1s1 clean. > > WARNING: Expected rawoffset 0, found 63 > > I think I saw this behaviour if slice contains previously created > partitions with 0 offset. (bsdlabel /dev/da1s1 will show you). > > Try create it again, but do bsdlabel -e before journaling, set all > offsets to * (asterisk) and save new label. (remember you will lose you > data! so do backup before) > Ok, I'll try to clean up old partition but what amused me is that when I created journaling manually it worked and same time it does not work with same device names from /etc/fstab. to me: /dev/da1s1d.journal == /dev/da1s1.journald does it make any sense? From lulf at FreeBSD.org Wed May 21 17:50:09 2008 From: lulf at FreeBSD.org (lulf@FreeBSD.org) Date: Wed May 21 17:50:11 2008 Subject: bin/75632: gvinum(8) commands not consistent with vinum doc Message-ID: <200805211750.m4LHo8Do059340@freefall.freebsd.org> Synopsis: gvinum(8) commands not consistent with vinum doc State-Changed-From-To: open->analyzed State-Changed-By: lulf State-Changed-When: Wed May 21 17:49:15 UTC 2008 State-Changed-Why: - Looking into it. http://www.freebsd.org/cgi/query-pr.cgi?pr=75632 From lulf at FreeBSD.org Wed May 21 17:52:13 2008 From: lulf at FreeBSD.org (lulf@FreeBSD.org) Date: Wed May 21 17:52:14 2008 Subject: kern/89660: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done Message-ID: <200805211752.m4LHqCeF059393@freefall.freebsd.org> Synopsis: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done State-Changed-From-To: open->analyzed State-Changed-By: lulf State-Changed-When: Wed May 21 17:51:56 UTC 2008 State-Changed-Why: - Looking into it. http://www.freebsd.org/cgi/query-pr.cgi?pr=89660 From lulf at stud.ntnu.no Wed May 21 17:54:12 2008 From: lulf at stud.ntnu.no (Ulf Lilleengen) Date: Wed May 21 17:54:14 2008 Subject: kern/79035: [vinum] gvinum unable to create a striped set of mirrored sets/plexes In-Reply-To: <200805192001.m4JK1IQU061519@freefall.freebsd.org> References: <200805192001.m4JK1IQU061519@freefall.freebsd.org> Message-ID: <20080521175416.GA70240@nobby.studby.ntnu.no> On man, mai 19, 2008 at 08:01:18pm +0000, linimon@FreeBSD.org wrote: > Synopsis: [vinum] gvinum unable to create a striped set of mirrored sets/plexes > > Responsible-Changed-From-To: le->freebsd-geom > Responsible-Changed-By: linimon > Responsible-Changed-When: Mon May 19 20:01:03 UTC 2008 > Responsible-Changed-Why: > With bugmeister hat on, reassign as le@ has not been active in a while. > > This "bug" is sort of fixed in the SoC-work I did. Hope to resolve this as soon as possible. -- Ulf Lilleengen From dfilter at FreeBSD.ORG Thu May 22 10:30:08 2008 From: dfilter at FreeBSD.ORG (dfilter service) Date: Thu May 22 10:30:13 2008 Subject: bin/75632: commit references a PR Message-ID: <200805221030.m4MAU7JW075801@freefall.freebsd.org> The following reply was made to PR bin/75632; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/75632: commit references a PR Date: Thu, 22 May 2008 10:27:10 +0000 (UTC) lulf 2008-05-22 10:27:03 UTC FreeBSD src repository Modified files: sys/geom/vinum geom_vinum_share.c Log: - Recognize the 'volume' parameter when creating a plex. PR: kern/75632 Approved by: pjd (mentor) MFC after: 1 day Revision Changes Path 1.6 +2 -1 src/sys/geom/vinum/geom_vinum_share.c _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From marauder at pi.avalonnetworks.us Thu May 22 19:46:03 2008 From: marauder at pi.avalonnetworks.us (Marauder) Date: Thu May 22 19:46:07 2008 Subject: Unable to write to drive Message-ID: <48357420.5689.0089.0@pi.avalonnetworks.us> Hi all, I have a problem that is driving me crazy. Hopefully I'm submitting this question to the correct place. My problem is... I have opened the drive /dev/ad0 with open("/dev/ad0", O_WRONLY) and it return's a valid file descriptor. The I attempt to write using the file descriptor returned. The write fails with errno=22 (EINVAL) I have attempted to first open /dev/io with READ/WRITE access to see if that help's. No luck I have attempted to lock the section of the drive I would like to write to with lockf. No luck If anybody has any idea's or suggestions I would greatly appreciate them. Thanx From sbruno at miralink.com Thu May 22 20:09:11 2008 From: sbruno at miralink.com (Sean Bruno) Date: Thu May 22 20:09:14 2008 Subject: Unable to write to drive In-Reply-To: <48357420.5689.0089.0@pi.avalonnetworks.us> References: <48357420.5689.0089.0@pi.avalonnetworks.us> Message-ID: <4835CED9.8090901@miralink.com> Marauder wrote: > Hi all, > > I have a problem that is driving me crazy. Hopefully I'm submitting this question to the correct place. > > My problem is... I have opened the drive /dev/ad0 with open("/dev/ad0", O_WRONLY) and it return's a valid file descriptor. The I attempt to write using the file descriptor returned. The write fails with errno=22 (EINVAL) > > I have attempted to first open /dev/io with READ/WRITE access to see if that help's. No luck > I have attempted to lock the section of the drive I would like to write to with lockf. No luck > > If anybody has any idea's or suggestions I would greatly appreciate them. > > Thanx > > > _______________________________________________ > 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" > Is the disk /dev/ad0 in any kind of geom based device? That would keep you from writing I think. Also, have you tried "O_RDWR" as well? -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 From lulf at FreeBSD.org Fri May 23 15:47:36 2008 From: lulf at FreeBSD.org (lulf@FreeBSD.org) Date: Fri May 23 15:47:43 2008 Subject: bin/75632: gvinum(8) commands not consistent with vinum doc Message-ID: <200805231547.m4NFlaxd050423@freefall.freebsd.org> Synopsis: gvinum(8) commands not consistent with vinum doc State-Changed-From-To: analyzed->closed State-Changed-By: lulf State-Changed-When: Fri May 23 15:47:19 UTC 2008 State-Changed-Why: - A fix have been committed and MFCed. http://www.freebsd.org/cgi/query-pr.cgi?pr=75632 From linimon at FreeBSD.org Sat May 24 19:53:47 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sat May 24 19:53:55 2008 Subject: bin/123962: [panic] gjournal(8): gjournal (455Gb data, 8Gb journal), options INVARIANTS, files written via samba3, remove = panic ffs_truncate3 Message-ID: <200805241953.m4OJrkFi026834@freefall.freebsd.org> Old Synopsis: gjournal (455Gb data, 8Gb journal), options INVARIANTS, files written via samba3, remove = panic ffs_truncate3 New Synopsis: [panic] gjournal(8): gjournal (455Gb data, 8Gb journal), options INVARIANTS, files written via samba3, remove = panic ffs_truncate3 Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Sat May 24 19:52:49 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=123962 From bugmaster at FreeBSD.org Mon May 26 11:06:48 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 26 11:07:08 2008 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200805261106.m4QB6ldN064887@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/73177 geom kldload geom_* causes panic due to memory exhaustion o kern/76538 geom [gbde] nfs-write on gbde partition stalls and continue o kern/83464 geom [geom] [patch] Unhandled malloc failures within libgeo o kern/84556 geom [geom] GBDE-encrypted swap causes panic at shutdown o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/89546 geom [geom] GEOM error a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/113419 geom [geom] geom fox multipathing not failing back o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/115572 geom [gbde] [patch] gbde partitions fail at 28bit/48bit LBA o kern/120021 geom net-p2p/qbittorrent crashes system when it works thoug o kern/120231 geom [geom] GEOM_CONCAT error adding second drive o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/122067 geom [panic]: Geom crashed during boot f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/123122 geom GEOM / gjournal kernel lock o kern/123962 geom [panic] gjournal(8): gjournal (455Gb data, 8Gb journal 22 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/78131 geom gbde(8) "destroy" not working. o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/121559 geom [patch] [geom] geom label class allows to create inacc f kern/121907 geom [request] [geom] geom output to console obscures other o kern/123630 geom [patch] [gmirror] gmirror doesnt allow the original dr 15 problems total. From rick-freebsd at kiwi-computer.com Tue May 27 04:23:33 2008 From: rick-freebsd at kiwi-computer.com (Rick C. Petty) Date: Tue May 27 04:23:39 2008 Subject: Unable to write to drive In-Reply-To: <48357420.5689.0089.0@pi.avalonnetworks.us> References: <48357420.5689.0089.0@pi.avalonnetworks.us> Message-ID: <20080527035650.GA68298@keira.kiwi-computer.com> On Thu, May 22, 2008 at 01:24:49PM -0600, Marauder wrote: > > I have a problem that is driving me crazy. Hopefully I'm submitting this question to the correct place. > > My problem is... I have opened the drive /dev/ad0 with open("/dev/ad0", O_WRONLY) and it return's a valid file descriptor. The I attempt to write using the file descriptor returned. The write fails with errno=22 (EINVAL) What does your write instruction look like? I don't know if this still applies, but writes used to fail if not an integer multiple of 512 bytes in length. > I have attempted to first open /dev/io with READ/WRITE access to see if that help's. No luck I believe the io(4) device is used to directly access the I/O ports via the assembly instructions IN, INS, OUT, OUTS, CLI, and STI. This device is not used to gain privs on other devices. -- Rick C. Petty From marauder at pi.avalonnetworks.us Tue May 27 16:58:26 2008 From: marauder at pi.avalonnetworks.us (Marauder) Date: Tue May 27 16:58:28 2008 Subject: Unable to write to drive In-Reply-To: <20080527035650.GA68298@keira.kiwi-computer.com> References: <48357420.5689.0089.0@pi.avalonnetworks.us> <20080527035650.GA68298@keira.kiwi-computer.com> Message-ID: <483BE93B.5689.0089.0@pi.avalonnetworks.us> Actually I managed to fix this problem on Friday with the help of Sean Bruno. The problem was the one you described bellow that Read's and writes must be multiple's of 512. Thank you everybody for your help Binon >>> "Rick C. Petty" 5/26/2008 9:56 PM >>> On Thu, May 22, 2008 at 01:24:49PM -0600, Marauder wrote: > > I have a problem that is driving me crazy. Hopefully I'm submitting this question to the correct place. > > My problem is... I have opened the drive /dev/ad0 with open("/dev/ad0", O_WRONLY) and it return's a valid file descriptor. The I attempt to write using the file descriptor returned. The write fails with errno=22 (EINVAL) What does your write instruction look like? I don't know if this still applies, but writes used to fail if not an integer multiple of 512 bytes in length. > I have attempted to first open /dev/io with READ/WRITE access to see if that help's. No luck I believe the io(4) device is used to directly access the I/O ports via the assembly instructions IN, INS, OUT, OUTS, CLI, and STI. This device is not used to gain privs on other devices. -- Rick C. Petty _______________________________________________ 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 remko at FreeBSD.org Fri May 30 15:06:59 2008 From: remko at FreeBSD.org (remko@FreeBSD.org) Date: Fri May 30 15:07:03 2008 Subject: kern/124130: [gmirror][usb] gmirror fails to start usb devices that were present at boot time Message-ID: <200805301506.m4UF6wmT062516@freefall.freebsd.org> Synopsis: [gmirror][usb] gmirror fails to start usb devices that were present at boot time State-Changed-From-To: feedback->open State-Changed-By: remko State-Changed-When: Fri May 30 15:06:14 UTC 2008 State-Changed-Why: Return this to the open state, the ticket gets forwarded to -geom because this is a boot-time issue, the modules are loaded but not detected, unless the user unplugs the hardware and replugs it. http://www.freebsd.org/cgi/query-pr.cgi?pr=124130 From kena at vodka-pomme.net Fri May 30 15:20:03 2008 From: kena at vodka-pomme.net (Kena) Date: Fri May 30 15:20:14 2008 Subject: misc/124130: [gmirror][usb] gmirror fails to start usb devices that were present at boot time Message-ID: <200805301520.m4UFK3kv064287@freefall.freebsd.org> The following reply was made to PR kern/124130; it has been noted by GNATS. From: Kena To: Remko Lodder Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/124130: [gmirror][usb] gmirror fails to start usb devices that were present at boot time Date: Fri, 30 May 2008 16:56:52 +0200 Op 30 mei 2008, om 16:34 heeft Remko Lodder het volgende geschreven: > 1) the severity is not important, I understand it is frustrating to > detach/attach the devices though. It's not only frustrating; it borders on "impossible" without physical access to the system. (unless I'm missing something and it is actually possible to unload/ reload drives using tools and the usb stack -- which I don't know how to do) > 2) Just to be sure you have a gmirror_load="YES" in /boot/ > loader.conf ? Both are set: geom_mirror_load="YES" geom_journal_load="YES" anything else to help? -- k From remko at FreeBSD.org Fri May 30 15:30:21 2008 From: remko at FreeBSD.org (Remko Lodder) Date: Fri May 30 15:30:24 2008 Subject: misc/124130: [gmirror][usb] gmirror fails to start usb devices that were present at boot time Message-ID: <200805301530.m4UFUL8V065760@freefall.freebsd.org> The following reply was made to PR kern/124130; it has been noted by GNATS. From: Remko Lodder To: Kena Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/124130: [gmirror][usb] gmirror fails to start usb devices that were present at boot time Date: Fri, 30 May 2008 16:34:26 +0200 2 notes: 1) the severity is not important, I understand it is frustrating to detach/attach the devices though. 2) Just to be sure you have a gmirror_load="YES" in /boot/loader.conf ? -- /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News