From owner-freebsd-geom@FreeBSD.ORG Thu Oct 14 05:21:02 2004 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4814616A4CE; Thu, 14 Oct 2004 05:21:02 +0000 (GMT) Received: from mrynet.com (mrynet.com [63.231.249.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBA5A43D39; Thu, 14 Oct 2004 05:21:01 +0000 (GMT) (envelope-from staylor@mrynet.com) Received: from mrynet.com (staylor@localhost [127.0.0.1]) by mrynet.com (8.13.1/8.13.1) with ESMTP id i9E5L0JJ001097; Thu, 14 Oct 2004 00:21:01 -0500 (CDT) (envelope-from staylor@mrynet.com) Received: (from staylor@localhost) by mrynet.com (8.13.1/8.13.1/Submit) id i9E5L06d001096; Thu, 14 Oct 2004 00:21:00 -0500 (CDT) (envelope-from staylor) Message-Id: <200410140521.i9E5L06d001096@mrynet.com> From: staylor@mrynet.com (User Staylor) Date: Thu, 14 Oct 2004 00:21:00 -0500 X-Mailer: Mail User's Shell (7.2.6 beta(5) jp(8) 11/23/00) To: freebsd-current@freebsd.org, freebsd-geom@freebsd.org Subject: GEOM will panic 6.0-current on userland wrong-length disk reads X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2004 05:21:02 -0000 Just discovered (and verified with latest build on current.freebsd.org) that the following will panic the new GEOM fdc driver in 6.0-current: # dd if=/dev/fd0 bs=55 panic: wrong length 55 for sectorsize 512 And further checking, discovered that ALL disk devices will cause a panic: dd if=/dev/ad0 bs=1234 panic: wrong length 1234 for sectorsize 512 Perhaps this is geom's way of complaining? Seems a rather radical way to handle non-matching-blocksize reads of disk devices. A simple programming error reading a disk dev node will panic the machine. -scott From owner-freebsd-geom@FreeBSD.ORG Thu Oct 14 07:21:02 2004 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DE3116A4CE; Thu, 14 Oct 2004 07:21:02 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2F9743D53; Thu, 14 Oct 2004 07:21:01 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i9E7L0x3059230; Thu, 14 Oct 2004 09:21:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: staylor@mrynet.com (User Staylor) From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 14 Oct 2004 00:21:00 CDT." <200410140521.i9E5L06d001096@mrynet.com> Date: Thu, 14 Oct 2004 09:21:00 +0200 Message-ID: <59229.1097738460@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org cc: freebsd-geom@freebsd.org Subject: Re: GEOM will panic 6.0-current on userland wrong-length disk reads X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2004 07:21:02 -0000 Do you have rev. 1.63 of sys/geom/geom_io.c ? In message <200410140521.i9E5L06d001096@mrynet.com>, User Staylor writes: >Just discovered (and verified with latest build on >current.freebsd.org) that the following will panic >the new GEOM fdc driver in 6.0-current: > ># dd if=/dev/fd0 bs=55 >panic: wrong length 55 for sectorsize 512 > >And further checking, discovered that ALL disk devices will cause >a panic: > >dd if=/dev/ad0 bs=1234 >panic: wrong length 1234 for sectorsize 512 > >Perhaps this is geom's way of complaining? Seems a rather radical >way to handle non-matching-blocksize reads of disk devices. A >simple programming error reading a disk dev node will panic the >machine. > >-scott >_______________________________________________ >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" > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-geom@FreeBSD.ORG Thu Oct 14 09:05:33 2004 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9162116A4CE for ; Thu, 14 Oct 2004 09:05:33 +0000 (GMT) Received: from tierra2.ng.fadesa.es (tierra2.ng.fadesa.es [195.55.55.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3EEF43D2F for ; Thu, 14 Oct 2004 09:05:31 +0000 (GMT) (envelope-from fandino@ng.fadesa.es) Received: from [195.55.55.163] ([195.55.55.163]) (authenticated bits=0) by tierra2.ng.fadesa.es (8.12.10/8.12.10) with ESMTP id i9E95Pi3007379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Oct 2004 11:05:28 +0200 Message-ID: <416E4155.2080302@ng.fadesa.es> Date: Thu, 14 Oct 2004 11:05:25 +0200 From: fandino User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: gl, en, es MIME-Version: 1.0 To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: user fandino from 195.55.55.163 X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on tierra2 X-Virus-Status: Clean Subject: geom mirror -- bad read performance with BETA7 [long] X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: fandino@ng.fadesa.es List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2004 09:05:33 -0000 Hello, I'm in the process of testing gmirror and during tests I get a very poor read performance (about the 50%) and perhaps I'm missing something but my idea of raid1 read performace is near to a single disk throughput (or a bit better). first of all, I did tests over individual disks and they perform as expected: -- disk description -- # bsdlabel ad0s4 # /dev/ad0s4: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 64709820 0 unused 0 0 # "raw" part, don't edit d: 6291456 0 4.2BSD 0 0 0 # bsdlabel ad0s2s4 # /dev/ad2s4: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 64709820 0 unused 0 0 # "raw" part, don't edit d: 6291456 0 4.2BSD 0 0 0 -- format -- # newsfs -O2 -U ad0s4d /dev/ad0s4d: 3072.0MB (6291456 sectors) block size 16384, fragment size 2048 using 17 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. with soft updates super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, 3387328, 3763680, 4140032, 4516384, 4892736, 5269088, 5645440, 6021792 # newfs -O2 -U ad2s4d /dev/ad2s4d: 3072.0MB (6291456 sectors) block size 16384, fragment size 2048 using 17 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. with soft updates super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, 3387328, 3763680, 4140032, 4516384, 4892736, 5269088, 5645440, 6021792 -- mount and create a gigabyte file -- # mkdir /mnt1 /mnt2 # mount /dev/ad0s4d /mnt1 # mount /dev/ad2s4d /mnt2 # cd /mnt1/ # dd if=/dev/zero of=aa bs=1024k count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 39.285669 secs (27331642 bytes/sec) # cd /mnt2 # if=/dev/zero of=aa bs=1024k count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 39.295175 secs (27325030 bytes/sec) -- now read the newly created files -- # dd if=aa of=/dev/null bs=1024k 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 36.291125 secs (29586898 bytes/sec) # cd ../mnt2 # dd if=aa of=/dev/null bs=1024k 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 38.807037 secs (27668740 bytes/sec) -- ok it was good, now let me try to repeat all tests over a geom mirror -- # geom mirror label -v -b split -s 2048 probe /dev/ad0s4d /dev/ad2s4d Metadata value stored on /dev/ad0s4d. Metadata value stored on /dev/ad2s4d. Done. # gmirror list Geom name: probe State: COMPLETE Components: 2 Balance: split Slice: 2048 Flags: NONE SyncID: 1 ID: 3225011317 Providers: 1. Name: mirror/probe Mediasize: 3221224960 (3.0G) Sectorsize: 512 Mode: r0w0e0 Consumers: 1. Name: ad2s4d Mediasize: 3221225472 (3.0G) Sectorsize: 512 Mode: r0w0e0 State: ACTIVE Priority: 1 Flags: NONE SyncID: 1 ID: 1631357908 2. Name: ad0s4d Mediasize: 3221225472 (3.0G) Sectorsize: 512 Mode: r0w0e0 State: ACTIVE Priority: 0 Flags: NONE SyncID: 1 ID: 3998309608 Geom name: probe.sync -- format -- # newfs -O2 -U /dev/mirror/probe /dev/mirror/probe: 3072.0MB (6291452 sectors) block size 16384, fragment size 2048 using 17 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. with soft updates super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, 3387328, 3763680, 4140032, 4516384, 4892736, 5269088, 5645440, 6021792 # mount /dev/mirror/probe /mnt -- write and read a gigabyte file -- # dd if=/dev/zero of=aa bs=1024k count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 47.281526 secs (22709542 bytes/sec) # # # dd if=aa of=/dev/null bs=1024k 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 100.970277 secs (10634237 bytes/sec) -- opps!!!!! 10MB/second is very poor throughput. Any idea about this? I think there is something wrong. Thank you. # dmesg Copyright (c) 1992-2004 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 5.3-BETA7 #0: Sat Oct 2 21:01:00 UTC 2004 root@wv1u.samsco.home:/usr/obj/usr/src/sys/GENERIC module_register: module uhub/umass already exists! Module uhub/umass failed to register: 17 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(TM) XP 1600+ (1399.61-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383f9ff AMD Features=0xc0400000 real memory = 805224448 (767 MB) avail memory = 778170368 (742 MB) bktr_mem: memory holder loaded npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe6000000-0xe7ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: port 0xd800-0xd8ff mem 0xdc800000-0xdc803fff,0xe0000000-0xe3ffffff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe6000000 32MB info: [drm] Initialized r128 2.5.0 20030725 on minor 0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0xb400-0xb41f irq 9 at device 4.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb000-0xb01f irq 9 at device 4.3 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 4.4 (no driver attached) pcm0: port 0xa000-0xa003,0xa400-0xa403,0xa800-0xa8ff irq 5 at device 4.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: pci0: at device 10.0 (no driver attached) bktr0: mem 0xde000000-0xde000fff irq 10 at device 11.0 on pci0 bktr0: [GIANT-LOCKED] bktr0: Card has no configuration EEPROM. Cannot determine card make. bktr0: Pinnacle/Miro TV, Temic NTSC tuner. pci0: at device 11.1 (no driver attached) ed0: port 0x9400-0x941f irq 9 at device 13.0 on pci0 ed0: [GIANT-LOCKED] ed0: Ethernet address: 00:02:44:17:3a:fa ed0: if_start running deferred for Giant type NE2000 (16 bit) atapci1: port 0x7800-0x783f,0x8000-0x8003,0x8400-0x8407,0x8800-0x8803,0x9000-0x9007 mem 0xdb800000-0xdb81ffff irq 10 at device 17.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 orm0: at iomem 0xc0000-0xcbfff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1399614623 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0% ad0: 38166MB [77545/16/63] at ata0-master UDMA100 acd0: DVDR at ata0-slave UDMA33 ad2: 38166MB [77545/16/63] at ata1-master UDMA100 acd1: DVDROM at ata1-slave UDMA33 Mounting root from ufs:/dev/ad0s2a GEOM_MIRROR: Device probe created (id=3225011317). GEOM_MIRROR: Device probe: provider ad0s4d detected. GEOM_MIRROR: Device probe: provider ad2s4d detected. GEOM_MIRROR: Device probe: provider ad2s4d activated. GEOM_MIRROR: Device probe: provider ad0s4d activated. GEOM_MIRROR: Device probe: provider mirror/probe launched. WARNING: Expected rawoffset 0, found 13446405 WARNING: Expected rawoffset 0, found 13446405 WARNING: Expected rawoffset 0, found 13446405 GEOM_MIRROR: Device probe: provider mirror/probe destroyed. GEOM_MIRROR: Device probe destroyed. GEOM_MIRROR: Device probe created (id=3225011317). GEOM_MIRROR: Device probe: provider ad2s4d detected. GEOM_MIRROR: Device probe: provider ad0s4d detected. GEOM_MIRROR: Device probe: provider ad2s4d activated. GEOM_MIRROR: Device probe: provider ad0s4d activated. GEOM_MIRROR: Device probe: provider mirror/probe launched. WARNING: Expected rawoffset 0, found 13446405 WARNING: Expected rawoffset 0, found 13446405 WARNING: Expected rawoffset 0, found 13446405 GEOM_MIRROR: Cannot add disk mirror/probed to probe (error=17). WARNING: Expected rawoffset 0, found 13446405 WARNING: Expected rawoffset 0, found 13446405 From owner-freebsd-geom@FreeBSD.ORG Thu Oct 14 13:41:25 2004 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE4D916A4CE; Thu, 14 Oct 2004 13:41:25 +0000 (GMT) Received: from mrynet.com (mrynet.com [63.231.249.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43A5143D4C; Thu, 14 Oct 2004 13:41:25 +0000 (GMT) (envelope-from staylor@mrynet.com) Received: from mrynet.com (staylor@localhost [127.0.0.1]) by mrynet.com (8.13.1/8.13.1) with ESMTP id i9EDfOal006487; Thu, 14 Oct 2004 08:41:24 -0500 (CDT) (envelope-from staylor@mrynet.com) Received: (from staylor@localhost) by mrynet.com (8.13.1/8.13.1/Submit) id i9EDfOhU006486; Thu, 14 Oct 2004 08:41:24 -0500 (CDT) (envelope-from staylor) Message-Id: <200410141341.i9EDfOhU006486@mrynet.com> From: staylor@mrynet.com (User Staylor) Date: Thu, 14 Oct 2004 08:41:24 -0500 X-Mailer: Mail User's Shell (7.2.6 beta(5) jp(8) 11/23/00) To: "Poul-Henning Kamp" cc: freebsd-current@freebsd.org cc: freebsd-geom@freebsd.org Subject: Re: GEOM will panic 6.0-current on userland wrong-length disk reads X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2004 13:41:26 -0000 > Do you have rev. 1.63 of sys/geom/geom_io.c ? Yes: ttyp6:--ROOT--@mrynet (74): ident kernel | grep geom_io $FreeBSD: /repoman/r/ncvs/src/sys/geom/geom_io.c,v 1.63 2004/10/11 21:22:59 ups Exp $ And I've found that simply commenting-out the following resolves the issue: ttyp6:--ROOT--@mrynet (58): diff -C 10 geom_io.c- geom_io.c *** geom_io.c- Thu Oct 14 08:30:44 2004 --- geom_io.c Thu Oct 14 08:31:12 2004 *************** *** 238,265 **** --- 238,267 ---- g_io_request(struct bio *bp, struct g_consumer *cp) { struct g_provider *pp; KASSERT(cp != NULL, ("NULL cp in g_io_request")); KASSERT(bp != NULL, ("NULL bp in g_io_request")); KASSERT(bp->bio_data != NULL, ("NULL bp->data in g_io_request")); pp = cp->provider; KASSERT(pp != NULL, ("consumer not attached in g_io_request")); + #ifdef notyet if (bp->bio_cmd & (BIO_READ|BIO_WRITE|BIO_DELETE)) { KASSERT(bp->bio_offset % cp->provider->sectorsize == 0, ("wrong offset %jd for sectorsize %u", bp->bio_offset, cp->provider->sectorsize)); KASSERT(bp->bio_length % cp->provider->sectorsize == 0, ("wrong length %jd for sectorsize %u", bp->bio_length, cp->provider->sectorsize)); } + #endif g_trace(G_T_BIO, "bio_request(%p) from %p(%s) to %p(%s) cmd %d", bp, cp, cp->geom->name, pp, pp->name, bp->bio_cmd); bp->bio_from = cp; bp->bio_to = pp; bp->bio_error = 0; bp->bio_completed = 0; KASSERT(!(bp->bio_flags & BIO_ONQUEUE), If you're indicating that you are unable to duplicate this panic, let me know. I'll resort to pitching my current /usr/src tree and re-cvsup and retry. -scott > > In message <200410140521.i9E5L06d001096@mrynet.com>, User Staylor writes: > >Just discovered (and verified with latest build on > >current.freebsd.org) that the following will panic > >the new GEOM fdc driver in 6.0-current: > > > ># dd if=/dev/fd0 bs=55 > >panic: wrong length 55 for sectorsize 512 > > > >And further checking, discovered that ALL disk devices will cause > >a panic: > > > >dd if=/dev/ad0 bs=1234 > >panic: wrong length 1234 for sectorsize 512 > > > >Perhaps this is geom's way of complaining? Seems a rather radical > >way to handle non-matching-blocksize reads of disk devices. A > >simple programming error reading a disk dev node will panic the > >machine. > > > >-scott > >_______________________________________________ > >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" > > > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-geom@FreeBSD.ORG Thu Oct 14 13:44:09 2004 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1608C16A4CF; Thu, 14 Oct 2004 13:44:09 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id A295843D3F; Thu, 14 Oct 2004 13:44:08 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id A2254ACAF1; Thu, 14 Oct 2004 15:44:06 +0200 (CEST) Date: Thu, 14 Oct 2004 15:44:06 +0200 From: Pawel Jakub Dawidek To: User Staylor Message-ID: <20041014134406.GM73767@darkness.comp.waw.pl> References: <200410141341.i9EDfOhU006486@mrynet.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ivwvlL43CqGAdkOw" Content-Disposition: inline In-Reply-To: <200410141341.i9EDfOhU006486@mrynet.com> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org cc: freebsd-geom@freebsd.org Subject: Re: GEOM will panic 6.0-current on userland wrong-length disk reads X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2004 13:44:09 -0000 --ivwvlL43CqGAdkOw Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 14, 2004 at 08:41:24AM -0500, User Staylor wrote: +> > Do you have rev. 1.63 of sys/geom/geom_io.c ? +>=20 +> Yes: +> ttyp6:--ROOT--@mrynet (74): ident kernel | grep geom_io +> $FreeBSD: /repoman/r/ncvs/src/sys/geom/geom_io.c,v 1.63 2004/10/11 = 21:22:59 ups Exp $ Which revision of geom_dev.c do you have? 1.81 should be safe. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --ivwvlL43CqGAdkOw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBboKmForvXbEpPzQRAhJoAJ9fO8hdirJYi4vIYqnpPGDrwwlbUwCgq1+W 7Qw/QI/5IWvI8YXabwT3Bt8= =ZA9h -----END PGP SIGNATURE----- --ivwvlL43CqGAdkOw--