What on earth is all this %20 crap at the end of the GUID? (newfs?)
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 signature.asc Description: This is a digitally signed message part
Re: What on earth is all this %20 crap at the end of the GUID? (newfs?)
On 04/29/2014 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 I'm guessing it is picking up spaces from a physical ID on your disk from /sys/geom/label/g_label_disk_ident.c kern.geom.label.disk_ident.enable=0 in /boot/loader.conf will ignore that class. It was added in 10 and only shows up with certain devices. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What on earth is all this %20 crap at the end of the GUID? (newfs?)
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? -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: What on earth is all this %20 crap at the end of the GUID? (newfs?)
On Tue, Apr 29, 2014 at 8:30 PM, Allan Jude free...@allanjude.com 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
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 free...@allanjude.com 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. 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 - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV UTF-8: for when a ' just won\342\200\231t do. signature.asc Description: This is a digitally signed message part.
