From owner-freebsd-geom@FreeBSD.ORG Sun Dec 14 00:17:24 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD04C1065670 for ; Sun, 14 Dec 2008 00:17:24 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id 89B868FC12 for ; Sun, 14 Dec 2008 00:17:24 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) Received: by an-out-0708.google.com with SMTP id c2so735144anc.13 for ; Sat, 13 Dec 2008 16:17:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=7rbePJ1R00jLrvKLYIIo/QYCL+znCIu8BYMQ0iVcaN0=; b=tfnRLWfvxFmFQkjJm2+dnj+aO20y1T+RVKHmhpFyJzCjL5NmofTqOnHKltvxtG6YIp YJkPuFBW3abodw5nV0Cwl0yDwDBcDBQH/cSkKQeRSgPwCkl5Efo4C8kf9dki+mWJD/Wj REv1t6zSK0Zes5ixaxB6ev9QpYtllKMrLf19A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=eTtKXQ6sJTEv1N01dPI7JVtjsI7DBOPW6dJCXsa15tRau6a03lIZOzdAJLeG4IV+Po m+kJ0IgBkyBdt572Vtp5BL7Io5HBpcqMcMiSneSbhMK6ZFdbzmznRWdBM5uf8/5R9Lai MW7JUNPts/R20bkAe5p5VOyc34yNLALeI1XgM= Received: by 10.101.68.19 with SMTP id v19mr3779120ank.58.1229213843346; Sat, 13 Dec 2008 16:17:23 -0800 (PST) Received: by 10.100.210.20 with HTTP; Sat, 13 Dec 2008 16:17:23 -0800 (PST) Message-ID: <917871cf0812131617m4dff5295xe1eeb6d83a568fe@mail.gmail.com> Date: Sun, 14 Dec 2008 01:17:23 +0100 From: "Ulf Lilleengen" To: oxy@field.hu In-Reply-To: <3934.79.122.6.53.1229199747.squirrel@webmail.field.hu> MIME-Version: 1.0 References: <20081212155023.GA82667@keira.kiwi-computer.com> <917871cf0812130559r6d423688q57287dd765d6edf4@mail.gmail.com> <3934.79.122.6.53.1229199747.squirrel@webmail.field.hu> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Michael Jung , freebsd-geom@freebsd.org Subject: Re: Encrypting raid5 volume with geli X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2008 00:17:24 -0000 On Sat, Dec 13, 2008 at 9:22 PM, wrote: > > as i read it seems that it's useless for sync the raid after initing, i > have no chance to encrypt it with geli, am i right? As Rick says, you can try to apply the patch itself. You should just have to rebuild and reinstall src/sbin/geom for it to take effect. If not, I'm planning to MFC it pretty soon anyway. -- Ulf Lilleengen From owner-freebsd-geom@FreeBSD.ORG Sun Dec 14 02:07:29 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CE691065672 for ; Sun, 14 Dec 2008 02:07:29 +0000 (UTC) (envelope-from mikej@paymentallianceintl.com) Received: from mx2.confluenttech.com (mx2.confluentasp.com [216.26.153.14]) by mx1.freebsd.org (Postfix) with ESMTP id 0A5F68FC12 for ; Sun, 14 Dec 2008 02:07:28 +0000 (UTC) (envelope-from mikej@paymentallianceintl.com) Received: from calvin.pai.local (calvin.pai.local [10.0.6.33]) by mx2.confluenttech.com (8.14.1/8.13.8) with ESMTP id mBE27KVa090226; Sat, 13 Dec 2008 21:07:20 -0500 (EST) (envelope-from mikej@paymentallianceintl.com) Authentication-Results: mx2.confluenttech.com from=mikej@paymentallianceintl.com; sender-id=neutral; spf=neutral X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325 Content-Class: urn:content-classes:message MIME-Version: 1.0 Date: Sat, 13 Dec 2008 21:07:15 -0500 Message-ID: In-Reply-To: <917871cf0812130559r6d423688q57287dd765d6edf4@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Encrypting raid5 volume with geli thread-index: AcldKyHy2JmlnXAqRrOoAUbv19RoOwAYie1g References: <20081212155023.GA82667@keira.kiwi-computer.com> <917871cf0812130559r6d423688q57287dd765d6edf4@mail.gmail.com> From: "Michael Jung" Importance: normal To: "Ulf Lilleengen" Priority: normal Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-geom@freebsd.org Subject: RE: Encrypting raid5 volume with geli X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2008 02:07:29 -0000 From: Ulf Lilleengen [mailto:ulf.lilleengen@gmail.com] Sent: Saturday, December 13, 2008 8:59 AM To: Michael Jung Cc: freebsd-geom@freebsd.org Subject: Re: Encrypting raid5 volume with geli On Fri, Dec 12, 2008 at 5:00 PM, Michael Jung wrote: FreeBSD charon.confluentasp.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #2: Thu Sep 4 12:06:08 EDT 2008 In the interest of this thread I tried to duplicate the problem. I created: 10 drives: D d9 State: up /dev/da9 A: 0/17366 MB (0%) D d8 State: up /dev/da8 A: 0/17366 MB (0%) D d7 State: up /dev/da7 A: 0/17366 MB (0%) D d6 State: up /dev/da6 A: 0/17366 MB (0%) D d5 State: up /dev/da5 A: 0/17366 MB (0%) D d4 State: up /dev/da4 A: 0/17366 MB (0%) D d3 State: up /dev/da3 A: 0/17366 MB (0%) D d2 State: up /dev/da2 A: 0/17366 MB (0%) D d1 State: up /dev/da1 A: 0/17366 MB (0%) D d0 State: up /dev/da0 A: 0/17366 MB (0%) 1 volume: V test State: up Plexes: 1 Size: 152 GB 1 plex: P test.p0 R5 State: up Subdisks: 10 Size: 152 GB 10 subdisks: S test.p0.s9 State: up D: d9 Size: 16 GB S test.p0.s8 State: up D: d8 Size: 16 GB S test.p0.s7 State: up D: d7 Size: 16 GB S test.p0.s6 State: up D: d6 Size: 16 GB S test.p0.s5 State: up D: d5 Size: 16 GB S test.p0.s4 State: up D: d4 Size: 16 GB S test.p0.s3 State: up D: d3 Size: 16 GB S test.p0.s2 State: up D: d2 Size: 16 GB S test.p0.s1 State: up D: d1 Size: 16 GB S test.p0.s0 State: up D: d0 Size: 16 GB Which I can newfs and mount (root@charon) /etc# mount /dev/gvinum/test /mnt (root@charon) /etc# df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad4s1a 357G 119G 209G 36% / devfs 1.0K 1.0K 0B 100% /dev 172.0.255.28:/data/unix 1.3T 643G 559G 54% /nas1 /dev/gvinum/test 148G 4.0K 136G 0% /mnt But with /dev/gvinum/test unmounted if I try: (root@charon) /etc# geli init -P -K /root/test.key /dev/gvinum/test geli: Cannot store metadata on /dev/gvinum/test: Operation not permitted. (root@charon) /etc# My random file was created like dd if=/dev/random of=/root/test.key bs=64 count=1 I use GELI at home with no trouble, although not with a gvinum volume. Hello, When I tried this myself, I also got the EPERM error in return. I though this was very strange. I went through the gvinum code today, and put debugging prints everywhere, but everything looked fine, and it was only raid5 volumes that failed. Then I saw that the EPERM error came from the underlying providers of geom (more specifially from the read requests to the parity stripes etc), so I was starting to suspect that it was not a gvinum error. But still, I was able to write/read from the disks from outside of gvinum! Then, I discovered in geom userland code that it opens the disk where metadata should be written in write only mode. Then I discovered the reason: gvinum tries to write to the stripe in question, but has to read back the parity data from one of the other stripes. But, they are opened O_WRONLY, so the request fails. I tried opening the device as O_RDWR, and everything is find. Phew :) You can bet I was frustrated I hope to commit the attached change in the near future. -- Ulf Lilleengen I+++++++++++++++++++++++++++++++++ 7.1-PRERELEASE #0: Sat Dec 13 15:09:38 EST 2008 I just cvsup and applied your patch, now: (root@charon) /etc# geli init -P -K /root/test.key /dev/gvinum/test (root@charon) /etc# geli attach -p -k /root/test.key /dev/gvinum/test (root@charon) /etc# newfs /dev/gvinum/test.eli /dev/gvinum/test.eli: 121564.2MB (248963480 sectors) block size 16384, fragment size 2048 using 662 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272,........... (root@charon) /etc# mount /dev/gvinum/test.eli /mnt (root@charon) /etc# df -h /mnt Filesystem Size Used Avail Capacity Mounted on /dev/gvinum/test.eli 115G 4.0K 106G 0% /mnt (root@charon) /etc# I exercise it some but patch looks good! --mikej 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 owner-freebsd-geom@FreeBSD.ORG Sun Dec 14 13:42:16 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 123A11065672 for ; Sun, 14 Dec 2008 13:42:15 +0000 (UTC) (envelope-from oxy@field.hu) Received: from green.field.hu (green.field.hu [217.20.130.28]) by mx1.freebsd.org (Postfix) with ESMTP id 89BAA8FC08 for ; Sun, 14 Dec 2008 13:42:15 +0000 (UTC) (envelope-from oxy@field.hu) Received: from localhost (green.field.hu [217.20.130.28]) by green.field.hu (Postfix) with ESMTP id 8F1E5B24BB; Sun, 14 Dec 2008 14:42:11 +0100 (CET) X-Virus-Scanned: by Amavisd-new (Spamassassin+Razor2+Pyzor+DCC+Bayes db, Clamd Antivirus) at field.hu Received: from green.field.hu ([217.20.130.28]) by localhost (green.field.hu [217.20.130.28]) (amavisd-new, port 10024) with ESMTP id qwrK9qkunmto; Sun, 14 Dec 2008 14:42:07 +0100 (CET) Received: from [192.168.1.2] (catv4E5CB4D6.pool.t-online.hu [78.92.180.214]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by green.field.hu (Postfix) with ESMTPSA id 67E94B24B3; Sun, 14 Dec 2008 14:42:07 +0100 (CET) Message-ID: <49450D2B.9000304@field.hu> Date: Sun, 14 Dec 2008 14:42:03 +0100 From: oxy User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: rick-freebsd2008@kiwi-computer.com References: <20081212155023.GA82667@keira.kiwi-computer.com> <917871cf0812130559r6d423688q57287dd765d6edf4@mail.gmail.com> <3934.79.122.6.53.1229199747.squirrel@webmail.field.hu> <20081213212835.GA99136@keira.kiwi-computer.com> In-Reply-To: <20081213212835.GA99136@keira.kiwi-computer.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-geom@freebsd.org Subject: Re: Encrypting raid5 volume with geli X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2008 13:42:16 -0000 I am using 7.0-RELEASE can you guys give me a link where can I download the patch? thank you Rick C. Petty írta: > On Sat, Dec 13, 2008 at 09:22:27PM +0100, oxy@field.hu wrote: > >> as i read it seems that it's useless for sync the raid after initing, i >> > > Not sure what you mean here. RAID5 sync after creation is pretty typical. > I think it many cases it's unnecessary, but the current gvinum code does > perform a sync-after-create for raid5. > > >> have no chance to encrypt it with geli, am i right? >> > > With the patch lulf@ just committed, you should be able to geli a raid5 > volume under gvinum. You may have to wait for it to be MFC'd if you're not > using HEAD (FreeBSD-CURRENT). You could also apply his patch to your > source code and rebuild from /usr/src/sbin/gvinum/ and it should work for > you. > > -- Rick C. Petty > _______________________________________________ > freebsd-geom@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-geom > To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" > From owner-freebsd-geom@FreeBSD.ORG Sun Dec 14 18:36:52 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72A28106564A for ; Sun, 14 Dec 2008 18:36:52 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) Received: from mta1.eidsiva.net (mta1.eidsiva.net [82.147.40.130]) by mx1.freebsd.org (Postfix) with ESMTP id F29248FC08 for ; Sun, 14 Dec 2008 18:36:51 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiVPAFnaRElX+AYSPGdsb2JhbACJNIMMhwkBAQEBNa1gi2iCfg X-IronPort-AV: E=Sophos;i="4.36,219,1228086000"; d="scan'208";a="16406408" Received: from 18.6.erx-lhm.eidsiva.net (HELO @) ([87.248.6.18]) by mtc1.eidsiva.net with ESMTP; 14 Dec 2008 19:06:57 +0100 Date: Sun, 14 Dec 2008 18:06:59 +0100 From: Ulf Lilleengen To: oxy Message-ID: <20081214170659.GA12437@nobby> References: <20081212155023.GA82667@keira.kiwi-computer.com> <917871cf0812130559r6d423688q57287dd765d6edf4@mail.gmail.com> <3934.79.122.6.53.1229199747.squirrel@webmail.field.hu> <20081213212835.GA99136@keira.kiwi-computer.com> <49450D2B.9000304@field.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49450D2B.9000304@field.hu> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: rick-freebsd2008@kiwi-computer.com, freebsd-geom@freebsd.org Subject: Re: Encrypting raid5 volume with geli X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2008 18:36:52 -0000 On Sun, Dec 14, 2008 at 02:42:03PM +0100, oxy wrote: > I am using 7.0-RELEASE > can you guys give me a link where can I download the patch? > thank you Here: http://people.freebsd.org/~lulf/readwritefix.diff -- Ulf Lilleengen From owner-freebsd-geom@FreeBSD.ORG Sun Dec 14 20:17:28 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF1BE1065675 for ; Sun, 14 Dec 2008 20:17:28 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id A84A98FC13 for ; Sun, 14 Dec 2008 20:17:28 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (eeyi3hifoa47t5b2@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id mBEJuoqo003537; Sun, 14 Dec 2008 11:56:50 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id mBEJuoPp003536; Sun, 14 Dec 2008 11:56:50 -0800 (PST) (envelope-from jmg) Date: Sun, 14 Dec 2008 11:56:49 -0800 From: John-Mark Gurney To: Ulf Lilleengen Message-ID: <20081214195649.GK34842@funkthat.com> Mail-Followup-To: Ulf Lilleengen , Michael Jung , freebsd-geom@freebsd.org References: <20081212155023.GA82667@keira.kiwi-computer.com> <917871cf0812130559r6d423688q57287dd765d6edf4@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <917871cf0812130559r6d423688q57287dd765d6edf4@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hydrogen.funkthat.com [127.0.0.1]); Sun, 14 Dec 2008 11:56:50 -0800 (PST) Cc: Michael Jung , freebsd-geom@freebsd.org Subject: Re: Encrypting raid5 volume with geli X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2008 20:17:29 -0000 Ulf Lilleengen wrote this message on Sat, Dec 13, 2008 at 14:59 +0100: > Then, I discovered in geom userland code that it opens the disk where > metadata should be written in write only mode. Then I discovered the reason: > gvinum tries to write to the stripe in question, but has to read back the > parity data from one of the other stripes. But, they are opened O_WRONLY, so > the request fails. I tried opening the device as O_RDWR, and everything is > find. Isn't this a bug in gvinum that it lets a disk be opened in O_WRONLY, when it needs read permissions? Shouldn't it add the read permission to it's provider open, and let the underlying fd still be O_WRONLY (so the OS will prevent any reads) or it should be documented in the gvinum man page that raid5 volumes cannot be opened in O_WRONLY mode.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-geom@FreeBSD.ORG Sun Dec 14 22:59:15 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0845C106564A for ; Sun, 14 Dec 2008 22:59:15 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) Received: from mta2.eidsiva.net (mta2.eidsiva.net [82.147.40.138]) by mx1.freebsd.org (Postfix) with ESMTP id 8C75D8FC1C for ; Sun, 14 Dec 2008 22:59:14 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aj8sAEceRUlX+AYSPGdsb2JhbACMQIcJAQEBATWuGItQgn4 X-IronPort-AV: E=Sophos;i="4.36,220,1228086000"; d="diff'?scan'208";a="6698472" Received: from 18.6.erx-lhm.eidsiva.net (HELO @) ([87.248.6.18]) by mtc2.eidsiva.net with ESMTP; 14 Dec 2008 23:59:11 +0100 Date: Sun, 14 Dec 2008 22:59:13 +0100 From: Ulf Lilleengen To: John-Mark Gurney Message-ID: <20081214215913.GA3723@nobby> References: <20081212155023.GA82667@keira.kiwi-computer.com> <917871cf0812130559r6d423688q57287dd765d6edf4@mail.gmail.com> <20081214195649.GK34842@funkthat.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="huq684BweRXVnRxX" Content-Disposition: inline In-Reply-To: <20081214195649.GK34842@funkthat.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Michael Jung , freebsd-geom@freebsd.org Subject: Re: Encrypting raid5 volume with geli X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2008 22:59:15 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Dec 14, 2008 at 11:56:49AM -0800, John-Mark Gurney wrote: > Ulf Lilleengen wrote this message on Sat, Dec 13, 2008 at 14:59 +0100: > > Then, I discovered in geom userland code that it opens the disk where > > metadata should be written in write only mode. Then I discovered the reason: > > gvinum tries to write to the stripe in question, but has to read back the > > parity data from one of the other stripes. But, they are opened O_WRONLY, so > > the request fails. I tried opening the device as O_RDWR, and everything is > > find. > > Isn't this a bug in gvinum that it lets a disk be opened in O_WRONLY, > when it needs read permissions? Shouldn't it add the read permission > to it's provider open, and let the underlying fd still be O_WRONLY (so > the OS will prevent any reads) or it should be documented in the > gvinum man page that raid5 volumes cannot be opened in O_WRONLY mode.. > Yes, I agree. Michael, could you try the attached patch? It should fix the issue within gvinum itself. The previous change will have to be reverted too. -- Ulf Lilleengen --huq684BweRXVnRxX-- From owner-freebsd-geom@FreeBSD.ORG Mon Dec 15 04:50:38 2008 Return-Path: Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A55FE1065675; Mon, 15 Dec 2008 04:50:38 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 545AE8FC08; Mon, 15 Dec 2008 04:50:38 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBF4ocVf074794; Mon, 15 Dec 2008 04:50:38 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBF4ocSe074784; Mon, 15 Dec 2008 04:50:38 GMT (envelope-from linimon) Date: Mon, 15 Dec 2008 04:50:38 GMT Message-Id: <200812150450.mBF4ocSe074784@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-geom@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/129645: gjournal(8): GEOM_JOURNAL causes system to fail to bood due to a GEOM Timeout problem if the Journals and Data are on storage provided by separate device drivers. X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 04:50:38 -0000 Old Synopsis: GEOM_JOURNAL causes system to fail to bood due to a GEOM Timeout problem if the Journals and Data are on storage provided by separate device drivers. New Synopsis: gjournal(8): GEOM_JOURNAL causes system to fail to bood due to a GEOM Timeout problem if the Journals and Data are on storage provided by separate device drivers. Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Mon Dec 15 04:49:42 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=129645 From owner-freebsd-geom@FreeBSD.ORG Mon Dec 15 10:56:25 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90D271065670 for ; Mon, 15 Dec 2008 10:56:25 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C8CA48FC16 for ; Mon, 15 Dec 2008 10:56:24 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA13951; Mon, 15 Dec 2008 12:55:43 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <494637A3.9080807@icyb.net.ua> Date: Mon, 15 Dec 2008 12:55:31 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: vadim_nuclight@mail.ru References: <4939287C.3020208@icyb.net.ua> In-Reply-To: Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org Subject: Re: partition covering the whole slice [repost] X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 10:56:25 -0000 on 08/12/2008 14:30 Vadim Goncharov said the following: > Yes, of course. You should not intermix using glabel(8) utilizing /dev/ufs > (via tunefs) and bsdlabel partition starting from offset 0. This is because > glabel can't distinguish is that slice or partition - with offset 0 superblock > will be at the same position. > > You can try to erase bsdlabel completely (if this is not your boot partition) > from the slice and use filesystem directly from the slice. This will not affect > mount as you're already using labels. > > The other way will require shrinking-then-moving partition on the disk and > editing disklabel, better done with newfs(8). Vadim, thanks a lot for the explanation and the advice. I used gpart destroy to remove bsdlabel and now I have filesystems covering the whole slices. This works well. -- Andriy Gapon From owner-freebsd-geom@FreeBSD.ORG Mon Dec 15 11:06:52 2008 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 753E11065675 for ; Mon, 15 Dec 2008 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 67CC58FC1A for ; Mon, 15 Dec 2008 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBFB6qPr004331 for ; Mon, 15 Dec 2008 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBFB6pFm004327 for freebsd-geom@FreeBSD.org; Mon, 15 Dec 2008 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Dec 2008 11:06:51 GMT Message-Id: <200812151106.mBFB6pFm004327@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 11:06:52 -0000 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/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 kern/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 that 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 f 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] GBDE-encrypted swap causes panic at shutdown 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 41 problems total. From owner-freebsd-geom@FreeBSD.ORG Mon Dec 15 11:51:29 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 705EC1065670 for ; Mon, 15 Dec 2008 11:51:29 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8DA098FC0C for ; Mon, 15 Dec 2008 11:51:28 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA16462 for ; Mon, 15 Dec 2008 13:51:26 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <494644BE.8000307@icyb.net.ua> Date: Mon, 15 Dec 2008 13:51:26 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: gpart: mark slice active X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 11:51:29 -0000 How do I mark a slice active/inactive with gpart? -- Andriy Gapon From owner-freebsd-geom@FreeBSD.ORG Mon Dec 15 12:36:03 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 721C41065673 for ; Mon, 15 Dec 2008 12:36:03 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 2C0A08FC08 for ; Mon, 15 Dec 2008 12:36:02 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LCCg3-0006Vr-TK for freebsd-geom@freebsd.org; Mon, 15 Dec 2008 12:35:59 +0000 Received: from 195.208.174.178 ([195.208.174.178]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Dec 2008 12:35:59 +0000 Received: from vadim_nuclight by 195.208.174.178 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Dec 2008 12:35:59 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-geom@freebsd.org From: Vadim Goncharov Date: Mon, 15 Dec 2008 12:35:51 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 27 Message-ID: References: <4939287C.3020208@icyb.net.ua> <494637A3.9080807@icyb.net.ua> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 195.208.174.178 X-Comment-To: Andriy Gapon User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: partition covering the whole slice [repost] X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 12:36:03 -0000 Hi Andriy Gapon! On Mon, 15 Dec 2008 12:55:31 +0200; Andriy Gapon wrote about 'Re: partition covering the whole slice [repost]': >> Yes, of course. You should not intermix using glabel(8) utilizing /dev/ufs >> (via tunefs) and bsdlabel partition starting from offset 0. This is because >> glabel can't distinguish is that slice or partition - with offset 0 superblock >> will be at the same position. Also, that's why bsdlabel(8) creates partition 'a' with offset 16 by default. >> You can try to erase bsdlabel completely (if this is not your boot partition) >> from the slice and use filesystem directly from the slice. This will not affect >> mount as you're already using labels. >> >> The other way will require shrinking-then-moving partition on the disk and >> editing disklabel, better done with newfs(8). > thanks a lot for the explanation and the advice. > I used gpart destroy to remove bsdlabel and now I have filesystems > covering the whole slices. This works well. Also, check that your fsck doesn't complain about that setup (can't automatically determine how to check it). -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-geom@FreeBSD.ORG Mon Dec 15 23:55:07 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 992F91065676 for ; Mon, 15 Dec 2008 23:55:07 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout011.mac.com (asmtpout011.mac.com [17.148.16.86]) by mx1.freebsd.org (Postfix) with ESMTP id 850968FC1C for ; Mon, 15 Dec 2008 23:55:07 +0000 (UTC) (envelope-from xcllnt@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed Received: from [172.24.104.81] (natint3.juniper.net [66.129.224.36]) by asmtp011.mac.com (Sun Java(tm) System Messaging Server 6.3-7.03 (built Aug 7 2008; 32bit)) with ESMTPSA id <0KBX00IUVZRO5A30@asmtp011.mac.com> for freebsd-geom@freebsd.org; Mon, 15 Dec 2008 15:55:00 -0800 (PST) Message-id: <03FF0C63-26EA-4A1D-8FDE-A699A3D8DBD9@mac.com> From: Marcel Moolenaar To: Andriy Gapon In-reply-to: <494644BE.8000307@icyb.net.ua> Date: Mon, 15 Dec 2008 15:54:59 -0800 References: <494644BE.8000307@icyb.net.ua> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-geom@freebsd.org Subject: Re: gpart: mark slice active X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 23:55:07 -0000 On Dec 15, 2008, at 3:51 AM, Andriy Gapon wrote: > > How do I mark a slice active/inactive with gpart? gpart set -a active -i FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-geom@FreeBSD.ORG Tue Dec 16 03:09:24 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBAE1106564A for ; Tue, 16 Dec 2008 03:09:24 +0000 (UTC) (envelope-from gfritz@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id 8A9228FC13 for ; Tue, 16 Dec 2008 03:09:24 +0000 (UTC) (envelope-from gfritz@gmail.com) Received: by wa-out-1112.google.com with SMTP id m34so1452784wag.27 for ; Mon, 15 Dec 2008 19:09:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition:user-agent; bh=Ec6/BcRZaCpVIr6ai+A+h7CZNxA/VwGMCb3xc8YetsQ=; b=PmwkkqkXaD8CQv/qgE8cwNXuWp6er8VdRoD4OYr4bHRyc2aL5begFUMkwsqYq8Ssq3 PUGNNh9I9BSKuoIoVRQMqXY2OC65xn1m2FzmEVWHOao4I1txT1zw4yDZeq1by7SynUxM buRCvf4igFUuBTZciMAPfQ3m7Y+5k4sHBL/a0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; b=esSN8YuPiFD69B8gbVn49WBpMhCg1GpL0eoMig/S3OdjUzGxF9zBDDguFQze8EkKdj d81/9VPb7EMDUbjlIGoBi4dlK1EYRQYhs/E5MPltfabX+ZujR2cnFtmxvWCKSrluOCkp aJsm7kUnaKbNbifacTGypHiu8ufbw2XBV31TA= Received: by 10.114.124.1 with SMTP id w1mr5383603wac.132.1229395762592; Mon, 15 Dec 2008 18:49:22 -0800 (PST) Received: from dev.null (34-12-66-208.dsl.cust.wirelessbeehive.com [208.66.12.34]) by mx.google.com with ESMTPS id q18sm655980pog.9.2008.12.15.18.49.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 15 Dec 2008 18:49:22 -0800 (PST) Received: by dev.null (Postfix, from userid 1002) id 1E49587B42B; Mon, 15 Dec 2008 19:49:21 -0700 (MST) Date: Mon, 15 Dec 2008 19:49:21 -0700 From: Geoff Fritz To: freebsd-geom@freebsd.org Message-ID: <20081216024921.GC55072@dev.null> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Subject: GEOM_JOURNAL: Flush cache of concat/foo: error=19 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2008 03:09:24 -0000 I've been experiementing with a bunch of GEOM services lately, and I've got a really ugly patchwork of disk space that might be better off done with ZFS. Without going into insane detail, here's how the layers stack up: drives --> gmirror --> gconcat --> geli -> gjournal (The goal was to utilize a bunch of misc drives, have all of the used space have redundancy, and only need to provide a single password when the system boots.) So I've got this /dev/concat/foo.eli.journal device mounted as my root partition (I boot via USB stick, to test full-disk crypto), with options "rw,noatime,async". I'm seeing the error (mentioned in the subject) when I beat the tar out of the filesystem, followed by a healthy stack of "last message repeated...". I'm currently compiling openoffice.org, which is when I first noticed the errors. I've been unable to locate the meaning of error "19" from searching the archives or the sources (a few too many levels of function calls for me to sort through). What does the error mean, is it serious, and how do I prevent it? Thanks for any pointers. -- Geoff From owner-freebsd-geom@FreeBSD.ORG Tue Dec 16 04:06:37 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FE511065670 for ; Tue, 16 Dec 2008 04:06:37 +0000 (UTC) (envelope-from gfritz@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id D43A28FC1F for ; Tue, 16 Dec 2008 04:06:36 +0000 (UTC) (envelope-from gfritz@gmail.com) Received: by wa-out-1112.google.com with SMTP id m34so1463011wag.27 for ; Mon, 15 Dec 2008 20:06:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition:user-agent; bh=JBv/KwCY8Ky25Oyh0qCZXkATXFGZgEdvXme3wsNpt/g=; b=H4AmxCim06JmotSnPZfw+hN/Mag900RIhMFSckTDztdESeAO7f9JGO7CrweT8dKbzS 4PXMQ686GojCuMe2YE7Rq+mWGvNq/DrNG0toM7gdm0nflYFVseM8VW9Lfy1ZndajjVid CZS62QNzNka0uFzCtENlBqwC1neygpCkZ19Cs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; b=Tff7JgFQtwWaMMNW3IebCwVybOtrLQjZsWpsV9Bz4MWWcKwE1RfFmOzdYiFqPjpshw 3gvWUnXVs6VMBCd+sstSLgPftbUgXPdH8n+U79i12rx1cWYIYZbm+9yj6eAi/X/kDPAY /wLMGIXbX2263EM3P0+qY/mGtzvr5ei6wSh9w= Received: by 10.114.146.6 with SMTP id t6mr5415411wad.207.1229400396427; Mon, 15 Dec 2008 20:06:36 -0800 (PST) Received: from dev.null (34-12-66-208.dsl.cust.wirelessbeehive.com [208.66.12.34]) by mx.google.com with ESMTPS id z15sm784517pod.0.2008.12.15.20.06.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 15 Dec 2008 20:06:36 -0800 (PST) Received: by dev.null (Postfix, from userid 1002) id 2CA7087B42B; Mon, 15 Dec 2008 21:06:33 -0700 (MST) Date: Mon, 15 Dec 2008 21:06:33 -0700 From: Geoff Fritz To: freebsd-geom@freebsd.org Message-ID: <20081216040633.GA17495@dev.null> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Subject: GCACHE -- what's it for? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2008 04:06:37 -0000 I noticed the presence of the geom_cache module recently. Very little available in the archives on what it's used for. Found a post by pjd@ with a link to a tarball containing a man page: "The gcache utility is used for setting up a clean cache in front of the IDE controller on one disk." (btw, where do I post to get this man page included in the release? freebsd-doc? I'm running 7.1-RC1 and the man page is absent.) I set up a test device with it, and noticed that the disk did a lot of thrashing when it was being written to, moreso than normal. Is the purpose of this module to ensure that when the gcache provdider says the write was made it was in fact 100% written to the physical disk (or at least accepted by the next layer down)? Thanks for the info. -- Geoff From owner-freebsd-geom@FreeBSD.ORG Tue Dec 16 11:41:12 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1244106564A for ; Tue, 16 Dec 2008 11:41:12 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2FCB58FC1C for ; Tue, 16 Dec 2008 11:41:11 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA27780; Tue, 16 Dec 2008 13:41:07 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <494793D2.5070107@icyb.net.ua> Date: Tue, 16 Dec 2008 13:41:06 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: vadim_nuclight@mail.ru References: <4939287C.3020208@icyb.net.ua> <494637A3.9080807@icyb.net.ua> In-Reply-To: Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org Subject: Re: partition covering the whole slice [repost] X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2008 11:41:13 -0000 on 15/12/2008 14:35 Vadim Goncharov said the following: > Hi Andriy Gapon! > > On Mon, 15 Dec 2008 12:55:31 +0200; Andriy Gapon wrote about 'Re: partition covering the whole slice [repost]': > >>> Yes, of course. You should not intermix using glabel(8) utilizing /dev/ufs >>> (via tunefs) and bsdlabel partition starting from offset 0. This is because >>> glabel can't distinguish is that slice or partition - with offset 0 superblock >>> will be at the same position. > > Also, that's why bsdlabel(8) creates partition 'a' with offset 16 by default. But it seems that sysinstall doesn't, unfortunately. >>> You can try to erase bsdlabel completely (if this is not your boot partition) >>> from the slice and use filesystem directly from the slice. This will not affect >>> mount as you're already using labels. >>> >>> The other way will require shrinking-then-moving partition on the disk and >>> editing disklabel, better done with newfs(8). >> thanks a lot for the explanation and the advice. >> I used gpart destroy to remove bsdlabel and now I have filesystems >> covering the whole slices. This works well. > > Also, check that your fsck doesn't complain about that setup (can't > automatically determine how to check it). Yes, this happens indeed - whether I specify /dev/da0s1 or /dev/ufs/