From ghostsblood at gmail.com Fri May 1 08:20:10 2009 From: ghostsblood at gmail.com (ghostcorps) Date: Fri May 1 08:20:22 2009 Subject: How do I add a new HDD to encrypted RAID5 array? Message-ID: <23329663.post@talk.nabble.com> Hi Guys, This seems liek a really basic question, I expect a simple 'no', but I havn't found anything definative yet. I currently have a hardware RAID5 array (onboard using Intel Matrix) encrypted with GELI, but I need to add 2 new discs to the array. If I add a disc to the array and have it rebuilt with the Intel Matrix Storage Manager, prior to booting FreeBSD will that destroy the encrypted data? If so, how can I decrypt the disk without copying the data to another partition? Using: OS: FreeBSD 7.0 Mobo: Asus p5b-e http://www.asus.com.au/products.aspx?l1=3&l2=11&l3=307&l4=0&model=1347&modelmenu=1 HDDs: Seagate 500g SATA2 Please let me know if you need any other info. Thanks =^_^= -- View this message in context: http://www.nabble.com/How-do-I-add-a-new-HDD-to-encrypted-RAID5-array--tp23329663p23329663.html Sent from the freebsd-geom mailing list archive at Nabble.com. From ghostsblood at gmail.com Fri May 1 08:20:10 2009 From: ghostsblood at gmail.com (ghostcorps) Date: Fri May 1 08:20:22 2009 Subject: Rebuild encrypted RAID5? Message-ID: <23329555.post@talk.nabble.com> -- View this message in context: http://www.nabble.com/Rebuild-encrypted-RAID5--tp23329555p23329555.html Sent from the freebsd-geom mailing list archive at Nabble.com. From fb-geom at psconsult.nl Sat May 2 16:31:09 2009 From: fb-geom at psconsult.nl (Paul Schenkeveld) Date: Sat May 2 16:31:16 2009 Subject: Multiple FreeBSD instances with gpt Message-ID: <20090502161442.GA42972@psconsult.nl> Hello, Is there a GPT equivalent for boot0 which allows for multiple instances of FreeBSD to co-reside on a single harddisk with GPT as the primary partitioning scheme and that provides a boot menu similar to boot0? I could try to use grub here but I'm not a big fan of grub. Regards, Paul Schenkeveld From linimon at FreeBSD.org Sat May 2 21:49:03 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sat May 2 21:49:10 2009 Subject: kern/134113: [geli] Problem setting secondary GELI key Message-ID: <200905022149.n42Ln2CC035481@freefall.freebsd.org> Old Synopsis: Problem setting secondary GELI key New Synopsis: [geli] Problem setting secondary GELI key Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Sat May 2 21:48:39 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=134113 From linimon at FreeBSD.org Sat May 2 22:01:47 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sat May 2 22:01:53 2009 Subject: kern/134044: [geom] gmirror(8) overwrites fs with stale data from returning member Message-ID: <200905022201.n42M1j5Z061561@freefall.freebsd.org> Old Synopsis: Gmirror overwrites fs with stale data from returning member New Synopsis: [geom] gmirror(8) overwrites fs with stale data from returning member Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Sat May 2 22:01:05 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=134044 From bugmaster at FreeBSD.org Mon May 4 11:07:51 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 4 11:08:43 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200905041107.n44B7niJ098556@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/134113 geom [geli] Problem setting secondary GELI key o kern/134044 geom [geom] gmirror(8) overwrites fs with stale data from r o kern/133931 geom [geli] [request] intentionally wrong password to destr o kern/133604 geom [gvinum] [panic] writing to gjournal on a gvinum volum o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o kern/132273 geom glabel(8): [patch] failing on journaled partition o kern/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131353 geom [geom] gjournal(8) kernel lock o kern/131037 geom [geli] Unable to create disklabel on .eli-Device o kern/130528 geom gjournal fsck during boot o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid o bin/128398 geom [patch] glabel(8): teach geom_label to recognise gpt l f kern/128276 geom [gmirror] machine lock up when gmirror module is used o kern/126902 geom [geom] geom_label: kernel panic during install boot o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s o kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/124130 geom [gmirror] [usb] gmirror fails to start usb devices tha o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123630 geom [patch] [gmirror] gmirror doesnt allow the original dr o kern/123122 geom [geom] GEOM / gjournal kernel lock f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120231 geom [geom] GEOM_CONCAT error adding second drive o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/120021 geom [geom] [panic] net-p2p/qbittorrent crashes system when o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o kern/89546 geom [geom] GEOM error s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. s kern/73177 geom kldload geom_* causes panic due to memory exhaustion 52 problems total. From dfilter at FreeBSD.ORG Wed May 6 19:40:02 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Wed May 6 19:40:10 2009 Subject: kern/133604: commit references a PR Message-ID: <200905061940.n46Je2h7047170@freefall.freebsd.org> The following reply was made to PR kern/133604; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/133604: commit references a PR Date: Wed, 6 May 2009 19:34:42 +0000 (UTC) Author: lulf Date: Wed May 6 19:34:32 2009 New Revision: 191856 URL: http://svn.freebsd.org/changeset/base/191856 Log: - Split up the BIO queue into a queue for new and one for completed requests. This is necessary for two reasons: 1) In order to avoid collisions with the use of a BIOs flags set by a consumer or a provider 2) Because GV_BIO_DONE was used to mark a BIO as done, not enough flags was available, so the consumer flags of a BIO had to be misused in order to support enough flags. The new queue makes it possible to recycle the GV_BIO_DONE flag into GV_BIO_GROW. As a consequence, gvinum will now work with any other GEOM class under it or on top of it. - Use bio_pflags for storing internal flags on downgoing BIOs, as the requests appear to come from a consumer of a gvinum volume. Use bio_cflags only for cloned BIOs. - Move gv_post_bio to be used internally for maintenance requests. - Remove some cases where flags where set without need. PR: kern/133604 Modified: head/sys/geom/vinum/geom_vinum.c head/sys/geom/vinum/geom_vinum.h head/sys/geom/vinum/geom_vinum_plex.c head/sys/geom/vinum/geom_vinum_raid5.c head/sys/geom/vinum/geom_vinum_var.h Modified: head/sys/geom/vinum/geom_vinum.c ============================================================================== --- head/sys/geom/vinum/geom_vinum.c Wed May 6 19:18:19 2009 (r191855) +++ head/sys/geom/vinum/geom_vinum.c Wed May 6 19:34:32 2009 (r191856) @@ -81,18 +81,6 @@ gv_orphan(struct g_consumer *cp) } void -gv_post_bio(struct gv_softc *sc, struct bio *bp) -{ - - KASSERT(sc != NULL, ("NULL sc")); - KASSERT(bp != NULL, ("NULL bp")); - mtx_lock(&sc->bqueue_mtx); - bioq_disksort(sc->bqueue, bp); - wakeup(sc); - mtx_unlock(&sc->bqueue_mtx); -} - -void gv_start(struct bio *bp) { struct g_geom *gp; @@ -111,8 +99,10 @@ gv_start(struct bio *bp) g_io_deliver(bp, EOPNOTSUPP); return; } - - gv_post_bio(sc, bp); + mtx_lock(&sc->bqueue_mtx); + bioq_disksort(sc->bqueue_down, bp); + wakeup(sc); + mtx_unlock(&sc->bqueue_mtx); } void @@ -125,9 +115,11 @@ gv_done(struct bio *bp) gp = bp->bio_from->geom; sc = gp->softc; - bp->bio_cflags |= GV_BIO_DONE; - gv_post_bio(sc, bp); + mtx_lock(&sc->bqueue_mtx); + bioq_disksort(sc->bqueue_up, bp); + wakeup(sc); + mtx_unlock(&sc->bqueue_mtx); } int @@ -179,8 +171,12 @@ gv_init(struct g_class *mp) gp->softc = g_malloc(sizeof(struct gv_softc), M_WAITOK | M_ZERO); sc = gp->softc; sc->geom = gp; - sc->bqueue = g_malloc(sizeof(struct bio_queue_head), M_WAITOK | M_ZERO); - bioq_init(sc->bqueue); + sc->bqueue_down = g_malloc(sizeof(struct bio_queue_head), + M_WAITOK | M_ZERO); + sc->bqueue_up = g_malloc(sizeof(struct bio_queue_head), + M_WAITOK | M_ZERO); + bioq_init(sc->bqueue_down); + bioq_init(sc->bqueue_up); LIST_INIT(&sc->drives); LIST_INIT(&sc->subdisks); LIST_INIT(&sc->plexes); @@ -969,7 +965,8 @@ gv_worker(void *arg) gv_cleanup(sc); mtx_destroy(&sc->bqueue_mtx); mtx_destroy(&sc->equeue_mtx); - g_free(sc->bqueue); + g_free(sc->bqueue_down); + g_free(sc->bqueue_up); g_free(sc); kproc_exit(ENXIO); break; /* not reached */ @@ -984,38 +981,40 @@ gv_worker(void *arg) /* ... then do I/O processing. */ mtx_lock(&sc->bqueue_mtx); - bp = bioq_takefirst(sc->bqueue); + /* First do new requests. */ + bp = bioq_takefirst(sc->bqueue_down); + if (bp != NULL) { + mtx_unlock(&sc->bqueue_mtx); + /* A bio that interfered with another bio. */ + if (bp->bio_pflags & GV_BIO_ONHOLD) { + s = bp->bio_caller1; + p = s->plex_sc; + /* Is it still locked out? */ + if (gv_stripe_active(p, bp)) { + /* Park the bio on the waiting queue. */ + bioq_disksort(p->wqueue, bp); + } else { + bp->bio_pflags &= ~GV_BIO_ONHOLD; + g_io_request(bp, s->drive_sc->consumer); + } + /* A special request requireing special handling. */ + } else if (bp->bio_pflags & GV_BIO_INTERNAL) { + p = bp->bio_caller1; + gv_plex_start(p, bp); + } else { + gv_volume_start(sc, bp); + } + mtx_lock(&sc->bqueue_mtx); + } + /* Then do completed requests. */ + bp = bioq_takefirst(sc->bqueue_up); if (bp == NULL) { msleep(sc, &sc->bqueue_mtx, PRIBIO, "-", hz/10); mtx_unlock(&sc->bqueue_mtx); continue; } mtx_unlock(&sc->bqueue_mtx); - - /* A bio that is coming up from an underlying device. */ - if (bp->bio_cflags & GV_BIO_DONE) { - gv_bio_done(sc, bp); - /* A bio that interfered with another bio. */ - } else if (bp->bio_cflags & GV_BIO_ONHOLD) { - s = bp->bio_caller1; - p = s->plex_sc; - /* Is it still locked out? */ - if (gv_stripe_active(p, bp)) { - /* Park the bio on the waiting queue. */ - bioq_disksort(p->wqueue, bp); - } else { - bp->bio_cflags &= ~GV_BIO_ONHOLD; - g_io_request(bp, s->drive_sc->consumer); - } - /* A special request requireing special handling. */ - } else if (bp->bio_cflags & GV_BIO_INTERNAL || - bp->bio_pflags & GV_BIO_INTERNAL) { - p = bp->bio_caller1; - gv_plex_start(p, bp); - /* A fresh bio, scheduled it down. */ - } else { - gv_volume_start(sc, bp); - } + gv_bio_done(sc, bp); } } Modified: head/sys/geom/vinum/geom_vinum.h ============================================================================== --- head/sys/geom/vinum/geom_vinum.h Wed May 6 19:18:19 2009 (r191855) +++ head/sys/geom/vinum/geom_vinum.h Wed May 6 19:34:32 2009 (r191856) @@ -127,7 +127,6 @@ void gv_remove_event(struct gv_softc *, void gv_drive_tasted(struct gv_softc *, struct g_provider *); void gv_drive_lost(struct gv_softc *, struct gv_drive *); void gv_setup_objects(struct gv_softc *); -void gv_post_bio(struct gv_softc *, struct bio *); void gv_start(struct bio *); int gv_access(struct g_provider *, int, int, int); void gv_cleanup(struct gv_softc *); Modified: head/sys/geom/vinum/geom_vinum_plex.c ============================================================================== --- head/sys/geom/vinum/geom_vinum_plex.c Wed May 6 19:18:19 2009 (r191855) +++ head/sys/geom/vinum/geom_vinum_plex.c Wed May 6 19:34:32 2009 (r191856) @@ -48,6 +48,8 @@ static int gv_plex_offset(struct gv_plex int *, int); static int gv_plex_normal_request(struct gv_plex *, struct bio *, off_t, off_t, caddr_t); +static void gv_post_bio(struct gv_softc *, struct bio *); + void gv_plex_start(struct gv_plex *p, struct bio *bp) { @@ -111,7 +113,7 @@ gv_plex_start(struct gv_plex *p, struct */ if (cbp->bio_caller2 != NULL && gv_stripe_active(p, cbp)) { /* Park the bio on the waiting queue. */ - cbp->bio_cflags |= GV_BIO_ONHOLD; + cbp->bio_pflags |= GV_BIO_ONHOLD; bioq_disksort(p->wqueue, cbp); } else { s = cbp->bio_caller1; @@ -209,7 +211,7 @@ gv_plex_normal_request(struct gv_plex *p goto bad; err = gv_plex_offset(p, boff, bcount, &real_off, - &real_len, &sdno, (bp->bio_pflags & GV_BIO_SYNCREQ)); + &real_len, &sdno, (bp->bio_pflags & GV_BIO_GROW)); /* If the request was blocked, put it into wait. */ if (err == GV_ERR_ISBUSY) { bioq_disksort(p->rqueue, bp); @@ -239,12 +241,12 @@ gv_plex_normal_request(struct gv_plex *p /* If the subdisk is up, just continue. */ break; case GV_SD_DOWN: - if (bp->bio_cflags & GV_BIO_INTERNAL) + if (bp->bio_pflags & GV_BIO_INTERNAL) G_VINUM_DEBUG(0, "subdisk must be in the stale state in" " order to perform administrative requests"); goto bad; case GV_SD_STALE: - if (!(bp->bio_cflags & GV_BIO_SYNCREQ)) { + if (!(bp->bio_pflags & GV_BIO_SYNCREQ)) { G_VINUM_DEBUG(0, "subdisk stale, unable to perform " "regular requests"); goto bad; @@ -273,8 +275,6 @@ gv_plex_normal_request(struct gv_plex *p cbp->bio_data = addr; cbp->bio_done = gv_done; cbp->bio_caller1 = s; - if ((bp->bio_cflags & GV_BIO_SYNCREQ)) - cbp->bio_cflags |= GV_BIO_SYNCREQ; /* Store the sub-requests now and let others issue them. */ bioq_insert_tail(p->bqueue, cbp); @@ -282,8 +282,8 @@ gv_plex_normal_request(struct gv_plex *p bad: G_VINUM_LOGREQ(0, bp, "plex request failed."); /* Building the sub-request failed. If internal BIO, do not deliver. */ - if (bp->bio_cflags & GV_BIO_INTERNAL) { - if (bp->bio_cflags & GV_BIO_MALLOC) + if (bp->bio_pflags & GV_BIO_INTERNAL) { + if (bp->bio_pflags & GV_BIO_MALLOC) g_free(bp->bio_data); g_destroy_bio(bp); p->flags &= ~(GV_PLEX_SYNCING | GV_PLEX_REBUILDING | @@ -311,9 +311,9 @@ gv_plex_normal_done(struct gv_plex *p, s /* Just set it to length since multiple plexes will * screw things up. */ pbp->bio_completed = pbp->bio_length; - if (pbp->bio_cflags & GV_BIO_SYNCREQ) + if (pbp->bio_pflags & GV_BIO_SYNCREQ) gv_sync_complete(p, pbp); - else if (pbp->bio_pflags & GV_BIO_SYNCREQ) + else if (pbp->bio_pflags & GV_BIO_GROW) gv_grow_complete(p, pbp); else g_io_deliver(pbp, pbp->bio_error); @@ -392,7 +392,7 @@ gv_plex_raid5_done(struct gv_plex *p, st /* Handle parity data. */ if (TAILQ_EMPTY(&wp->bits)) { - if (bp->bio_parent->bio_cflags & GV_BIO_CHECK) + if (bp->bio_parent->bio_pflags & GV_BIO_CHECK) i = gv_check_parity(p, bp, wp); else i = gv_normal_parity(p, bp, wp); @@ -424,16 +424,16 @@ gv_plex_raid5_done(struct gv_plex *p, st if (pbp->bio_inbed == pbp->bio_children) { /* Hand it over for checking or delivery. */ if (pbp->bio_cmd == BIO_WRITE && - (pbp->bio_cflags & GV_BIO_CHECK)) { + (pbp->bio_pflags & GV_BIO_CHECK)) { gv_parity_complete(p, pbp); } else if (pbp->bio_cmd == BIO_WRITE && - (pbp->bio_cflags & GV_BIO_REBUILD)) { + (pbp->bio_pflags & GV_BIO_REBUILD)) { gv_rebuild_complete(p, pbp); - } else if (pbp->bio_cflags & GV_BIO_INIT) { + } else if (pbp->bio_pflags & GV_BIO_INIT) { gv_init_complete(p, pbp); - } else if (pbp->bio_cflags & GV_BIO_SYNCREQ) { - gv_sync_complete(p, pbp); } else if (pbp->bio_pflags & GV_BIO_SYNCREQ) { + gv_sync_complete(p, pbp); + } else if (pbp->bio_pflags & GV_BIO_GROW) { gv_grow_complete(p, pbp); } else { g_io_deliver(pbp, pbp->bio_error); @@ -480,7 +480,7 @@ gv_check_parity(struct gv_plex *p, struc bp->bio_parent->bio_error = EAGAIN; /* ... but we rebuild it. */ - if (bp->bio_parent->bio_cflags & GV_BIO_PARITY) { + if (bp->bio_parent->bio_pflags & GV_BIO_PARITY) { s = pbp->bio_caller1; g_io_request(pbp, s->drive_sc->consumer); finished = 0; @@ -546,6 +546,18 @@ gv_plex_flush(struct gv_plex *p) } } +static void +gv_post_bio(struct gv_softc *sc, struct bio *bp) +{ + + KASSERT(sc != NULL, ("NULL sc")); + KASSERT(bp != NULL, ("NULL bp")); + mtx_lock(&sc->bqueue_mtx); + bioq_disksort(sc->bqueue_down, bp); + wakeup(sc); + mtx_unlock(&sc->bqueue_mtx); +} + int gv_sync_request(struct gv_plex *from, struct gv_plex *to, off_t offset, off_t length, int type, caddr_t data) @@ -566,14 +578,14 @@ gv_sync_request(struct gv_plex *from, st } bp->bio_length = length; bp->bio_done = gv_done; - bp->bio_cflags |= GV_BIO_SYNCREQ; + bp->bio_pflags |= GV_BIO_SYNCREQ; bp->bio_offset = offset; bp->bio_caller1 = from; bp->bio_caller2 = to; bp->bio_cmd = type; if (data == NULL) data = g_malloc(length, M_WAITOK); - bp->bio_cflags |= GV_BIO_MALLOC; /* Free on the next run. */ + bp->bio_pflags |= GV_BIO_MALLOC; /* Free on the next run. */ bp->bio_data = data; /* Send down next. */ @@ -613,7 +625,7 @@ gv_sync_complete(struct gv_plex *to, str BIO_WRITE, bp->bio_data); /* If it was a write, read the next one. */ } else if (bp->bio_cmd == BIO_WRITE) { - if (bp->bio_cflags & GV_BIO_MALLOC) + if (bp->bio_pflags & GV_BIO_MALLOC) g_free(bp->bio_data); to->synced += bp->bio_length; /* If we're finished, clean up. */ @@ -684,10 +696,10 @@ gv_grow_request(struct gv_plex *p, off_t bp->bio_caller1 = p; bp->bio_offset = offset; bp->bio_length = length; - bp->bio_pflags |= GV_BIO_SYNCREQ; /* XXX: misuse of pflags AND syncreq.*/ + bp->bio_pflags |= GV_BIO_GROW; if (data == NULL) data = g_malloc(length, M_WAITOK); - bp->bio_cflags |= GV_BIO_MALLOC; + bp->bio_pflags |= GV_BIO_MALLOC; bp->bio_data = data; gv_post_bio(sc, bp); @@ -720,7 +732,7 @@ gv_grow_complete(struct gv_plex *p, stru BIO_WRITE, bp->bio_data); /* If it was a write, read next. */ } else if (bp->bio_cmd == BIO_WRITE) { - if (bp->bio_cflags & GV_BIO_MALLOC) + if (bp->bio_pflags & GV_BIO_MALLOC) g_free(bp->bio_data); /* Find the real size of the plex. */ @@ -790,7 +802,7 @@ gv_init_request(struct gv_sd *s, off_t s bp->bio_done = gv_done; bp->bio_error = 0; bp->bio_length = length; - bp->bio_cflags |= GV_BIO_INIT; + bp->bio_pflags |= GV_BIO_INIT; bp->bio_offset = start; bp->bio_caller1 = s; @@ -908,8 +920,8 @@ gv_parity_request(struct gv_plex *p, int return; } - bp->bio_cflags = flags; - bp->bio_cflags |= GV_BIO_MALLOC; + bp->bio_pflags = flags; + bp->bio_pflags |= GV_BIO_MALLOC; /* We still have more parity to build. */ bp->bio_offset = offset; @@ -927,14 +939,14 @@ gv_parity_complete(struct gv_plex *p, st int error, flags; error = bp->bio_error; - flags = bp->bio_cflags; + flags = bp->bio_pflags; flags &= ~GV_BIO_MALLOC; sc = p->vinumconf; KASSERT(sc != NULL, ("gv_parity_complete: NULL sc")); /* Clean up what we allocated. */ - if (bp->bio_cflags & GV_BIO_MALLOC) + if (bp->bio_pflags & GV_BIO_MALLOC) g_free(bp->bio_data); g_destroy_bio(bp); @@ -986,14 +998,14 @@ gv_rebuild_complete(struct gv_plex *p, s off_t offset; error = bp->bio_error; - flags = bp->bio_cflags; + flags = bp->bio_pflags; offset = bp->bio_offset; flags &= ~GV_BIO_MALLOC; sc = p->vinumconf; KASSERT(sc != NULL, ("gv_rebuild_complete: NULL sc")); /* Clean up what we allocated. */ - if (bp->bio_cflags & GV_BIO_MALLOC) + if (bp->bio_pflags & GV_BIO_MALLOC) g_free(bp->bio_data); g_destroy_bio(bp); Modified: head/sys/geom/vinum/geom_vinum_raid5.c ============================================================================== --- head/sys/geom/vinum/geom_vinum_raid5.c Wed May 6 19:18:19 2009 (r191855) +++ head/sys/geom/vinum/geom_vinum_raid5.c Wed May 6 19:34:32 2009 (r191856) @@ -65,9 +65,9 @@ gv_raid5_start(struct gv_plex *p, struct wp->parity = NULL; TAILQ_INIT(&wp->bits); - if (bp->bio_cflags & GV_BIO_REBUILD) + if (bp->bio_pflags & GV_BIO_REBUILD) err = gv_raid5_rebuild(p, wp, bp, addr, boff, bcount); - else if (bp->bio_cflags & GV_BIO_CHECK) + else if (bp->bio_pflags & GV_BIO_CHECK) err = gv_raid5_check(p, wp, bp, addr, boff, bcount); else err = gv_raid5_request(p, wp, bp, addr, boff, bcount, &delay); @@ -120,8 +120,8 @@ gv_raid5_start(struct gv_plex *p, struct } /* If internal, stop and reset state. */ - if (bp->bio_cflags & GV_BIO_INTERNAL) { - if (bp->bio_cflags & GV_BIO_MALLOC) + if (bp->bio_pflags & GV_BIO_INTERNAL) { + if (bp->bio_pflags & GV_BIO_MALLOC) g_free(bp->bio_data); g_destroy_bio(bp); /* Reset flags. */ @@ -277,7 +277,7 @@ gv_raid5_rebuild(struct gv_plex *p, stru return (EINVAL); case GV_SD_STALE: - if (!(bp->bio_cflags & GV_BIO_REBUILD)) + if (!(bp->bio_pflags & GV_BIO_REBUILD)) return (ENXIO); G_VINUM_DEBUG(1, "sd %s is reviving", broken->name); @@ -326,7 +326,6 @@ gv_raid5_rebuild(struct gv_plex *p, stru cbp = gv_raid5_clone_bio(bp, broken, wp, NULL, 1); if (cbp == NULL) return (ENOMEM); - cbp->bio_cflags |= GV_BIO_REBUILD; wp->parity = cbp; p->synced = boff; @@ -400,7 +399,7 @@ gv_raid5_request(struct gv_plex *p, stru /* If synchronizing request, just write it if disks are stale. */ if (original->state == GV_SD_STALE && parity->state == GV_SD_STALE && - bp->bio_cflags & GV_BIO_SYNCREQ && bp->bio_cmd == BIO_WRITE) { + bp->bio_pflags & GV_BIO_SYNCREQ && bp->bio_cmd == BIO_WRITE) { type = REQ_TYPE_NORMAL; /* Our parity stripe is missing. */ } else if (parity->state != GV_SD_UP) { Modified: head/sys/geom/vinum/geom_vinum_var.h ============================================================================== --- head/sys/geom/vinum/geom_vinum_var.h Wed May 6 19:18:19 2009 (r191855) +++ head/sys/geom/vinum/geom_vinum_var.h Wed May 6 19:34:32 2009 (r191856) @@ -108,7 +108,7 @@ #define GV_DFLT_SYNCSIZE 65536 /* Flags for BIOs, as they are processed within vinum. */ -#define GV_BIO_DONE 0x01 +#define GV_BIO_GROW 0x01 #define GV_BIO_MALLOC 0x02 #define GV_BIO_ONHOLD 0x04 #define GV_BIO_SYNCREQ 0x08 @@ -117,7 +117,7 @@ #define GV_BIO_CHECK 0x40 #define GV_BIO_PARITY 0x80 #define GV_BIO_INTERNAL \ - (GV_BIO_SYNCREQ | GV_BIO_INIT | GV_BIO_REBUILD |GV_BIO_CHECK) + (GV_BIO_SYNCREQ | GV_BIO_INIT | GV_BIO_REBUILD | GV_BIO_CHECK | GV_BIO_GROW) /* Error codes to be used within gvinum. */ #define GV_ERR_SETSTATE (-1) /* Error setting state. */ @@ -233,7 +233,10 @@ struct gv_softc { struct mtx equeue_mtx; /* Event queue lock. */ struct mtx bqueue_mtx; /* BIO queue lock. */ struct mtx config_mtx; /* Configuration lock. */ - struct bio_queue_head *bqueue; /* BIO queue. */ + struct bio_queue_head *bqueue_down; /* BIO queue incoming + requests. */ + struct bio_queue_head *bqueue_up; /* BIO queue for completed + requests. */ struct g_geom *geom; /* Pointer to our VINUM geom. */ }; #endif _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From lulf at FreeBSD.org Wed May 6 19:46:50 2009 From: lulf at FreeBSD.org (lulf@FreeBSD.org) Date: Wed May 6 19:46:56 2009 Subject: kern/133604: [gvinum] [panic] writing to gjournal on a gvinum volume Message-ID: <200905061946.n46JknuN060150@freefall.freebsd.org> Synopsis: [gvinum] [panic] writing to gjournal on a gvinum volume State-Changed-From-To: open->closed State-Changed-By: lulf State-Changed-When: Wed May 6 19:45:37 UTC 2009 State-Changed-Why: - A fix was committed. A standalone fix will probably not be committed to -STABLE until a possible MFC of gvinum from HEAD. http://www.freebsd.org/cgi/query-pr.cgi?pr=133604 From edwintorok at gmail.com Fri May 8 19:19:11 2009 From: edwintorok at gmail.com (=?ISO-8859-1?Q?T=F6r=F6k_Edwin?=) Date: Fri May 8 19:19:18 2009 Subject: compatibility with Linux software RAID? Message-ID: <4A048020.3070709@gmail.com> Hi, Apologies if this has been answered before, but is there a way to access (even if just read-only) RAID arrays created by Linux software raid tools (mdadm)? I want to test the new superpages support in FreeBSD 7.2, and do some performance comparisons with Linux, problem is all my data is on a RAID10 array. I have this RAID10 array (according to /proc/mdstat Linux): md4 : active raid10 sda3[0] sdc3[5] sdf3[4] sdd3[3] sde3[2] sdb3[1] 2159617728 blocks 64K chunks 2 near-copies [6/6] [UUUUUU] See here for how Linux's md driver lays out data: http://en.wikipedia.org/wiki/Non-standard_RAID_levels#Linux_MD_RAID_10 Does FreeBSD support reading this RAID format? Alternatively I also have a RAID1 array on same disks: md3 : active raid1 sda1[0] sdd1[5] sde1[4] sdf1[3] sdb1[2] sdc1[1] 9767424 blocks [6/6] [UUUUUU] I see that FreeBSD supports RAID1, but will it read in parallel from all 6 disks? (if not I can just mount one of them readonly) Also if gmirror does support the above, is there a way to tell it to treat the disks as readonly? Also is there support for recognizing Linux RAID superblocks (partition type 0xf Linux raid autodetect)? Best regards, --Edwin From bugmaster at FreeBSD.org Mon May 11 11:06:57 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 11 11:08:07 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200905111106.n4BB6teF085960@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/134113 geom [geli] Problem setting secondary GELI key o kern/134044 geom [geom] gmirror(8) overwrites fs with stale data from r o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o kern/132273 geom glabel(8): [patch] failing on journaled partition o kern/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131353 geom [geom] gjournal(8) kernel lock o kern/131037 geom [geli] Unable to create disklabel on .eli-Device o kern/130528 geom gjournal fsck during boot o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid o bin/128398 geom [patch] glabel(8): teach geom_label to recognise gpt l f kern/128276 geom [gmirror] machine lock up when gmirror module is used o kern/126902 geom [geom] geom_label: kernel panic during install boot o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s o kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/124130 geom [gmirror] [usb] gmirror fails to start usb devices tha o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123630 geom [patch] [gmirror] gmirror doesnt allow the original dr o kern/123122 geom [geom] GEOM / gjournal kernel lock f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120231 geom [geom] GEOM_CONCAT error adding second drive o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/120021 geom [geom] [panic] net-p2p/qbittorrent crashes system when o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o kern/89546 geom [geom] GEOM error s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. s kern/73177 geom kldload geom_* causes panic due to memory exhaustion 51 problems total. From ivoras at freebsd.org Wed May 13 12:56:52 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Wed May 13 12:56:58 2009 Subject: compatibility with Linux software RAID? In-Reply-To: <4A048020.3070709@gmail.com> References: <4A048020.3070709@gmail.com> Message-ID: T?r?k Edwin wrote: > Hi, > > Apologies if this has been answered before, but is there a way to access > (even if just read-only) RAID arrays created by Linux software raid > tools (mdadm)? > > I want to test the new superpages support in FreeBSD 7.2, and do some > performance comparisons with Linux, problem is all my data is on a > RAID10 array. RAID is not the only problem you have - how will you access the data? FreeBSD's ext2 file system driver isn't nearly as good for any kind of realistic performance testing - you'd probably need to test Linux with extX and FreeBSD with UFS2. > Also if gmirror does support the above, is there a way to tell it to > treat the disks as readonly? Both gmirror and gstripe can work in a sort of "on-the-fly" mode, without actually committing any configuration to the drives (see the "create" command in both). In theory, you could use gmirror and gstripe with exactly the same parameters as you did in Linux to reconstitute your data. You'll also probably need gnop to align data before using gmirror and gstripe. Of course, only do this if you're completely sure what you're doing and know how RAID10 is physically implemented. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20090513/5d0a52b6/signature.pgp From edwintorok at gmail.com Thu May 14 12:11:55 2009 From: edwintorok at gmail.com (=?ISO-8859-1?Q?T=F6r=F6k_Edwin?=) Date: Thu May 14 12:12:02 2009 Subject: freebsd-geom Digest, Vol 263, Issue 2 In-Reply-To: <20090514120030.7F37510656DC@hub.freebsd.org> References: <20090514120030.7F37510656DC@hub.freebsd.org> Message-ID: <4A0C0A85.50001@gmail.com> On 2009-05-14 15:00, freebsd-geom-request@freebsd.org wrote: > Send freebsd-geom mailing list submissions to > freebsd-geom@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-geom > or, via email, send a message with subject or body 'help' to > freebsd-geom-request@freebsd.org > > You can reach the person managing the list at > freebsd-geom-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-geom digest..." > > > Today's Topics: > > 1. Re: compatibility with Linux software RAID? (Ivan Voras) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 13 May 2009 14:56:37 +0200 > From: Ivan Voras > Subject: Re: compatibility with Linux software RAID? > To: freebsd-geom@freebsd.org > Message-ID: > Content-Type: text/plain; charset="utf-8" > > T??r??k Edwin wrote: > >> Hi, >> >> Apologies if this has been answered before, but is there a way to access >> (even if just read-only) RAID arrays created by Linux software raid >> tools (mdadm)? >> >> I want to test the new superpages support in FreeBSD 7.2, and do some >> performance comparisons with Linux, problem is all my data is on a >> RAID10 array. >> > > RAID is not the only problem you have - how will you access the data? > FreeBSD's ext2 file system driver isn't nearly as good for any kind of > realistic performance testing - you'd probably need to test Linux with > extX and FreeBSD with UFS2. > I can test FreeBSD booted with superpages enabled vs FreeBSD booted without superpages enabled. You're right that comparing FreeBSD w/ Linux FS vs. Linux w/ Linux FS is not fair. I could copy the data to a temporary ramfs storage, and test from there to eliminate filesystem differences. (not taking the time needed to copy the data into account). > >> Also if gmirror does support the above, is there a way to tell it to >> treat the disks as readonly? >> > > Both gmirror and gstripe can work in a sort of "on-the-fly" mode, > without actually committing any configuration to the drives (see the > "create" command in both). In theory, you could use gmirror and gstripe > with exactly the same parameters as you did in Linux to reconstitute > your data. You'll also probably need gnop to align data before using > gmirror and gstripe. Of course, only do this if you're completely sure > what you're doing and know how RAID10 is physically implemented. > Thanks, I'll do some experiments in a VM first, and if it all works I'll move on to testing with the real drives. Best regards, --Edwin From achill at matrix.gatewaynet.com Mon May 18 09:36:30 2009 From: achill at matrix.gatewaynet.com (Achilleas Mantzios) Date: Mon May 18 09:36:38 2009 Subject: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online Message-ID: <200905181200.28732.achill@matrix.gatewaynet.com> Hello, in advance sorry for the cross posting, it is just that freebsd-geom didnt seem that populated. I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf0000000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: "GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22)." Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status Name Status Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? Thanx for any suggestions. -- Achilleas Mantzios From achill at matrix.gatewaynet.com Mon May 18 09:36:32 2009 From: achill at matrix.gatewaynet.com (Achilleas Mantzios) Date: Mon May 18 09:36:55 2009 Subject: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online Message-ID: <200905181204.09021.achill@matrix.gatewaynet.com> Hello, in advance sorry for the cross posting, it is just that freebsd-geom didnt seem that populated. I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf0000000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: "GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22)." Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status Name Status Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? Thanx for any suggestions. -- Achilleas Mantzios From panixgr at yahoo.com Mon May 18 09:38:59 2009 From: panixgr at yahoo.com (panix panix) Date: Mon May 18 09:39:12 2009 Subject: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online Message-ID: <559547.57332.qm@web31605.mail.mud.yahoo.com> Hello, in advance sorry for the cross posting, it is just that freebsd-geom didnt seem that populated. I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf0000000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: "GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22)." Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status Name Status Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? Thanx for any suggestions. From bugmaster at FreeBSD.org Mon May 18 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 18 11:08:15 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200905181106.n4IB6qCp075659@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/134113 geom [geli] Problem setting secondary GELI key o kern/134044 geom [geom] gmirror(8) overwrites fs with stale data from r o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o kern/132273 geom glabel(8): [patch] failing on journaled partition o kern/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131353 geom [geom] gjournal(8) kernel lock o kern/131037 geom [geli] Unable to create disklabel on .eli-Device o kern/130528 geom gjournal fsck during boot o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid o bin/128398 geom [patch] glabel(8): teach geom_label to recognise gpt l f kern/128276 geom [gmirror] machine lock up when gmirror module is used o kern/126902 geom [geom] geom_label: kernel panic during install boot o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s o kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/124130 geom [gmirror] [usb] gmirror fails to start usb devices tha o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123630 geom [patch] [gmirror] gmirror doesnt allow the original dr o kern/123122 geom [geom] GEOM / gjournal kernel lock f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120231 geom [geom] GEOM_CONCAT error adding second drive o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/120021 geom [geom] [panic] net-p2p/qbittorrent crashes system when o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o kern/89546 geom [geom] GEOM error s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. s kern/73177 geom kldload geom_* causes panic due to memory exhaustion 51 problems total. From achill at matrix.gatewaynet.com Mon May 18 13:07:41 2009 From: achill at matrix.gatewaynet.com (Achilleas Mantzios) Date: Mon May 18 13:07:48 2009 Subject: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online Message-ID: <200905181200.28732.achill@matrix.gatewaynet.com> Hello, in advance sorry for the cross posting, it is just that freebsd-geom didnt seem that populated. I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf0000000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: "GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22)." Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status Name Status Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? Thanx for any suggestions. -- Achilleas Mantzios _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From achill at matrix.gatewaynet.com Mon May 18 13:07:47 2009 From: achill at matrix.gatewaynet.com (Achilleas Mantzios) Date: Mon May 18 13:09:17 2009 Subject: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online Message-ID: <200905181204.09021.achill@matrix.gatewaynet.com> Hello, in advance sorry for the cross posting, it is just that freebsd-geom didnt seem that populated. I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf0000000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: "GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22)." Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status Name Status Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? Thanx for any suggestions. -- Achilleas Mantzios _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From panixgr at yahoo.com Mon May 18 13:07:54 2009 From: panixgr at yahoo.com (panix panix) Date: Mon May 18 13:10:09 2009 Subject: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online Message-ID: <559547.57332.qm@web31605.mail.mud.yahoo.com> Hello, in advance sorry for the cross posting, it is just that freebsd-geom didnt seem that populated. I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf0000000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: "GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22)." Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status Name Status Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? Thanx for any suggestions. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From achill at matrix.gatewaynet.com Mon May 18 17:05:08 2009 From: achill at matrix.gatewaynet.com (Achilleas Mantzios) Date: Mon May 18 17:05:24 2009 Subject: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online Message-ID: <200905181020.20621.achill@matrix.gatewaynet.com> Hello, I run 7.1-PRERELEASE, its a home server. today morning after a power failure, the rebuild my root gm0 failed on disk ad4. The messages were: May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 May 18 08:02:08 panix kernel: drm0: on vgapci0 May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf0000000 128MB May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 May 18 08:02:08 panix kernel: drm0: [ITHREAD] May 18 08:02:08 panix kernel: ad4: FAILURE - device detached May 18 08:02:08 panix kernel: subdisk4: detached May 18 08:02:08 panix kernel: ad4: detached May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ hoping that the rebuld failure was temprary and so i tried to just run # gmirror forget gm0 # gmirror insert gm0 ad4 But the system responded (if i remember correctly) Unknown provider ad4. The system no longer could see ad4 being online. So i rebooted the system many times and had these results: -When having put offline ad4 (disconnected by hardware), the system booted ok. -When having both disks online the system responded consistently with: "GEOM_MIRROR: Cannot add disk ad6 to gm0 (error=22)." Which IMO is not very ok, since gm0 should add ad6 without problem, no matter if ad4 is online or not. -When having only ad4 online, then it simply cannot find gm0 at all. (kind of reasonable) So my only option is to have only ad6 online, with a current gmirror status: panix# gmirror status Name Status Components mirror/gm0 COMPLETE ad6 Anyone has an idea of how should i proceed (besides buying a UPS unit!) Is it meaningfull to go for a new Disk to replace current ad4? Why is the presence of the supposed bad disk ad4, affecting gm0, when having already told gm0 to forget about ad4? Thanx for any suggestions. -- Achilleas Mantzios From 000.fbsd at quip.cz Mon May 18 19:22:50 2009 From: 000.fbsd at quip.cz (Miroslav Lachman) Date: Mon May 18 19:23:02 2009 Subject: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online In-Reply-To: <200905181020.20621.achill@matrix.gatewaynet.com> References: <200905181020.20621.achill@matrix.gatewaynet.com> Message-ID: <4A11B1EC.3090601@quip.cz> Achilleas Mantzios wrote: > Hello, > I run 7.1-PRERELEASE, its a home server. > today morning after a power failure, the rebuild my root gm0 failed on disk ad4. > The messages were: > > May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 > May 18 08:02:08 panix kernel: drm0: on vgapci0 > May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf0000000 128MB > May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 > May 18 08:02:08 panix kernel: drm0: [ITHREAD] > May 18 08:02:08 panix kernel: ad4: FAILURE - device detached > May 18 08:02:08 panix kernel: subdisk4: detached > May 18 08:02:08 panix kernel: ad4: detached > May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. > May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. > > I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ > hoping that the rebuld failure was temprary > and so i tried to just run > # gmirror forget gm0 > # gmirror insert gm0 ad4 The correct order of commands is: atacontrol list gmirror list gmirror forget gm0 gmirror clear -v ad4 gmirror insert -v gm0 ad4 Miroslav Lachman From achill at matrix.gatewaynet.com Tue May 19 10:05:07 2009 From: achill at matrix.gatewaynet.com (Achilleas Mantzios) Date: Tue May 19 10:05:14 2009 Subject: Weird problem with gmirror - cannot add the Good disk when previously failed SATA disk is online In-Reply-To: <4A11B1EC.3090601@quip.cz> References: <200905181020.20621.achill@matrix.gatewaynet.com> <4A11B1EC.3090601@quip.cz> Message-ID: <200905191305.01618.achill@matrix.gatewaynet.com> ???? Monday 18 May 2009 22:07:24 ?/? Miroslav Lachman ??????: > Achilleas Mantzios wrote: > > Hello, > > I run 7.1-PRERELEASE, its a home server. > > today morning after a power failure, the rebuild my root gm0 failed on disk ad4. > > The messages were: > > > > May 18 08:02:02 panix kernel: ad4: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=268091264 > > May 18 08:02:08 panix kernel: drm0: on vgapci0 > > May 18 08:02:08 panix kernel: info: [drm] AGP at 0xf0000000 128MB > > May 18 08:02:08 panix kernel: info: [drm] Initialized i915 1.5.0 20060119 > > May 18 08:02:08 panix kernel: drm0: [ITHREAD] > > May 18 08:02:08 panix kernel: ad4: FAILURE - device detached > > May 18 08:02:08 panix kernel: subdisk4: detached > > May 18 08:02:08 panix kernel: ad4: detached > > May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: provider ad4 disconnected. > > May 18 08:02:08 panix kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad4 stopped. > > > > I read http://www.eztiger.org/2008/08/removing-and-re-adding-a-disk-in-gmirror/ > > hoping that the rebuld failure was temprary > > and so i tried to just run > > # gmirror forget gm0 > > # gmirror insert gm0 ad4 > > The correct order of commands is: > atacontrol list > gmirror list > > gmirror forget gm0 > gmirror clear -v ad4 > gmirror insert -v gm0 ad4 > Thanx. > > Miroslav Lachman > -- Achilleas Mantzios From ivoras at freebsd.org Thu May 21 17:33:43 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Thu May 21 17:33:51 2009 Subject: gjournal+gstripe+gmirror question In-Reply-To: References: Message-ID: Alexei Troussov wrote: > Hello All, > > I decided to build multi-terabyte data storage (file server) using 4 x > 1Tb disks. No special raid controller is used, FreeBSD 7.1 is running on > another disk, so the disk array is going to be used for file storage only. > So, I tried several combinations of gmirror/gstripe and put gjournal on it: > > 1) two mirrors and stripe on them This is RAID 10 > 2) two stripes and mirror on them This is RAID 01. It is slightly worse because if one drive fails, no other drive must be allowed to fail. In the RAID10 case, each drive from the mirrored sets can fail. > Both configurations gave excellent I/O speed (around 100Mb/sec), and I You should get better - the total performance should be near or even slightly above 2-drive striped (RAID-0) configuration. Modern drives have sequential performance between 60 MB/s and 80 MB/s so you should be getting between 120 MB/s and 160 MB/s. > chose the first one as it needs less time to resync disks when one of > the mirrors fails. To make picture more complete, I didn't try graid3 > because it seems to load CPU more than configs above, which is not good > for my barebone :) Correct. > Now when my top-level gstripe gets "gjournal"-ed, I see relatively poor > write speed around 20-30 Mb/sec. > As far as I understand from man gjournal and some posts here, > performance usually drops about 40-50%, but what I have is much worse... > > Are there a better way to configure/tune the whole thing? > Thanks in advance! > > PS Here is my current playground config: > Stripesize: 131072 Try a stripe size of 16 kB. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 258 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20090521/70f2a0e4/signature.pgp From bugmaster at FreeBSD.org Mon May 25 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon May 25 11:08:08 2009 Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org Message-ID: <200905251106.n4PB6p1A092794@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/134113 geom [geli] Problem setting secondary GELI key o kern/134044 geom [geom] gmirror(8) overwrites fs with stale data from r o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o kern/132273 geom glabel(8): [patch] failing on journaled partition o kern/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131353 geom [geom] gjournal(8) kernel lock o kern/131037 geom [geli] Unable to create disklabel on .eli-Device o kern/130528 geom gjournal fsck during boot o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid o bin/128398 geom [patch] glabel(8): teach geom_label to recognise gpt l f kern/128276 geom [gmirror] machine lock up when gmirror module is used o kern/126902 geom [geom] geom_label: kernel panic during install boot o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s o kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/124130 geom [gmirror] [usb] gmirror fails to start usb devices tha o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123630 geom [patch] [gmirror] gmirror doesnt allow the original dr o kern/123122 geom [geom] GEOM / gjournal kernel lock f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120231 geom [geom] GEOM_CONCAT error adding second drive o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/120021 geom [geom] [panic] net-p2p/qbittorrent crashes system when o kern/119743 geom [geom] geom label for cds is keeped after dismount and o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o kern/89546 geom [geom] GEOM error s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. s kern/73177 geom kldload geom_* causes panic due to memory exhaustion 51 problems total. From gavin at FreeBSD.org Tue May 26 08:57:27 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Tue May 26 08:57:39 2009 Subject: kern/134922: kernel panic when use fdisk on disk who been removed from gmirror Message-ID: <200905260857.n4Q8vQla085832@freefall.freebsd.org> Synopsis: kernel panic when use fdisk on disk who been removed from gmirror Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: gavin Responsible-Changed-When: Tue May 26 08:56:32 UTC 2009 Responsible-Changed-Why: ver to maintainer(s) http://www.freebsd.org/cgi/query-pr.cgi?pr=134922 From dan.naumov at gmail.com Wed May 27 00:04:47 2009 From: dan.naumov at gmail.com (Dan Naumov) Date: Wed May 27 00:05:19 2009 Subject: GELI encryption - CPU requirements? Message-ID: Hello (World). I am in the process of building a new system for a home NAS/webserver use and the hardware is basically this: Intel Atom 330 (1,6 Ghz, dualcore), a motherboard based on Intel D945GCLF2, 2 GB RAM. Silicon Image SIL3124 4xSATA RAID card (intended to be used in JBOD mode) 1 x 1.5 TB Western Digital Caviar Green (will get more as the need arises) A pic of the system, for the curious: http://tranquilpc.files.wordpress.com/2009/03/bbs2-pure-and-simple-storage.jpg?w=500&h=360 I have been looking into encrypting most of the system with GELI using the default 256bit AES, how big of a performance hit should I expect on this CPU? I know there is no way of giving any exact estimations without actual measurements on the given set of hardware, but either way, assuming long sequential reads or writes off a single SATA disk, what would you expect your CPU usage to be like and whats the actual read/write performance hit is likely to be? I tried googling for some "with and without GELI encryption" kind of benchmarks, but unfortunately couldn't find any. Thank you. Dan Naumov From rwmaillists at googlemail.com Wed May 27 01:33:57 2009 From: rwmaillists at googlemail.com (RW) Date: Wed May 27 01:34:03 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: References: Message-ID: <20090527020034.1087a542@gumby.homeunix.com> On Wed, 27 May 2009 02:37:08 +0300 Dan Naumov wrote: > Hello (World). > > I am in the process of building a new system for a home NAS/webserver > use and the hardware is basically this: > > Intel Atom 330 (1,6 Ghz, dualcore), a motherboard based on Intel > D945GCLF2, 2 GB RAM. > Silicon Image SIL3124 4xSATA RAID card (intended to be used in JBOD > mode) 1 x 1.5 TB Western Digital Caviar Green (will get more as the > need arises) > > I have been looking into encrypting most of the system with GELI using > the default 256bit AES, how big of a performance hit should I expect > on this CPU? Probably quite significant for some disk operations. I have a 4 year old 2.8 GHz single-core amd64 running i386 and I see ~100% cpu utilization when copying large files between two geli partitions. If you haven't already bought it you might want to look at cpus with AES hardware acceleration. From ivoras at freebsd.org Wed May 27 09:33:50 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Wed May 27 09:33:58 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: References: Message-ID: Dan Naumov wrote: > Hello (World). > > I am in the process of building a new system for a home NAS/webserver > use and the hardware is basically this: > > Intel Atom 330 (1,6 Ghz, dualcore), a motherboard based on Intel > D945GCLF2, 2 GB RAM. > Silicon Image SIL3124 4xSATA RAID card (intended to be used in JBOD mode) > 1 x 1.5 TB Western Digital Caviar Green (will get more as the need arises) > > A pic of the system, for the curious: > http://tranquilpc.files.wordpress.com/2009/03/bbs2-pure-and-simple-storage.jpg?w=500&h=360 > > I have been looking into encrypting most of the system with GELI using > the default 256bit AES, how big of a performance hit should I expect > on this CPU? If you have an Atom machine you can simply check - issue an "openssl speed aes" command and check the results. For comparison, Xeon 5405 (2 GHz) gives: type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes aes-128 cbc 89558.04k 101934.80k 104123.42k 102857.83k 103801.84k aes-192 cbc 84368.49k 89821.97k 91069.49k 90385.70k 91112.45k aes-256 cbc 75515.15k 80486.21k 81367.19k 80650.02k 81554.34k I.e. with AES-256 and blocks of data of 1024 bytes, I get 80 MB/s. Except if you're really paranoid, you might want to relax your security requirements and use aes-128 without essentially reducing your practical security. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20090527/a3b7ad9d/signature.pgp From ac at belngo.info Wed May 27 11:03:08 2009 From: ac at belngo.info (Alaksiej C) Date: Wed May 27 11:03:15 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: References: Message-ID: <5709ce310905270331t38952f66uf872a85b3e799596@mail.gmail.com> Ivan Voras : > Except if you're really paranoid, you might want to relax your security > requirements and use aes-128 without essentially reducing your practical > security. It's true. Also, sector size option (-s) could help you. Larger its value - faster ciphering, for the price of less optimal disk space usage, of course. From dan.naumov at gmail.com Wed May 27 11:45:49 2009 From: dan.naumov at gmail.com (Dan Naumov) Date: Wed May 27 11:45:56 2009 Subject: Questions on GELI encryption Message-ID: Hello (World) again :) Sorry for creating another discussion thread so fast, but I figured that since the new questions I have do not fall under the scope of "CPU horsepower requirements for GELI", I thought they deserved a new one: 1) I am reading the Handbook section on GELI ( http://www.freebsd.org/doc/en/books/handbook/disks-encrypting.html ) and I am a bit confused. The example a) creates a keyfile b) initializes a provider with the keyfile c) attaches the provider d) creates a new filesystem directly on the provider and e) mounts it Now, I am probably missing something very obvious, but are "slices" no longer a requirement for creating and using an UFS filesystem in FreeBSD? 2) The example in the Handbook encrypts the entire drive. If my system is going to use 1 big drive, I want /home and /data encrypted, while the rest of the system can stay non-encrypted, how should I go about doing this? Should I create a single big slice with 1 big root partition and 2 separated partitions for /home and /data and the initialise GELI on these specific partitions? Can basically anything be used a a "provider" for GELI? A disk drive, a slice, a partition inside a slice, a file? 3) The handbook states the following: "It is not mandatory that both a passphrase and a key file are used; either method of securing the Master Key can be used in isolation.". Now, how to use just the keyfile is pretty obvious, according to the geli manpage "geom init -P" will not use the passphrase as the key component. However, if I want to just protect my data using the passphrase and not use the keyfile(s), how do I do this? What are the implications of using only the passphrase instead of using both a passphrase and a keyfile? Thanks! Dan Naumov From ivoras at freebsd.org Wed May 27 11:50:11 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Wed May 27 11:50:17 2009 Subject: Questions on GELI encryption In-Reply-To: References: Message-ID: Dan Naumov wrote: > Hello (World) again :) > > Sorry for creating another discussion thread so fast, but I figured > that since the new questions I have do not fall under the scope of > "CPU horsepower requirements for GELI", I thought they deserved a new > one: > > 1) I am reading the Handbook section on GELI ( > http://www.freebsd.org/doc/en/books/handbook/disks-encrypting.html ) > and I am a bit confused. The example > > a) creates a keyfile > b) initializes a provider with the keyfile > c) attaches the provider > d) creates a new filesystem directly on the provider and > e) mounts it > > Now, I am probably missing something very obvious, but are "slices" no > longer a requirement for creating and using an UFS filesystem in > FreeBSD? No, and have not been since introduction of GEOM a long-ish time ago. > 2) The example in the Handbook encrypts the entire drive. If my system > is going to use 1 big drive, I want /home and /data encrypted, while > the rest of the system can stay non-encrypted, how should I go about > doing this? Should I create a single big slice with 1 big root > partition and 2 separated partitions for /home and /data and the > initialise GELI on these specific partitions? Yes. > Can basically anything > be used a a "provider" for GELI? A disk drive, a slice, a partition > inside a slice, a file? Yes, again because of GEOM, not specific to GELI. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20090527/830d4e7a/signature.pgp From ac at belngo.info Wed May 27 12:01:33 2009 From: ac at belngo.info (Alaksiej C) Date: Wed May 27 12:01:43 2009 Subject: Questions on GELI encryption In-Reply-To: References: Message-ID: <5709ce310905270501n2f1c3d21n846a7d2f37e528b7@mail.gmail.com> Just in case you will decide to encrypt a whole HDD: Keep in mind that some BIOSes in some situations searches for MBR, and if it's not present, the drive will be regarded as "empty". Therefore BIOS could set HPA and write its backup information to it. As control block of GELI resides at the end of underlying provider (HDD in our case), it will be destroyed. From petefrench at ticketswitch.com Wed May 27 12:27:17 2009 From: petefrench at ticketswitch.com (Pete French) Date: Wed May 27 12:27:24 2009 Subject: Questions on GELI encryption In-Reply-To: Message-ID: > 3) The handbook states the following: "It is not mandatory that both a > passphrase and a key file are used; either method of securing the > Master Key can be used in isolation.". Now, how to use just the > keyfile is pretty obvious, according to the geli manpage "geom init > -P" will not use the passphrase as the key component. However, if I > want to just protect my data using the passphrase and not use the > keyfile(s), how do I do this? What are the implications of using only > the passphrase instead of using both a passphrase and a keyfile? Just initialise is with only the passphrase, and it will ask for it on boot. One thing which always annoyed me was with multiple encrypted drives it would ask me for the opassword multiple times on boot (I have a zpool over the top of encrypted drives). I eventually solved this with a very small encrypted partition (a couple of K) which is then used as the keyfile for the other partitions. So it asks me once, decrypts the small passpharse partition (which is full of random data) and then uses that as the keyfile for the rest of the drives. Works quite nicely. -pete. From dan.naumov at gmail.com Wed May 27 13:25:05 2009 From: dan.naumov at gmail.com (Dan Naumov) Date: Wed May 27 13:25:11 2009 Subject: Questions on GELI encryption In-Reply-To: References: Message-ID: I decided to give geom / geli a bit of a disaster test (inside a VM) 1) I created a new disk "ad1" 2) Created a new slice on it "ad1s1" 3) Created 2 similarly sized (~20GB) partitions inside the silce: "ad1s1d" and "ad1s1e" ======================= geli init -s 4096 /dev/ad1s1d Enter new passphrase: geli attach /dev/ad1s1d Enter passphrase: newfs /dev/a1s1d.eli mount /dev/a1s1d.eli /mnt/geli1 ======================= Alright, now we have a passphrase-protected geli partition working and mounted at /mnt/geli1, now the stress test: cp -R /usr/ports /mnt/geli1 Now that we have rebooted the machine: ======================= geli attach /dev/ad1s1d Enter passphrase: GEOM_ELI: Device ad1s1d.eli created. GEOM_ELI: Encryption: AES-CBC 128 GEOM_ELI: Crypto: software GEOM_LABEL: Label for provider ad1s1d.eli is ufsid/4a1d391db28ff834. ======================= Looking good so far, right? ======================= mount /dev/ad1s1d.eli /mnt/geli1 mount: /dev/ad1s1d.eli : Operation not permitted fsck /dev/ad1s1d.eli fsck: Could not determine filesystem type ======================= Oops :( - Dan Naumov From dan.naumov at gmail.com Wed May 27 13:56:37 2009 From: dan.naumov at gmail.com (Dan Naumov) Date: Wed May 27 13:56:43 2009 Subject: Questions on GELI encryption In-Reply-To: References: Message-ID: Thanks, that worked like a charm. Is there a way to have background fsck autolaunch itself when an attempt is made to mount an unclean ufs filesystem on a geli provider? - Dan Naumov On Wed, May 27, 2009 at 4:48 PM, Michael Jung wrote: > I ran into this also, try: > > fsck -y -t ufs /dev/ad1s1d.eli > > as fsck can not determine the file system type. > > --mikej > > Looking good so far, right? > > > ======================= > mount /dev/ad1s1d.eli /mnt/geli1 > mount: /dev/ad1s1d.eli : Operation not permitted > > fsck /dev/ad1s1d.eli > fsck: Could not determine filesystem type > ======================= > > Oops :( From dan.naumov at gmail.com Wed May 27 14:52:22 2009 From: dan.naumov at gmail.com (Dan Naumov) Date: Wed May 27 14:52:29 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: <5709ce310905270331t38952f66uf872a85b3e799596@mail.gmail.com> References: <5709ce310905270331t38952f66uf872a85b3e799596@mail.gmail.com> Message-ID: It seems that GELI already defaults to AES-128. What documentation should I be looking into to see how different sector size options affect effective available disk space and performance? - Dan Naumov On Wed, May 27, 2009 at 1:31 PM, Alaksiej C wrote: > Ivan Voras : >> Except if you're really paranoid, you might want to relax your security >> requirements and use aes-128 without essentially reducing your practical >> security. > > > It's true. > > Also, sector size option (-s) could help you. Larger its value - > faster ciphering, for the price of less optimal disk space usage, of > course. > _______________________________________________ > 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 dan.naumov at gmail.com Wed May 27 15:57:14 2009 From: dan.naumov at gmail.com (Dan Naumov) Date: Wed May 27 15:57:20 2009 Subject: Questions on GELI encryption In-Reply-To: References: Message-ID: And some further questions: 1) Is there any basis for the claims that in the event of a failure (power outage, slowly dying drive, etc) that one is much more likely to lose ALL his data when using encryption vs not using any encryption? The argument is that when you have a non-encrypted drive or partition that is damaged, you have a lot of tools at your disposal to attempt to recover your data, but if your data is encrypted, even relatively low amount of damage in the "wrong" place on the drive/partition can cause it to become undecipherable and cause complete loss of data. 2) Thanks to the help I have received so far, I now know how to use "passkey + keyfile", "keyfile" and "passkey" init and authentication methods for a encrypted GELI provider. The question I have is whether it is possible to have a "passkey OR keyfile" authentication method when using GELI. The idea is to normally use a strong passkey for attaching and using the providers, while keeping a keyfile stored "elsewhere" in a safe location out of premises. In the event of forgetting the passkey, the keyfile would be retrieved and used to access the data and change the forgotten passkey. Thanks again for your insight. - Dan Naumov On Wed, May 27, 2009 at 4:56 PM, Dan Naumov wrote: > Thanks, that worked like a charm. Is there a way to have background > fsck autolaunch itself when an attempt is made to mount an unclean ufs > filesystem on a geli provider? > > - Dan Naumov From rwmaillists at googlemail.com Wed May 27 16:56:26 2009 From: rwmaillists at googlemail.com (RW) Date: Wed May 27 16:56:31 2009 Subject: Questions on GELI encryption In-Reply-To: References: Message-ID: <20090527175613.1b92c217@gumby.homeunix.com> On Wed, 27 May 2009 18:57:11 +0300 Dan Naumov wrote: > And some further questions: > > 1) Is there any basis for the claims that in the event of a failure > (power outage, slowly dying drive, etc) that one is much more likely > to lose ALL his data when using encryption vs not using any > encryption? The argument is that when you have a non-encrypted drive > or partition that is damaged, you have a lot of tools at your disposal > to attempt to recover your data, but if your data is encrypted, even > relatively low amount of damage in the "wrong" place on the > drive/partition can cause it to become undecipherable and cause > complete loss of data. You can backup the metadata to a file, if you lock yourself out you can use the install disk as a "live-cd" > > 2) Thanks to the help I have received so far, I now know how to use > "passkey + keyfile", "keyfile" and "passkey" init and authentication > methods for a encrypted GELI provider. The question I have is whether > it is possible to have a "passkey OR keyfile" authentication method > when using GELI. The idea is to normally use a strong passkey for > attaching and using the providers, while keeping a keyfile stored > "elsewhere" in a safe location out of premises. In the event of > forgetting the passkey, the keyfile would be retrieved and used to > access the data and change the forgotten passkey. > I've not used it myself, but take a look at the setkey option. You could have key 0 as a passphrase and key 1 as a file. OTOH I don't see the advantage of keeping the file in a safe place over keeping the passphrase in a safe place. From volker at vwsoft.com Wed May 27 20:32:17 2009 From: volker at vwsoft.com (Volker) Date: Wed May 27 20:32:25 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: References: Message-ID: <4A1D9EC5.3020006@vwsoft.com> On 12/23/-58 20:59, Ivan Voras wrote: > Dan Naumov wrote: >> Hello (World). >> >> I am in the process of building a new system for a home NAS/webserver >> use and the hardware is basically this: >> >> Intel Atom 330 (1,6 Ghz, dualcore), a motherboard based on Intel >> D945GCLF2, 2 GB RAM. >> Silicon Image SIL3124 4xSATA RAID card (intended to be used in JBOD mode) >> 1 x 1.5 TB Western Digital Caviar Green (will get more as the need arises) >> >> A pic of the system, for the curious: >> http://tranquilpc.files.wordpress.com/2009/03/bbs2-pure-and-simple-storage.jpg?w=500&h=360 >> >> I have been looking into encrypting most of the system with GELI using >> the default 256bit AES, how big of a performance hit should I expect >> on this CPU? > > If you have an Atom machine you can simply check - issue an "openssl > speed aes" command and check the results. For comparison, Xeon 5405 (2 > GHz) gives: > > type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 > bytes > aes-128 cbc 89558.04k 101934.80k 104123.42k 102857.83k > 103801.84k > aes-192 cbc 84368.49k 89821.97k 91069.49k 90385.70k > 91112.45k > aes-256 cbc 75515.15k 80486.21k 81367.19k 80650.02k > 81554.34k > > I.e. with AES-256 and blocks of data of 1024 bytes, I get 80 MB/s. > > Except if you're really paranoid, you might want to relax your security > requirements and use aes-128 without essentially reducing your practical > security. > For reference, here're the values taken on a dual core Atom: type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes aes-128 cbc 17947.16k 18502.91k 18703.91k 18271.91k 18955.39k aes-192 cbc 16404.93k 15966.46k 16615.41k 16115.26k 16466.56k aes-256 cbc 13711.70k 14016.79k 14342.35k 14109.98k 14738.16k FreeBSD dardanos 7.2-STABLE FreeBSD 7.2-STABLE #10 r192673: Sun May 24 10:22:05 CEST 2009 CPU: Intel(R) Atom(TM) CPU 330 @ 1.60GHz (1618.44-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106c2 Stepping = 2 Features=0xbfe9fbff Features2=0x40e31d> AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Logical CPUs per core: 2 real memory = 2137391104 (2038 MB) avail memory = 2077528064 (1981 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP/HT): APIC ID: 3 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 cryptosoft0: on motherboard I would not expect a fast workhorse but these machines are making a nice desktop system. Enjoy! Volker From dan.naumov at gmail.com Wed May 27 20:41:16 2009 From: dan.naumov at gmail.com (Dan Naumov) Date: Wed May 27 20:41:23 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: <4A1D9EC5.3020006@vwsoft.com> References: <4A1D9EC5.3020006@vwsoft.com> Message-ID: Wow, so on a dual core Atom, I would essentially be bottlenecked by my CPU at 18 MB/s throughput? I guess that puts GELI encryption completely out of the question and I need to look into some other solution :( - Dan Naumov > For reference, here're the values taken on a dual core Atom: > > type ? ? ? ? ? ? 16 bytes ? ? 64 bytes ? ?256 bytes ? 1024 bytes ? 8192 > bytes > aes-128 cbc ? ? ?17947.16k ? ?18502.91k ? ?18703.91k ? ?18271.91k > 18955.39k > > aes-192 cbc ? ? ?16404.93k ? ?15966.46k ? ?16615.41k ? ?16115.26k > 16466.56k > > aes-256 cbc ? ? ?13711.70k ? ?14016.79k ? ?14342.35k ? ?14109.98k > 14738.16k > > > FreeBSD dardanos 7.2-STABLE FreeBSD 7.2-STABLE #10 r192673: Sun May 24 > 10:22:05 CEST 2009 > > CPU: Intel(R) Atom(TM) CPU ?330 ? @ 1.60GHz (1618.44-MHz 686-class CPU) > ?Origin = "GenuineIntel" ?Id = 0x106c2 ?Stepping = 2 > > Features=0xbfe9fbff > ?Features2=0x40e31d> > ?AMD Features=0x20100000 > ?AMD Features2=0x1 > ?Cores per package: 2 > ?Logical CPUs per core: 2 > real memory ?= 2137391104 (2038 MB) > avail memory = 2077528064 (1981 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > ?cpu0 (BSP): APIC ID: ?0 > ?cpu1 (AP/HT): APIC ID: ?1 > ?cpu2 (AP): APIC ID: ?2 > ?cpu3 (AP/HT): APIC ID: ?3 > ioapic0: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > cryptosoft0: on motherboard From dan.naumov at gmail.com Wed May 27 20:58:58 2009 From: dan.naumov at gmail.com (Dan Naumov) Date: Wed May 27 20:59:04 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: <4A1D9EC5.3020006@vwsoft.com> References: <4A1D9EC5.3020006@vwsoft.com> Message-ID: Could you also run the test for: Camellia and Blowfish please? Thanks, - Dan Naumov > For reference, here're the values taken on a dual core Atom: > > type ? ? ? ? ? ? 16 bytes ? ? 64 bytes ? ?256 bytes ? 1024 bytes ? 8192 > bytes > aes-128 cbc ? ? ?17947.16k ? ?18502.91k ? ?18703.91k ? ?18271.91k > 18955.39k > > aes-192 cbc ? ? ?16404.93k ? ?15966.46k ? ?16615.41k ? ?16115.26k > 16466.56k > > aes-256 cbc ? ? ?13711.70k ? ?14016.79k ? ?14342.35k ? ?14109.98k > 14738.16k > > > FreeBSD dardanos 7.2-STABLE FreeBSD 7.2-STABLE #10 r192673: Sun May 24 > 10:22:05 CEST 2009 > > CPU: Intel(R) Atom(TM) CPU ?330 ? @ 1.60GHz (1618.44-MHz 686-class CPU) > ?Origin = "GenuineIntel" ?Id = 0x106c2 ?Stepping = 2 > > Features=0xbfe9fbff > ?Features2=0x40e31d> > ?AMD Features=0x20100000 > ?AMD Features2=0x1 > ?Cores per package: 2 > ?Logical CPUs per core: 2 > real memory ?= 2137391104 (2038 MB) > avail memory = 2077528064 (1981 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > ?cpu0 (BSP): APIC ID: ?0 > ?cpu1 (AP/HT): APIC ID: ?1 > ?cpu2 (AP): APIC ID: ?2 > ?cpu3 (AP/HT): APIC ID: ?3 > ioapic0: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > cryptosoft0: on motherboard > > > I would not expect a fast workhorse but these machines are making a nice > desktop system. > > Enjoy! > > Volker > _______________________________________________ > 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 volker at vwsoft.com Wed May 27 21:23:18 2009 From: volker at vwsoft.com (Volker) Date: Wed May 27 21:24:05 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: References: <4A1D9EC5.3020006@vwsoft.com> Message-ID: <4A1DAF2D.1040604@vwsoft.com> On 05/27/09 22:58, Dan Naumov wrote: > Could you also run the test for: Camellia and Blowfish please? Sure but do not count on the absolute values as the system wasn't idling 100% (~88-96%): type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes camellia-128 cbc 20121.31k 21752.35k 21556.40k 21838.64k 22375.53k camellia-192 cbc 16804.24k 17087.62k 17283.35k 17494.13k 16584.06k camellia-256 cbc 15925.81k 17256.89k 17425.49k 17605.67k 17092.26k type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes blowfish cbc 49186.75k 51979.89k 53195.92k 53742.92k 52371.59k Also I found the sha values of interest: type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes sha1 3303.61k 8459.49k 19921.03k 33585.85k 47594.24k sha256 3408.83k 8519.20k 15886.04k 20473.32k 21481.23k sha512 1065.92k 4681.24k 7383.90k 10189.10k 11597.66k > >> For reference, here're the values taken on a dual core Atom: >> >> type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 >> bytes >> aes-128 cbc 17947.16k 18502.91k 18703.91k 18271.91k >> 18955.39k >> >> aes-192 cbc 16404.93k 15966.46k 16615.41k 16115.26k >> 16466.56k >> >> aes-256 cbc 13711.70k 14016.79k 14342.35k 14109.98k >> 14738.16k >> >> >> FreeBSD dardanos 7.2-STABLE FreeBSD 7.2-STABLE #10 r192673: Sun May 24 >> 10:22:05 CEST 2009 >> >> CPU: Intel(R) Atom(TM) CPU 330 @ 1.60GHz (1618.44-MHz 686-class CPU) >> Origin = "GenuineIntel" Id = 0x106c2 Stepping = 2 >> >> Features=0xbfe9fbff >> Features2=0x40e31d> >> AMD Features=0x20100000 >> AMD Features2=0x1 >> Cores per package: 2 >> Logical CPUs per core: 2 >> real memory = 2137391104 (2038 MB) >> avail memory = 2077528064 (1981 MB) >> ACPI APIC Table: >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> cpu0 (BSP): APIC ID: 0 >> cpu1 (AP/HT): APIC ID: 1 >> cpu2 (AP): APIC ID: 2 >> cpu3 (AP/HT): APIC ID: 3 >> ioapic0: Changing APIC ID to 2 >> ioapic0 irqs 0-23 on motherboard >> kbd1 at kbdmux0 >> cryptosoft0: on motherboard From dan.naumov at gmail.com Wed May 27 21:36:53 2009 From: dan.naumov at gmail.com (Dan Naumov) Date: Wed May 27 21:36:59 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: <4A1DAF2D.1040604@vwsoft.com> References: <4A1D9EC5.3020006@vwsoft.com> <4A1DAF2D.1040604@vwsoft.com> Message-ID: This is great, thanks a lot! Just as I got depressed that if I would be stuck with 18MB/s throughput if I went with my planned route, you provide more results that show that Blowfish would be a great choice for what I want to do, 50 MB/s is going to be plenty for my needs. Your results also seem to be backed by these benchmark results I found (Also ran on an Atom): http://www.mail-archive.com/support@pfsense.com/msg15423.html Thanks a lot again! - Dan Naumov On Thu, May 28, 2009 at 12:22 AM, Volker wrote: > > On 05/27/09 22:58, Dan Naumov wrote: >> Could you also run the test for: Camellia and Blowfish please? > > Sure but do not count on the absolute values as the system wasn't idling > 100% (~88-96%): > > type ? ? ? ? ? ? 16 bytes ? ? 64 bytes ? ?256 bytes ? 1024 bytes ? 8192 > bytes > camellia-128 cbc ? ?20121.31k ? ?21752.35k ? ?21556.40k ? ?21838.64k > 22375.53k > camellia-192 cbc ? ?16804.24k ? ?17087.62k ? ?17283.35k ? ?17494.13k > 16584.06k > camellia-256 cbc ? ?15925.81k ? ?17256.89k ? ?17425.49k ? ?17605.67k > 17092.26k > > type ? ? ? ? ? ? 16 bytes ? ? 64 bytes ? ?256 bytes ? 1024 bytes ? 8192 > bytes > blowfish cbc ? ? 49186.75k ? ?51979.89k ? ?53195.92k ? ?53742.92k > 52371.59k > > Also I found the sha values of interest: > > type ? ? ? ? ? ? 16 bytes ? ? 64 bytes ? ?256 bytes ? 1024 bytes ? 8192 > bytes > sha1 ? ? ? ? ? ? ?3303.61k ? ? 8459.49k ? ?19921.03k ? ?33585.85k > 47594.24k > sha256 ? ? ? ? ? ?3408.83k ? ? 8519.20k ? ?15886.04k ? ?20473.32k > 21481.23k > sha512 ? ? ? ? ? ?1065.92k ? ? 4681.24k ? ? 7383.90k ? ?10189.10k > 11597.66k > > >> >>> For reference, here're the values taken on a dual core Atom: >>> >>> type ? ? ? ? ? ? 16 bytes ? ? 64 bytes ? ?256 bytes ? 1024 bytes ? 8192 >>> bytes >>> aes-128 cbc ? ? ?17947.16k ? ?18502.91k ? ?18703.91k ? ?18271.91k >>> 18955.39k >>> >>> aes-192 cbc ? ? ?16404.93k ? ?15966.46k ? ?16615.41k ? ?16115.26k >>> 16466.56k >>> >>> aes-256 cbc ? ? ?13711.70k ? ?14016.79k ? ?14342.35k ? ?14109.98k >>> 14738.16k >>> >>> >>> FreeBSD dardanos 7.2-STABLE FreeBSD 7.2-STABLE #10 r192673: Sun May 24 >>> 10:22:05 CEST 2009 >>> >>> CPU: Intel(R) Atom(TM) CPU ?330 ? @ 1.60GHz (1618.44-MHz 686-class CPU) >>> ?Origin = "GenuineIntel" ?Id = 0x106c2 ?Stepping = 2 >>> >>> Features=0xbfe9fbff >>> ?Features2=0x40e31d> >>> ?AMD Features=0x20100000 >>> ?AMD Features2=0x1 >>> ?Cores per package: 2 >>> ?Logical CPUs per core: 2 >>> real memory ?= 2137391104 (2038 MB) >>> avail memory = 2077528064 (1981 MB) >>> ACPI APIC Table: >>> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >>> ?cpu0 (BSP): APIC ID: ?0 >>> ?cpu1 (AP/HT): APIC ID: ?1 >>> ?cpu2 (AP): APIC ID: ?2 >>> ?cpu3 (AP/HT): APIC ID: ?3 >>> ioapic0: Changing APIC ID to 2 >>> ioapic0 irqs 0-23 on motherboard >>> kbd1 at kbdmux0 >>> cryptosoft0: on motherboard > > From dan.naumov at gmail.com Wed May 27 22:04:05 2009 From: dan.naumov at gmail.com (Dan Naumov) Date: Wed May 27 22:04:18 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: References: <4A1D9EC5.3020006@vwsoft.com> Message-ID: Wow, when I thought things couldn't get any better, people surprise me :) Volker, could I bug you for another set of Intel Atom results for AES and Blowfish, bu this time with -multi 4? Thanks! - Dan Naumov On Thu, May 28, 2009 at 12:41 AM, Michael Jung wrote: > FWIW: > > You need to use the "-multi " switch for multi-core/multi-processors > > #openssl speed aes > CPU: Dual-Core AMD Opteron(tm) Processor 2216 (2394.02-MHz 686-class CPU) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > ?cpu0 (BSP): APIC ID: ?0 > ?cpu1 (AP): APIC ID: ?1 > ?cpu2 (AP): APIC ID: ?2 > ?cpu3 (AP): APIC ID: ?3 > 7.0-RELEASE > > type ? ? ? ? ? ? 16 bytes ? ? 64 bytes ? ?256 bytes ? 1024 bytes ? 8192 bytes > aes-128 cbc ? ? ?51067.07k ? ?51552.36k ? ?52142.46k ? ?52158.35k ? ?52302.93k > aes-192 cbc ? ? ?44284.34k ? ?45152.29k ? ?45648.03k ? ?45653.66k ? ?45784.30k > aes-256 cbc ? ? ?39358.18k ? ?39717.28k ? ?40087.25k ? ?40117.40k ? ?40196.85k > > Same machine with multi switch > > #openssl speed aes -multi 4 > aes-128 cbc ? ? 204173.66k ? 205888.69k ? 208489.35k ? 208569.53k ? 209142.85k > aes-192 cbc ? ? 176980.36k ? 180404.81k ? 182537.84k ? 182469.91k ? 183064.72k > aes-256 cbc ? ? 157313.97k ? 158619.06k ? 160317.78k ? 160399.19k ? 160746.01k > > --mikej > > -----Original Message----- > From: owner-freebsd-geom@freebsd.org [mailto:owner-freebsd-geom@freebsd.org] On Behalf Of Dan Naumov > Sent: Wednesday, May 27, 2009 4:41 PM > To: freebsd-geom@freebsd.org > Subject: Re: Re: GELI encryption - CPU requirements? > > Wow, so on a dual core Atom, I would essentially be bottlenecked by my > CPU at 18 MB/s throughput? I guess that puts GELI encryption > completely out of the question and I need to look into some other > solution :( > > > - Dan Naumov > > > >> For reference, here're the values taken on a dual core Atom: >> >> type ? ? ? ? ? ? 16 bytes ? ? 64 bytes ? ?256 bytes ? 1024 bytes ? 8192 >> bytes >> aes-128 cbc ? ? ?17947.16k ? ?18502.91k ? ?18703.91k ? ?18271.91k >> 18955.39k >> >> aes-192 cbc ? ? ?16404.93k ? ?15966.46k ? ?16615.41k ? ?16115.26k >> 16466.56k >> >> aes-256 cbc ? ? ?13711.70k ? ?14016.79k ? ?14342.35k ? ?14109.98k >> 14738.16k >> >> >> FreeBSD dardanos 7.2-STABLE FreeBSD 7.2-STABLE #10 r192673: Sun May 24 >> 10:22:05 CEST 2009 >> >> CPU: Intel(R) Atom(TM) CPU ?330 ? @ 1.60GHz (1618.44-MHz 686-class CPU) >> ?Origin = "GenuineIntel" ?Id = 0x106c2 ?Stepping = 2 >> >> Features=0xbfe9fbff >> ?Features2=0x40e31d> >> ?AMD Features=0x20100000 >> ?AMD Features2=0x1 >> ?Cores per package: 2 >> ?Logical CPUs per core: 2 >> real memory ?= 2137391104 (2038 MB) >> avail memory = 2077528064 (1981 MB) >> ACPI APIC Table: >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> ?cpu0 (BSP): APIC ID: ?0 >> ?cpu1 (AP/HT): APIC ID: ?1 >> ?cpu2 (AP): APIC ID: ?2 >> ?cpu3 (AP/HT): APIC ID: ?3 >> ioapic0: Changing APIC ID to 2 >> ioapic0 irqs 0-23 on motherboard >> kbd1 at kbdmux0 >> cryptosoft0: on motherboard > _______________________________________________ > 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" > > CONFIDENTIALITY NOTE: This message is intended only for the use > of the individual or entity to whom it is addressed and may contain > information that is privileged, confidential, and exempt from > disclosure under applicable law. If the reader of this message is > not the intended recipient, you are hereby notified that any > dissemination, distribution or copying of this communication > is strictly prohibited. If you have received this transmission > in error, please notify us by telephone at (502) 212-4001 or > notify us at PAI , Dept. 99, 11857 Commonwealth Drive, > Louisville, KY ?40299. ?Thank you. > From ac at belngo.info Wed May 27 22:50:16 2009 From: ac at belngo.info (Alaksiej C) Date: Wed May 27 22:50:22 2009 Subject: Questions on GELI encryption In-Reply-To: <20090527175613.1b92c217@gumby.homeunix.com> References: <20090527175613.1b92c217@gumby.homeunix.com> Message-ID: <5709ce310905271550j28fc6254t5ee2960f84c50e7b@mail.gmail.com> > 1) Is there any basis for the claims that in the event > of a failure (power outage, slowly dying drive, etc) > that one is much more likely to lose ALL his data > when using encryption vs not using any encryption? > The argument is that when you have a non-encrypted Dan, The only "wrong" place, which if damaged will make your encrypted data unusable is control block (metadata). As it was mentioned before, you can back it up with "geli backup" command. Though, if data is really valuable, it would be better to do backup copies of it regularly regardless of encryption. And if you do, than, speaking about probability of irreparable data loss, there's no difference between encrypted and unencrypted HDD, slice etc. From ac at belngo.info Wed May 27 23:02:50 2009 From: ac at belngo.info (Alaksiej C) Date: Wed May 27 23:03:04 2009 Subject: Questions on GELI encryption In-Reply-To: <5709ce310905271550j28fc6254t5ee2960f84c50e7b@mail.gmail.com> References: <20090527175613.1b92c217@gumby.homeunix.com> <5709ce310905271550j28fc6254t5ee2960f84c50e7b@mail.gmail.com> Message-ID: <5709ce310905271602s5144f877ra487867098785dc2@mail.gmail.com> On Thu, May 28, 2009 at 1:50 AM, Alaksiej C wrote: > Though, if data is really valuable, it would be better to do backup > copies of it regularly regardless of encryption. And if you do, than, > speaking about probability of irreparable data loss, there's no > difference between encrypted and unencrypted HDD, slice etc. > Well, to say more precisely, there's a possibility of losing "last-minute data", which couldn't be recovered from copies, so it's better to backup both data and GELI metadata. In this case, I believe, you will have the same level of repairability as for unencrypted drive. From mikej at paymentallianceintl.com Thu May 28 00:05:12 2009 From: mikej at paymentallianceintl.com (Michael Jung) Date: Thu May 28 00:05:18 2009 Subject: GELI encryption - CPU requirements? In-Reply-To: References: <4A1D9EC5.3020006@vwsoft.com> Message-ID: FWIW: You need to use the "-multi " switch for multi-core/multi-processors #openssl speed aes CPU: Dual-Core AMD Opteron(tm) Processor 2216 (2394.02-MHz 686-class CPU) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 7.0-RELEASE type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes aes-128 cbc 51067.07k 51552.36k 52142.46k 52158.35k 52302.93k aes-192 cbc 44284.34k 45152.29k 45648.03k 45653.66k 45784.30k aes-256 cbc 39358.18k 39717.28k 40087.25k 40117.40k 40196.85k Same machine with multi switch #openssl speed aes -multi 4 aes-128 cbc 204173.66k 205888.69k 208489.35k 208569.53k 209142.85k aes-192 cbc 176980.36k 180404.81k 182537.84k 182469.91k 183064.72k aes-256 cbc 157313.97k 158619.06k 160317.78k 160399.19k 160746.01k --mikej -----Original Message----- From: owner-freebsd-geom@freebsd.org [mailto:owner-freebsd-geom@freebsd.org] On Behalf Of Dan Naumov Sent: Wednesday, May 27, 2009 4:41 PM To: freebsd-geom@freebsd.org Subject: Re: Re: GELI encryption - CPU requirements? Wow, so on a dual core Atom, I would essentially be bottlenecked by my CPU at 18 MB/s throughput? I guess that puts GELI encryption completely out of the question and I need to look into some other solution :( - Dan Naumov > For reference, here're the values taken on a dual core Atom: > > type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 > bytes > aes-128 cbc 17947.16k 18502.91k 18703.91k 18271.91k > 18955.39k > > aes-192 cbc 16404.93k 15966.46k 16615.41k 16115.26k > 16466.56k > > aes-256 cbc 13711.70k 14016.79k 14342.35k 14109.98k > 14738.16k > > > FreeBSD dardanos 7.2-STABLE FreeBSD 7.2-STABLE #10 r192673: Sun May 24 > 10:22:05 CEST 2009 > > CPU: Intel(R) Atom(TM) CPU 330 @ 1.60GHz (1618.44-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x106c2 Stepping = 2 > > Features=0xbfe9fbff > Features2=0x40e31d> > AMD Features=0x20100000 > AMD Features2=0x1 > Cores per package: 2 > Logical CPUs per core: 2 > real memory = 2137391104 (2038 MB) > avail memory = 2077528064 (1981 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP/HT): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP/HT): APIC ID: 3 > ioapic0: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > cryptosoft0: on motherboard _______________________________________________ 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" CONFIDENTIALITY NOTE: This message is intended only for the use of the individual or entity to whom it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, please notify us by telephone at (502) 212-4001 or notify us at PAI , Dept. 99, 11857 Commonwealth Drive, Louisville, KY 40299. Thank you. From linimon at FreeBSD.org Thu May 28 22:14:04 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu May 28 22:14:10 2009 Subject: kern/116896: [geom] [patch] Typo in a kassert in GEOM Message-ID: <200905282214.n4SME4gY075951@freefall.freebsd.org> Old Synopsis: [patch] Typo in a kassert in GEOM New Synopsis: [geom] [patch] Typo in a kassert in GEOM Responsible-Changed-From-To: pjd->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:10:40 UTC 2009 Responsible-Changed-Why: pjd is not actively working on GEOM at the moment. Apparently this fix still needs to be MFCed. http://www.freebsd.org/cgi/query-pr.cgi?pr=116896 From linimon at FreeBSD.org Thu May 28 22:14:39 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu May 28 22:14:46 2009 Subject: bin/81779: misleading error messages in geom(8) utilities. Message-ID: <200905282214.n4SMEcLP076346@freefall.freebsd.org> Synopsis: misleading error messages in geom(8) utilities. Responsible-Changed-From-To: pjd->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:14:18 UTC 2009 Responsible-Changed-Why: pjd is not actively working on GEOM at the moment. http://www.freebsd.org/cgi/query-pr.cgi?pr=81779 From linimon at FreeBSD.org Thu May 28 22:15:03 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu May 28 22:15:08 2009 Subject: kern/88601: [geli] geli cause kernel panic under heavy disk usage Message-ID: <200905282215.n4SMF2qf076400@freefall.freebsd.org> Synopsis: [geli] geli cause kernel panic under heavy disk usage Responsible-Changed-From-To: pjd->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:14:45 UTC 2009 Responsible-Changed-Why: pjd is not actively working on GEOM at the moment. http://www.freebsd.org/cgi/query-pr.cgi?pr=88601 From linimon at FreeBSD.org Thu May 28 22:15:30 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu May 28 22:15:37 2009 Subject: kern/113885: [gmirror] [patch] improved gmirror balance algorithm Message-ID: <200905282215.n4SMFUlj076452@freefall.freebsd.org> Synopsis: [gmirror] [patch] improved gmirror balance algorithm Responsible-Changed-From-To: pjd->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:15:15 UTC 2009 Responsible-Changed-Why: pjd is not actively working on GEOM at the moment. http://www.freebsd.org/cgi/query-pr.cgi?pr=113885 From linimon at FreeBSD.org Thu May 28 22:15:54 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu May 28 22:16:00 2009 Subject: kern/115856: [geli] ZFS thought it was degraded when it should have been faulted Message-ID: <200905282215.n4SMFrdU076501@freefall.freebsd.org> Synopsis: [geli] ZFS thought it was degraded when it should have been faulted Responsible-Changed-From-To: pjd->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:15:43 UTC 2009 Responsible-Changed-Why: pjd is not actively working on GEOM at the moment. http://www.freebsd.org/cgi/query-pr.cgi?pr=115856 From linimon at FreeBSD.org Thu May 28 22:16:40 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu May 28 22:16:47 2009 Subject: kern/120091: [geom] [geli] [gjournal] geli does not prompt for password on /dev/concat/XXX.eli.journal Message-ID: <200905282216.n4SMGeNM076555@freefall.freebsd.org> Synopsis: [geom] [geli] [gjournal] geli does not prompt for password on /dev/concat/XXX.eli.journal State-Changed-From-To: feedback->open State-Changed-By: linimon State-Changed-When: Thu May 28 22:16:01 UTC 2009 State-Changed-Why: Note that feedback was received some time ago. Responsible-Changed-From-To: pjd->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:16:01 UTC 2009 Responsible-Changed-Why: pjd is not actively working on GEOM at the moment. http://www.freebsd.org/cgi/query-pr.cgi?pr=120091 From linimon at FreeBSD.org Thu May 28 22:16:58 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu May 28 22:17:06 2009 Subject: kern/121481: [gmirror] data rot on disk with gmirror Message-ID: <200905282216.n4SMGvUi076605@freefall.freebsd.org> Synopsis: [gmirror] data rot on disk with gmirror Responsible-Changed-From-To: pjd->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:16:48 UTC 2009 Responsible-Changed-Why: pjd is not actively working on GEOM at the moment. http://www.freebsd.org/cgi/query-pr.cgi?pr=121481 From linimon at FreeBSD.org Thu May 28 22:17:15 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu May 28 22:17:22 2009 Subject: kern/122738: [geom] gmirror list "losts consumers" after gmirror deactivate command Message-ID: <200905282217.n4SMHFXM076657@freefall.freebsd.org> Synopsis: [geom] gmirror list "losts consumers" after gmirror deactivate command Responsible-Changed-From-To: pjd->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:17:06 UTC 2009 Responsible-Changed-Why: pjd is not actively working on GEOM at the moment. http://www.freebsd.org/cgi/query-pr.cgi?pr=122738 From linimon at FreeBSD.org Thu May 28 22:18:58 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu May 28 22:19:05 2009 Subject: docs/130548: [patch] gjournal(8) man page is missing sysctls Message-ID: <200905282218.n4SMIw9e076730@freefall.freebsd.org> Synopsis: [patch] gjournal(8) man page is missing sysctls Responsible-Changed-From-To: pjd->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 28 22:17:23 UTC 2009 Responsible-Changed-Why: pjd is not actively working on GEOM at the moment. http://www.freebsd.org/cgi/query-pr.cgi?pr=130548 From dfilter at FreeBSD.ORG Fri May 29 19:40:07 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Fri May 29 19:40:13 2009 Subject: kern/116896: commit references a PR Message-ID: <200905291940.n4TJe6Ar093459@freefall.freebsd.org> The following reply was made to PR kern/116896; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/116896: commit references a PR Date: Fri, 29 May 2009 19:37:26 +0000 (UTC) Author: lulf Date: Fri May 29 19:37:17 2009 New Revision: 193053 URL: http://svn.freebsd.org/changeset/base/193053 Log: MFC r179097: - Assert that we don't send new provider event for a provider which has G_PF_WITHER flag set. - Fix typo in assertion condition (sorry, but I forgot who report that). MFC r179151: Force commit to note, that the typo in KASSERT() was: PR: kern/116896 Reported by: VANHULLEBUS Yvan Modified: stable/7/sys/ (props changed) stable/7/sys/contrib/pf/ (props changed) stable/7/sys/dev/ath/ath_hal/ (props changed) stable/7/sys/dev/cxgb/ (props changed) stable/7/sys/geom/geom_subr.c Modified: stable/7/sys/geom/geom_subr.c ============================================================================== --- stable/7/sys/geom/geom_subr.c Fri May 29 19:27:52 2009 (r193052) +++ stable/7/sys/geom/geom_subr.c Fri May 29 19:37:17 2009 (r193053) @@ -531,6 +531,8 @@ g_new_provider_event(void *arg, int flag return; pp = arg; G_VALID_PROVIDER(pp); + KASSERT(!(pp->flags & G_PF_WITHER), + ("g_new_provider_event but withered")); LIST_FOREACH(mp, &g_classes, class) { if (mp->taste == NULL) continue; @@ -620,7 +622,7 @@ g_destroy_provider(struct g_provider *pp ("g_destroy_provider but attached")); KASSERT (pp->acr == 0, ("g_destroy_provider with acr")); KASSERT (pp->acw == 0, ("g_destroy_provider with acw")); - KASSERT (pp->acw == 0, ("g_destroy_provider with ace")); + KASSERT (pp->ace == 0, ("g_destroy_provider with ace")); g_cancel_event(pp); LIST_REMOVE(pp, provider); gp = pp->geom; _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From lists at jnielsen.net Sun May 31 01:48:02 2009 From: lists at jnielsen.net (John Nielsen) Date: Sun May 31 01:48:07 2009 Subject: FreeBSD on USB drive for a MacBook Pro Message-ID: <200905302136.49369.lists@jnielsen.net> I'm looking for advice and/or pointers. I have an Intel-based MacBook Pro and I would like to use a USB thumb drive to be able to boot FreeBSD on it. Some questions: 1) Is this even possible? I've read that you _can_ boot Mac OS X from a USB hard drive on a new MacBook but I'm not sure if the same goes for non-Mac OSen or thumb drives. 2) What steps should I take to partition the thing? What boot code should I use and where should it live? I'm planning to do a manual installation in any event. 3) If I manage to get 1 and 2 sorted out, will I be able to boot the same thumb drive on a regular PC? Will any additional steps be necessary? 4) Just to be contrary, I'd also like to use GELI (if possible) for everything but /boot. Does needing an extra /boot partition change anything? I'll be doing some experimenting, but if some things are already known (not) to work I'd like to start with as much info as possible. Thanks, JN From wojtek at wojtek.tensor.gdynia.pl Sun May 31 08:33:07 2009 From: wojtek at wojtek.tensor.gdynia.pl (Wojciech Puchar) Date: Sun May 31 08:33:13 2009 Subject: FreeBSD on USB drive for a MacBook Pro In-Reply-To: <200905302136.49369.lists@jnielsen.net> References: <200905302136.49369.lists@jnielsen.net> Message-ID: > > 4) Just to be contrary, I'd also like to use GELI (if possible) for > everything but /boot. Does needing an extra /boot partition change > anything? Actually you can't create /boot partition, but something else like /b and link /boot to /b/boot bootloader subsystem requires that things are in /boot subdirectory on bootpartition. make /boot partition a, encrypted partition as d and add in loader.conf vfs.root.mountfrom="ufs:da0d.eli" if you do this and not forget to add -b in geli init everything will just work. From utisoft at googlemail.com Sun May 31 08:34:26 2009 From: utisoft at googlemail.com (Chris Rees) Date: Sun May 31 08:34:32 2009 Subject: FreeBSD on USB drive for a MacBook Pro In-Reply-To: <200905302136.49369.lists@jnielsen.net> References: <200905302136.49369.lists@jnielsen.net> Message-ID: 2009/5/31 John Nielsen : > I'm looking for advice and/or pointers. I have an Intel-based MacBook Pro > and I would like to use a USB thumb drive to be able to boot FreeBSD on > it. Some questions: > > 1) Is this even possible? I've read that you _can_ boot Mac OS X from a > USB hard drive on a new MacBook but I'm not sure if the same goes for > non-Mac OSen or thumb drives. Yes. It is possible; as long as you can fit it on. The EFI is quite capable of handling USB sticks. > 2) What steps should I take to partition the thing? What boot code should > I use and where should it live? I'm planning to do a manual installation > in any event. Use Disk Utility, and use GPT layout, as long as you don't care about booting then stick on PCs. > 3) If I manage to get 1 and 2 sorted out, will I be able to boot the same > thumb drive on a regular PC? Will any additional steps be necessary? See above. > 4) Just to be contrary, I'd also like to use GELI (if possible) for > everything but /boot. Does needing an extra /boot partition change > anything? Doubt it, that shouldn't be a problem. See http://www.slax.org/forum.php?action=view&parentID=14468 > I'll be doing some experimenting, but if some things are already known > (not) to work I'd like to start with as much info as possible. > > Thanks, > > JN Good luck. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list?