From nobody@FreeBSD.ORG  Sun Oct  1 07:56:44 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 2932A37B502; Sun,  1 Oct 2000 07:56:44 -0700 (PDT)
Message-Id: <20001001145644.2932A37B502@hub.freebsd.org>
Date: Sun,  1 Oct 2000 07:56:44 -0700 (PDT)
From: whs@xs4all.nl
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: Better and more disktab entries for MO drives
X-Send-Pr-Version: www-1.0

>Number:         21675
>Category:       conf
>Synopsis:       [patch] Better and more disktab entries for MO drives
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sun Oct 01 08:00:01 PDT 2000
>Closed-Date:    
>Last-Modified:  Mon Jan 14 01:16:04 UTC 2008
>Originator:     W.Scholten
>Release:        3.3
>Organization:
>Environment:
FreeBSD localhost 3.3-RELEASE FreeBSD 3.3-RELEASE #28
>Description:
Disktab entries for MO drives and a little info on how to use it. Very
useful, could also be put in sec 8.3 of the handbook.
>How-To-Repeat:

>Fix:
This patch replaces an old entry (named after and IBM MO drive, but MO
disks can be used on any other MO drive) and adds 640MB formats.


begin 644 disktab.diff.gz
M'XL("!I*USD``V1I<VMT86(N9&EF9@"]5-MJVT`0?8Z_8D`/35#DK*Z1!0;7
M+;1Y,"FXCX6R6JT=$:UD5JNX@7Y\9U:*8[NYE=)*6&N-S\R>,W/6GN?!A33B
MHBC;6\/S<:/+]<FRJ^%:&``?_"0+TBR<0,`8&[FN>P`_1EYF\8"<S<#S)_&Y
M[X,[K+/9"$ZRC7#BRR1A+&N$P[)O-L9W,8XQPZ?1.)@O/V8Y=U)_$F0K[O@L
MB+(1C#QE>!B$[*=JZ'DU7\#BZWN/0D"?A5Q#.([+6MS`@J]K:1KO>F-*P2O<
MS#O)S/U42]7<29Y7,BO,=/EA>95IY81$P$):Z<1^D-7&2:*L;IT0OPLG0(4M
M+BQ*L[9SHB@*TZA/0`'#JQ6`M",V28CVOIH>*G90TC]RG;\2Y#JO*R+,GTFB
MC+=JLM@C43`"5=:EZA214ZMV;W_?,F/#Z)%*D*:,R/@8(=L@J?,(7+L$#ZY!
M`TS0(>EO9*AJ;Z)\!\D)D@^0?`\B=A"BF8L!(BQDY-+M@(<73!@H!:KO-S1]
MOX%L#ZM&*VY:."UD@5$C"QL_RVPF5?BBY89K";Q/X"WF5%6SQ1PY7H^A:\MZ
M#86\*X6$@K,SLL$)82N>RPJ\.7A;\#3]!M865+71Q[`]3!)9S*FYD92^JO@:
M1*>UEK6I[J%H9%N_,[!MM!4`B(?%'!1*X&=C2N5U`9A=VTUJN5VUX!E@X'7X
MP$UX7W_*+++#54E>MY0#=[SJ)*K4C8)'?MNRJB"7*!=;1)LZ8#07MRU5H&H.
MM%*81K?$@.[^"'R2M=2EZ%U/9P")+JYM8?+;&PS_O-\O#_V>A$'<)UB[V]=7
M[#ZXO8?V1YB(8T./B&/DD#@,UX[_B_0MR2/^?NSO\P]]%L;!06F4,40?9#S\
M@=JD`R6/26*7]"@(^_Y=\1\O36,P,J)`\(THS;T=\X?/2\@Y#1W/C.@J;LJF
M;I_LP+,3W"'W.H$-ITZ$U(DX\H]UOVU\^Z*?G.(3H@\F^;]%IR0:?8NBDW\S
,;!C]`ID&5AH'"```
`
end


>Release-Note:
>Audit-Trail:

From: "W.H.Scholten" <whs@xs4all.nl>
To: freebsd-gnats-submit@FreeBSD.org, whs@xs4all.nl
Cc:  
Subject: Re: misc/21675: Better and more disktab entries for MO drives
Date: Sun, 05 Nov 2000 22:58:33 +0000

 This is a multi-part message in MIME format.
 
 --------------1CFBAE3959E2B60015FB7483
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 Correction for the disktab diff (se was 2048 for a 512 byte medium in
 the 230_max entry) and use of -m 0 in the newfs example. Plain diff (to
 the original disktab entry of e.g. fbsd 3.3R or 4.1R) attached.
 
 Wouter
 
 --------------1CFBAE3959E2B60015FB7483
 Content-Type: text/plain; charset=us-ascii; name="disktab.diff"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline; filename="disktab.diff"
 
 --- /etc/disktab.orig	Sun Oct  1 16:28:39 2000
 +++ /etc/disktab	Sun Oct  1 16:27:59 2000
 @@ -195,11 +195,11 @@
  	:pc#576600:oc#0:\
  	:pa#576600:oa#0:ta=4.2BSD:ba#8192:fa#1024:
  
 -mta3230|mo230|IBM MTA-3230 230 Meg 3.5inch Magneto-Optical:\
 -	:ty=removeable:dt=SCSI:rm#3600:\
 -	:se#512:nt#64:ns#32:nc#216:sc#2048:su#444384:\
 -	:pa#444384:oa#0:ba#4096:fa#0:ta=4.2BSD:\
 -	:pc#444384:oc#0:
 +#mta3230|mo230|IBM MTA-3230 230 Meg 3.5inch Magneto-Optical:\
 +#	:ty=removeable:dt=SCSI:rm#3600:\
 +#	:se#512:nt#64:ns#32:nc#216:sc#2048:su#444384:\
 +#	:pa#444384:oa#0:ba#4096:fa#0:ta=4.2BSD:\
 +#	:pc#444384:oc#0:
  
  minimum:ty=mfs:se#512:nt#1:rm#300:\
  	:ns#2880:nc#1:\
 @@ -216,4 +216,42 @@
  	:pa#196608:oa#0:ba#4096:fa#512:\
  	:pb#196608:ob#0:bb#4096:fb#512:\
  	:pc#196608:oc#0:bc#4096:fc#512:
 +
 +
 +# ---- 90 mm magneto optical disk formats (dedicated disk): ----
 +# Prepare a disk as follows (e.g. using device da0):
 +#	disklabel -B -w -r da0 mo230
 +# or:
 +#	disklabel -w -r da0 mo640
 +# (the -B flag currrently doesn't work for 640 MB media).
 +# and then:
 +#	newfs -t 0 -u 0 -m 0 da0a
 +# (t=0 and u=0 means the values from disklabel will be used for # tracks and
 +# # sectors).
 +
 +
 +mo230|Generic 3.5in 230MB MO disk:\
 +	:ty=removeable:dt=SCSI:rm#3600:\
 +	:se#512:nt#64:ns#32:nc#217:sc#2048:su#446325:\
 +	:pa#446325:oa#0:ba#4096:fa#0:ta=4.2BSD:\
 +	:pc#446325:oc#0:
 +
 +mo640|Generic 3.5in 640MB MO disk:\
 +        :ty=removable:dt=SCSI:rm#3600:\
 +	:se#2048:nt#64:ns#32:nc#151:sc#2048:su#310352:\
 +        :pa#310352:oa#0:ba#8192:fa#2048:ta=4.2BSD:\
 +        :pc#310352:oc#0:
 +
 +mo230_max|Generic 3.5in 230MB MO disk using max capcity for CHS based calculations:\
 +        :ty=removeable:dt=SCSI:rm#3600:\
 +        :se#512:nt#25:ns#33:nc#541:\
 +        :pa#446325:oa#0:ba#4096:fa#0:ta=4.2BSD:\
 +        :pc#446325:oc#0:
 +
 +mo640_max|Generic 3.5in 640MB MO disk using max capcity for CHS based calculations:\
 +        :ty=removeable:dt=SCSI:rm#3600:\
 +        :se#2048:nt#28:ns#17:nc#652:\
 +        :pa#310352:oa#0:ba#8192:fa#2048:ta=4.2BSD:\
 +        :pc#310352:oc#0:
 +
  
 
 --------------1CFBAE3959E2B60015FB7483--
 
 
 

From: Bruce Evans <bde@zeta.org.au>
To: "W.H.Scholten" <whs@xs4all.nl>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/21675: Better and more disktab entries for MO drives
Date: Tue, 7 Nov 2000 15:49:28 +1100 (EST)

 On Sun, 5 Nov 2000, W.H.Scholten wrote:
 
 >  Correction for the disktab diff (se was 2048 for a 512 byte medium in
 >  the 230_max entry) and use of -m 0 in the newfs example. Plain diff (to
 >  the original disktab entry of e.g. fbsd 3.3R or 4.1R) attached.
 
 See a recent thread about fixing disklabel(8) (actually about making
 disklabel(8) easier to use).  There is no need for disktab entries
 for drives that report their size to the driver, except possibly for
 cloning a large number of identical drives with the same customized
 label (the min* entries for floppies are a good example of this), but
 customized labels belong in customized disktab files, not in the
 standard one (the min* entries belong since they are used by the system
 for building releases).
 
 >  +# ---- 90 mm magneto optical disk formats (dedicated disk): ----
 >  +# Prepare a disk as follows (e.g. using device da0):
 >  +#	disklabel -B -w -r da0 mo230
 >  +# or:
 >  +#	disklabel -w -r da0 mo640
 >  +# (the -B flag currrently doesn't work for 640 MB media).
 
 The problem seems to be in disklabel(8).
 
 >  +# and then:
 >  +#	newfs -t 0 -u 0 -m 0 da0a
 >  +# (t=0 and u=0 means the values from disklabel will be used for # tracks and
 >  +# # sectors).
 
 Are t and u worth forcing to the physical values for mo disks?  Are the
 physical values actually physical?  I force t and u for floppies, but the
 effects are mostly cosmetic (newfs doesn't really understand the weird
 geometry of 1 track with 4096 sectors, especially on a disk with only
 2880 sectors, and it prints confusing warnings which release engineers
 have been ignoring for too long).
 
 Bruce
 
 

From: "W.H.Scholten" <whs@xs4all.nl>
To: Bruce Evans <bde@zeta.org.au>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/21675: Better and more disktab entries for MO drives
Date: Tue, 07 Nov 2000 15:57:45 +0000

 Bruce Evans wrote:
 > 
 > On Sun, 5 Nov 2000, W.H.Scholten wrote:
 > 
 > >  Correction for the disktab diff (se was 2048 for a 512 byte medium in
 > >  the 230_max entry) and use of -m 0 in the newfs example. Plain diff (to
 > >  the original disktab entry of e.g. fbsd 3.3R or 4.1R) attached.
 > 
 > See a recent thread about fixing disklabel(8) (actually about making
 > disklabel(8) easier to use).  There is no need for disktab entries
 > for drives that report their size to the driver, except possibly for
 > cloning a large number of identical drives with the same customized
 > label (the min* entries for floppies are a good example of this), but
 > customized labels belong in customized disktab files, not in the
 > standard one (the min* entries belong since they are used by the system
 > for building releases).
 
 Well, as I said in my first report, this stuff could be put in the fbsd
 documentation; there seems to be almost none. A problem is also bad
 disktab entries that appear in various places and, not willing to dive
 into the disklabel stuff, people (like me) try and they don't always
 work, least not in current releases where disklabel seems more picky and
 the error messages it spits out are unhelpfull to say the least (Weird:
 writing such a label to a brand new disk works, writing it to a disk
 that has been used before fails...). So, good examples are needed. Place
 it in disktab or the docs (see also below about the 230_max/640_max
 entries).
 
 > >  +# ---- 90 mm magneto optical disk formats (dedicated disk): ----
 > >  +# Prepare a disk as follows (e.g. using device da0):
 > >  +#   disklabel -B -w -r da0 mo230
 > >  +# or:
 > >  +#   disklabel -w -r da0 mo640
 > >  +# (the -B flag currrently doesn't work for 640 MB media).
 > 
 > The problem seems to be in disklabel(8).
 > 
 > >  +# and then:
 > >  +#   newfs -t 0 -u 0 -m 0 da0a
 > >  +# (t=0 and u=0 means the values from disklabel will be used for # tracks and
 > >  +# # sectors).
 > 
 > Are t and u worth forcing to the physical values for mo disks?  Are the
 > physical values actually physical?  I force t and u for floppies, but the
 
 It makes a difference. If I don't use -t/-u then not all of the disk is
 used with the 230_max/640_max disklabel entries. It's nothing to do with
 physical formats, just using all available space on a disk (that's what
 the 230_max/640_max entries are for, as the CHS format specified by the
 drive does not use all available space).
 
 Wouter
 
 
>Unformatted:
