re: port-amd64/51216: Can't create wedges on a large (3TB) disk, gpt is ok but dkctl gives an error message

[m33 <m33%tok715.net@localhost>]

The following reply was made to PR port-amd64/51216; it has been noted by GNATS.

From: m33 <m33%tok715.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost
Subject: re: port-amd64/51216: Can't create wedges on a large (3TB) disk, gpt
 is ok but dkctl gives an error message
Date: Mon, 06 Jun 2016 20:03:38 +0200

 Le 06-06-2016 19:15, matthew green a écrit :
 > The following reply was made to PR port-amd64/51216; it has been noted 
 > by GNATS.
 > 
 > From: matthew green <mrg%eterna.com.au@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 >     netbsd-bugs%netbsd.org@localhost, m33%tok715.net@localhost
 > Subject: re: port-amd64/51216: Can't create wedges on a large (3TB)
 > disk, gpt is ok but dkctl gives an error message
 > Date: Tue, 07 Jun 2016 03:10:01 +1000
 > 
 >  Michael van Elst writes:
 >  > The following reply was made to PR port-amd64/51216; it has been 
 > noted b=
 >  y GNATS.
 >  > =
 > 
 >  > From: mlelstv%serpens.de@localhost (Michael van Elst)
 >  > To: gnats-bugs%netbsd.org@localhost
 >  > Cc: =
 > 
 >  > Subject: Re: port-amd64/51216: Can't create wedges on a large (3TB) 
 > disk=
 >  , gpt is ok but dkctl gives an error message
 >  > Date: Mon, 6 Jun 2016 16:28:54 +0000 (UTC)
 >  > =
 > 
 >  >  kre%munnari.OZ.AU@localhost (Robert Elz) writes:
 >  >  =
 > 
 >  >  > I wonder if now that wedges are becoming used more, and wdNx (and 
 > sdN=
 >  x)
 >  >  > thus used less, if perhaps we should start creating /dev/[sw]dN 
 > and
 >  >  > /dev/r[sw]dN as aliases of (or links to) /dev/[r][sw]dN[cd] (as 
 > appro=
 >  priate)
 >  >  > (ie /dev/wd1 is a link to /dev/wd1d on i386 (etc) or /dev/wd1c 
 > (on sp=
 >  arc etc))
 >  >  =
 > 
 >  >  =
 > 
 >  >  Maybe, but much of the confusion must have come from using commands 
 > in =
 >  the /dev
 >  >  directory. Tools like gpt interpret device names (e.g. wd0) and 
 > automat=
 >  ically
 >  >  select the raw device.... unless there is a file 'wd0' in the local 
 > dir=
 >  ectory.
 >  >  =
 > 
 >  >  That functionality should be changed. If you need a file in the 
 > local d=
 >  irectory
 >  >  it should be written like ./wd0.
 > 
 >  i like both of these ideas.
 > 
 >  - it avoids the accidental file creation in /dev =
 > 
 >  - it avoids odd errors when you have files called "wd0" lying around
 >    that aren't disks..
 > 
 > 
 >  .mrg.
 
 
 Thanks for your help, I will give it a try with carefull devices name 
 verification.
 
 My 2 cents: anything that helps avoid such confusion, and promotes using 
 modern/new commands will benefits to newcomers.
 And maybe long time users too, who get new hardware in the amd64 port 
 (with uefi and new boot process... large disks... tons of cpu cores for 
 virtual machines...).