Date: Wed, 18 Mar 1998 15:10:17 -0600 From: Richard Wackerbarth <rkw@dataplex.net> To: Mike Smith <mike@smith.net.au> Cc: stable@FreeBSD.ORG Subject: Re: Disk layout concernes (was Re: ATTENTION: Call for opinion re: root device naming change ) Message-ID: <l03130300b135e629b2a5@[208.2.87.4]> In-Reply-To: <199803182042.MAA22830@dingo.cdrom.com> References: Your message of "Tue, 17 Mar 1998 07:06:14 CST." <l03130300b13423dde761@[208.2.87.4]>
next in thread | previous in thread | raw e-mail | index | archive | help
At 2:42 PM -0600 3/18/98, Mike Smith wrote:
>> At 8:50 PM -0600 3/16/98, Studded wrote:
>> >Strong vote for keeping it in. In my mind (and with all due respect to
>> >those involved) the problems we've seen were caused by too little
>> >notice, too little regression testing, and too few people reading the
>> >right lists at all. It seems to me that the bugs have been worked out of
>> >the thing, and we have an opportunity to shout the news from the
>
>> I believe that this is incorrect. I, am I am sure others who might not
>> be so vocal, have a configuration that I don't know how to use with the
>> new kernel.
>>
>> As I understand it, Mike understands the problem but does not (yet) have a
>> solution short of reformatting the HD.
>
>I'll just sit on this one right now (I've been away playing house).
>
>You are completely wrong. I have told you this previously, and went to
>the special extent of mailing you explicitly once the (legitimate)
>problem you were seeing was corrected.
>
>I have never suggested that reformatting your disk was required (or
>recommended).
>
>> This is not a version mismatch problem. I have the latest (-stable) of
>> everything. This includes the "mount", MAKEDEV, and kernel changes. All
>> imagined sd0 entries are in /dev, etc.
>
>Then you have been remiss in describing your situation to me. I have
>not received any sort of bug report from you regarding your situation,
>let alone any supporting detail.
I previously offered to send you whatever you might wish from the disk in
question.
Just tell me what you wish.
I also never saw anything that told me that you had fixed it in the 2.2 branch.
The last word that I recall was that you were working on it.
Eivind Eklund <perhaps@yes.no> requested, and I sent him, the output of
fdisk and disklabel.
I repeat them here.
brw-r----- 1 root operator 4, 0x00010002 Mar 16 06:54 sd0
brw-r----- 1 root operator 4, 0 Mar 16 06:54 sd0a
brw-r----- 1 root operator 4, 1 Mar 16 06:54 sd0b
brw-r----- 1 root operator 4, 2 Mar 16 06:54 sd0c
brw-r----- 1 root operator 4, 3 Mar 16 06:54 sd0d
brw-r----- 1 root operator 4, 4 Mar 16 06:54 sd0e
brw-r----- 1 root operator 4, 5 Mar 16 06:54 sd0f
brw-r----- 1 root operator 4, 6 Mar 16 06:54 sd0g
brw-r----- 1 root operator 4, 7 Mar 16 06:54 sd0h
brw-r----- 1 root operator 4, 0x00020002 Mar 18 15:05 sd0s1
brw-r----- 1 root operator 4, 0x00020000 Mar 18 15:05 sd0s1a
brw-r----- 1 root operator 4, 0x00020001 Mar 18 15:05 sd0s1b
brw-r----- 1 root operator 4, 0x00020002 Mar 18 15:05 sd0s1c
brw-r----- 1 root operator 4, 0x00020003 Mar 18 15:05 sd0s1d
brw-r----- 1 root operator 4, 0x00020004 Mar 18 15:05 sd0s1e
brw-r----- 1 root operator 4, 0x00020005 Mar 18 15:05 sd0s1f
brw-r----- 1 root operator 4, 0x00020006 Mar 18 15:05 sd0s1g
brw-r----- 1 root operator 4, 0x00020007 Mar 18 15:05 sd0s1h
brw-r----- 1 root operator 4, 0x00050002 Mar 18 15:05 sd0s4
brw-r----- 1 root operator 4, 0x00050000 Mar 18 15:05 sd0s4a
brw-r----- 1 root operator 4, 0x00050001 Mar 18 15:05 sd0s4b
brw-r----- 1 root operator 4, 0x00050002 Mar 18 15:05 sd0s4c
brw-r----- 1 root operator 4, 0x00050003 Mar 18 15:05 sd0s4d
brw-r----- 1 root operator 4, 0x00050004 Mar 18 15:05 sd0s4e
brw-r----- 1 root operator 4, 0x00050005 Mar 18 15:05 sd0s4f
brw-r----- 1 root operator 4, 0x00050006 Mar 18 15:05 sd0s4g
brw-r----- 1 root operator 4, 0x00050007 Mar 18 15:05 sd0s4h
brw-r----- 1 root operator 4, 0x00060002 Mar 18 15:05 sd0s5
brw-r----- 1 root operator 4, 0x00060000 Mar 18 15:05 sd0s5a
brw-r----- 1 root operator 4, 0x00060001 Mar 18 15:05 sd0s5b
brw-r----- 1 root operator 4, 0x00060002 Mar 18 15:05 sd0s5c
brw-r----- 1 root operator 4, 0x00060003 Mar 18 15:05 sd0s5d
brw-r----- 1 root operator 4, 0x00060004 Mar 18 15:05 sd0s5e
brw-r----- 1 root operator 4, 0x00060005 Mar 18 15:05 sd0s5f
brw-r----- 1 root operator 4, 0x00060006 Mar 18 15:05 sd0s5g
brw-r----- 1 root operator 4, 0x00060007 Mar 18 15:05 sd0s5h
shrimp: {6} fdisk sd0
******* Working on device /dev/rsd0 *******
parameters extracted from in-core disklabel are:
cylinders=2708 heads=19 sectors/track=81 (1539 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2708 heads=19 sectors/track=81 (1539 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
<UNUSED>
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 0, size 50000 (24 Meg), flag 80
beg: cyl 0/ sector 1/ head 0;
end: cyl 1023/ sector 63/ head 255
shrimp: {7} disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: Barracuda 2Gb
label: Dataplex Root
flags:
bytes/sector: 512
sectors/track: 32
tracks/cylinder: 64
sectors/cylinder: 2048
cylinders: 2040
sectors/unit: 4178874
rpm: 7200
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 65536 0 4.2BSD 0 0 0 # (Cyl. 0 - 31)
b: 282608 65536 swap # (Cyl. 32 - 169*)
c: 4178874 0 unused 0 0 # (Cyl. 0 - 2040*)
e: 61440 348144 4.2BSD 0 0 0 # (Cyl. 169*- 199)
f: 3769290 409584 4.2BSD 0 0 0 # (Cyl. 199*- 2040*)
shrimp: {8}
Richard Wackerbarth
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?l03130300b135e629b2a5>