From owner-freebsd-current@FreeBSD.ORG Sun Jul 5 09:15:03 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 222F7106564A for ; Sun, 5 Jul 2009 09:15:03 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id AB3DF8FC0A for ; Sun, 5 Jul 2009 09:15:02 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: by fxm18 with SMTP id 18so2706311fxm.43 for ; Sun, 05 Jul 2009 02:15:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=kQ0LbLccaqs/7akl+qOqXAa0ZtwsNuI1OjZJoUSNjvg=; b=uuRFcmCOxmA+ro1jvNC2/5qqJOgBizxQMFhpVgm23xfvyfAX7rdDitBys+Uneh+024 hG5s7FUd0A/WDGjOEFYdq7A9WEOWldCFCuWD08olotWQR6C7VU4dGl/xMYd4SuV9RLfg h4z9NBU0y7FCQTlfH8gsiAy6dlYHUgYUaTrqE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=NeAkKT8R+9t/qK9ReX7gWcp8jtnnB2BAKyjIHQ12lDRNWADVvMe+ZaWHXk1xqoIKKV 44RT7AouSw8ojMcYDpgQPlDNaUT7zw0tMgsO9h6IxLuIibrQfTanW9QuynJ05F4QPD7B Pc3Rt31Z/S+iQsqofJKuVYRWe3yaqmIDgS2CM= MIME-Version: 1.0 Received: by 10.239.137.84 with SMTP id k20mr262668hbk.21.1246783712798; Sun, 05 Jul 2009 01:48:32 -0700 (PDT) Date: Sun, 5 Jul 2009 08:48:32 +0000 Message-ID: From: "b. f." To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 05 Jul 2009 12:29:54 +0000 Cc: Subject: RFC: ATA to CAM integration patch (and gjournaled previuos nodes) 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: Sun, 05 Jul 2009 09:15:03 -0000 Alexander Motin wrote: >Harald Schmalzbauer wrote: >> I have a gournaled FS whoch lists it's consumer as ad12p6 >You mean gjournal has provider names hardcoded to it's meta data? It >could be a problem. If it detects it's parts freely, then it should not >notice the change. I just changed provider names for a gjournal'ed disk when my disks were reordered, and with the proper corresponding changes to fstab, there were no problems -- everything was mounted and loaded upon reboot without me having to make any other changes. However, if you used the "-h" option with "gjournal label" you may have to manually relabel. >> Otherwise I only use labels (ufs) for quiet some time, so I thought >> testing would be painless... >> Can I safely remove glabel from the unmounted fs and relabel the new >> device? >I don't very understand whet you mean by "safe"? Safe for what? He means, can he relabel the disks without losing any data on them? I think that the answer is yes, provided he doesn't do anything foolish -- like relabel an existing file system with journal and data on the same provider, while increasing the size of the journal, which would cause all data on the space allocated to the new journal to be lost. He may have to use the "-f" flag with "gjournal label", or issue "gjournal clear" before relabeling, and he may lose the last sector of the file system and anything on the journal, but that usually isn't of any consequence. In any event, unless he hardcoded his provider names, this probably isn't necessary. If it does prove to be necessary, it would be wise to back up any data just to be safe, and to experiment on a test provider first, before trying to relabel. b.