From owner-freebsd-current@FreeBSD.ORG Mon Nov 2 20:37:50 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F04831065695 for ; Mon, 2 Nov 2009 20:37:50 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (hergotha.csail.mit.edu [66.92.79.170]) by mx1.freebsd.org (Postfix) with ESMTP id 826E58FC2F for ; Mon, 2 Nov 2009 20:37:50 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.3/8.14.3) with ESMTP id nA2KbmBs031297; Mon, 2 Nov 2009 15:37:48 -0500 (EST) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.3/8.14.3/Submit) id nA2Kbm43031296; Mon, 2 Nov 2009 15:37:48 -0500 (EST) (envelope-from wollman) Date: Mon, 2 Nov 2009 15:37:48 -0500 (EST) From: Garrett Wollman Message-Id: <200911022037.nA2Kbm43031296@hergotha.csail.mit.edu> To: jh@sandstorm.net References: <4AEF317B.8030200@sandstorm.net> Organization: None X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hergotha.csail.mit.edu [127.0.0.1]); Mon, 02 Nov 2009 15:37:48 -0500 (EST) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on hergotha.csail.mit.edu X-Mailman-Approved-At: Mon, 02 Nov 2009 21:13:50 +0000 Cc: current@freebsd.org Subject: Re: gnome, automounting, and ataraid don't get along well X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 20:37:51 -0000 In article <4AEF317B.8030200@sandstorm.net>, jh@sandstorm.net writes: >2) the devices in /dev/ufsid/ are associated with partitions on the adN >drives, not for the RAID they're assembled into (not sure whether ata or >ataraid or geom/glabel is responsible for this). This is a long-standing bug in ataraid. It should not be possible to open the individual members of a RAID set for writing, and the existence of the ataraid should spoil other consumers of the individual disk providers. (The same thing happens with regular UFS labels. I think the actual problem is that ataraid works behind GEOM's back, but doesn't withdraw the disk providers so GEOM thinks they are separate devices.) The only workaround that I have found is to disable the poor-man's-RAID and use gmirror instead. In general, having used both ataraid and gmirror systems since 5.x, my impression is that gmirror works better and is more manageable. -GAWollman