Re: What on earth is all this %20 crap at the end of the GUID? (newfs?)

On Tuesday 29 April 2014 20:52:30 Alan Somers wrote:
> On Tue, Apr 29, 2014 at 8:30 PM, Allan Jude <freebsd_at_allanjude.com> wrote:
> > On 2014-04-29 19:51, Sean Bruno wrote:
> >> Created a simple partition:
> >>  root_at_:~ # gpart create -s gpt da11
> >> 
> >> da11 created
> >> root_at_:~ # gpart add -t freebsd-ufs da11
> >> da11p1 added
> >> root_at_:~ # gpart show da11
> >> =>        40  7814037088  da11  GPT  (3.6T)
> >> 
> >>           40  7814037088     1  freebsd-ufs  (3.6T)
> >> 
> >> root_at_:~ #
> >> 
> >> 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.

In this particular case, it's a modified ciss driver.  If memory serves, ciss 
pads its cam ident strings with spaces and that's showing up here.

FWIW, this is usually why I rm -rf /dev/gptid /dev/diskid before doing an 
import. I don't usually want the synthetic names in there.

-Peter
-- 
Peter Wemm - peter_at_wemm.org; peter_at_FreeBSD.org; peter_at_yahoo-inc.com; KI6FJV
UTF-8: for when a ' just won\342\200\231t do.