From owner-freebsd-current@FreeBSD.ORG Wed Apr 30 02:52:32 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8AD33AA5 for ; Wed, 30 Apr 2014 02:52:32 +0000 (UTC) Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 24FC119D0 for ; Wed, 30 Apr 2014 02:52:32 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id x13so1061857wgg.8 for ; Tue, 29 Apr 2014 19:52:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tuGdxDKhpbT4ZNNdVp9oGQwk/B5mHVBG5LrI/p6grzc=; b=dJ+S6f7vAM3gXUrr9hGNvbMiUav2oJGRx+p5arHYSRnTAeqLTuhng5eYHD4dDTS3Ln JEsysbbpMHuSHNwcB3bZdBxdwocAz76RG+V1KrSHRGGlt3Iur9V5lbd9UTfYihgUf0RR Ml22BQgcQBJB+AmLqrwdKSaKQRMUMkgR2+fWFJdwb4YJLXghCdiinfe+Q+17pjou1tmg 9yqyjk7XCozNUjUY0u8sRUADHdT7Dv8O38SgavTBsXp3ZjrQk+mij2mDPeIK3qVDNdxP B/pD93WCr2TtSSi9+BMNgmZjGp0oWNtpTX6vykgkPS1QGt8pGEb7VwlOBVa3muId8Ojt ZB1w== MIME-Version: 1.0 X-Received: by 10.180.14.72 with SMTP id n8mr1150903wic.53.1398826350345; Tue, 29 Apr 2014 19:52:30 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.194.168.130 with HTTP; Tue, 29 Apr 2014 19:52:30 -0700 (PDT) In-Reply-To: <5360605B.80605@allanjude.com> References: <1398815513.2019.50.camel@powernoodle.corp.yahoo.com> <5360605B.80605@allanjude.com> Date: Tue, 29 Apr 2014 20:52:30 -0600 X-Google-Sender-Auth: sIq5gBPReqok2GRrpCIk45W1Dag Message-ID: Subject: Re: What on earth is all this %20 crap at the end of the GUID? (newfs?) From: Alan Somers To: Allan Jude Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Wed, 30 Apr 2014 02:52:32 -0000 On Tue, Apr 29, 2014 at 8:30 PM, Allan Jude wrote: > On 2014-04-29 19:51, Sean Bruno wrote: >> Created a simple partition: >> >> root@:~ # gpart create -s gpt da11 >> da11 created >> root@:~ # gpart add -t freebsd-ufs da11 >> da11p1 added >> root@:~ # gpart show da11 >> => 40 7814037088 da11 GPT (3.6T) >> 40 7814037088 1 freebsd-ufs (3.6T) >> >> root@:~ # >> >> Then run a newfs and reboot the system. Upon reboot this is what I get? >> >> => 40 7814037088 da11 GPT (3.6T) >> 40 7814037088 1 freebsd-ufs (3.6T) >> => 40 7814037088 diskid/DISK-Z1Z0DQ73%20%20%20%20%20%20%20%20% >> 20%20%20%20 GPT (3.6T) >> 40 7814037088 >> 1 freebsd-ufs (3.6T) >> >> >> What is going on here? >> >> sean >> > > That is highly unusual, does your disk have a bunch of blank spaces in > its serial # or something? Not that unusual at all. In ATA and SCSI alike it's common for text fields to be defined as fixed length strings. I've seen many vendors pad their entries out with spaces; for some reason they're allergic to using NULLs. geom should probably be modified to strip trailing whitespace from the serial number. -Alan > > -- > Allan Jude >