Well, I got a lot of repsonses on this one. Thanks to Alan Nabeth, Jay
Vlack, Peyton Bland, John J. Francini and Jeffry Hummel. The problem was
that power saving was enabled. I guess it is not really a problem, just
ignorance on my part. Basically the disks were spun down and had to spin up
every time I did a disklabel. I suspect that other accesses of disk would
be slow to respond as well, after the spindown time period which was 15
minutes. I disabled the power save on the disks. This can be done via
dxpower if you are running the gui and if you prefer the command line method
you must use sysconfigdb or edit the sysconfigtab manually. I prefer the
latter. The system administration manual gives you a brief description of
all of the power management parameters. Here is what I added:
pwrmgr:
disk_spindown=0
Disk response is fast now. The Alpha that I wrote this post about is
classified as a workstation, I don't see power save parameters for any of
the 'servers' that we have and when I ran the gui it said that power save
was not supported on the systems.
Original post below:
Hello admins,
I have a question about disklabel. I have a 433au that has a couple of
disks in it. Here is the output of disklabel for each:
# disklabel -r rz16
# /dev/rrz16a:
type: SCSI
disk: RZ1BA-BS
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 86
tracks/cylinder: 16
sectors/cylinder: 1376
cylinders: 3045
sectors/unit: 4110480
rpm: 5410
interleave: 1
trackskew: 36
cylinderskew: 48
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg] # NOTE:
values not exact
a: 262144 0 AdvFS # (Cyl. 0
- 190*)
b: 262144 262144 swap # (Cyl.
190*- 381*)
c: 4110480 0 unused 0 0 # (Cyl. 0
- 2987*)
d: 1195397 524288 unused 0 0 # (Cyl.
381*- 1249*)
e: 1195397 1719685 unused 0 0 # (Cyl.
1249*- 2118*)
f: 1195398 2915082 unused 0 0 # (Cyl.
2118*- 2987*)
g: 1433600 524288 AdvFS # (Cyl.
381*- 1422*)
h: 2152592 1957888 AdvFS # (Cyl.
1422*- 2987*)
# disklabel -r rz17
# /dev/rrz17a:
type: SCSI
disk: ST318405
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 474
tracks/cylinder: 4
sectors/cylinder: 1896
cylinders: 19036
sectors/unit: 35843670
rpm: 10023
interleave: 1
trackskew: 104
cylinderskew: 108
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg] # NOTE:
values not exact
a: 131072 0 unused 0 0 # (Cyl. 0
- 69*)
b: 262144 131072 unused 0 0 # (Cyl.
69*- 207*)
c: 35843670 0 AdvFS # (Cyl. 0
- 18904*)
d: 0 0 unused 0 0 # (Cyl. 0
- -1)
e: 0 0 unused 0 0 # (Cyl. 0
- -1)
f: 0 0 unused 0 0 # (Cyl. 0
- -1)
g: 17725227 393216 unused 0 0 # (Cyl.
207*- 9556*)
h: 17725227 18118443 unused 0 0 # (Cyl.
9556*- 18904*)
# disklabel -r rz19
Now, when I ran each of these commands I have both of the filesets from the
second disk rz17 mounted onto directories on the second disk, which is the
system disk. When I do the disklabel on the second disk it takes close to
20 seconds before I see any information. Subsequent disklabels on rz17 come
up immediately. The second disk is an 18.4G ULTRA160 10K RPM Cheetah and
the controller is only Wide. I know that I am not going to get the transfer
rate, but it should still work. Can anyone explain why such a large delay
on the first disklabel?
Thanks,
Trevor Osatchuk
Process Solutions Canada Ltd.
Support and Integration Analyst
(780) 452-2227 Ext. 286
trevor.osatchuk_at_pscl.com
Received on Tue Jun 05 2001 - 15:36:58 NZST