9 More Discussions You Might Find Interesting
1. Solaris
All,
One-way mirror. Elements of the concat in Last-errd state. What would be the best way to correct it?
metastat -s db2test -pc
db2test/d220 p 5.0GB db2test/d200
db2test/d219 p 5.0GB db2test/d200
db2test/d218 p 5.0GB db2test/d200
db2test/d217 p 30GB db2test/d200... (0 Replies)
Discussion started by: ossupport55
0 Replies
2. Solaris
Hi Guys,
I need a help with attaching the sub mirrors as it keep throwing errors.
I have done solaris live upgrade and it was succesful but it keeps throwing error only for root (s0) and swap (s1)when i try to attach them.
For rest of the partitions for slices 3,4,5 on target 1 are able to... (4 Replies)
Discussion started by: phanidhar6039
4 Replies
3. Solaris
Hi,
Ii am facing the belwo problem:
d50: Mirror
Submirror 0: d30
State: Needs maintenance
Submirror 1: d40
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 212176648 blocks (101 GB)
d30:... (3 Replies)
Discussion started by: sag71155
3 Replies
4. Shell Programming and Scripting
Hello...
I am trying to convert my script from one to another unix flavor...
from reliant to solaris...I did all but can not convert this awk/nawk:
First code if code that works what I want under reliant and the second should do same under solaris but it does not
I did so far from this :... (2 Replies)
Discussion started by: abdulaziz
2 Replies
5. Shell Programming and Scripting
Hello...
I have script that works perfect on solaris but on Reliant UNIX sometimes it does not work ...I send files to my Xp(from Reliant UNIX) but if I try to send it to my solaris machine file can not be send...
script is:
#!/bin/ksh
localFile=$1
remoteFile=$2
... (0 Replies)
Discussion started by: amon
0 Replies
6. Solaris
Ok, so I have a remote system (7 states away) that's using SDS to manage the two 18 gig disks. /, swap, /var, /home, and /opt.
The mirroring procedure I created uses installboot to ensure there's a bootblk on both disks of an SDS mirror.
The system has a problem booting (can't write to... (21 Replies)
Discussion started by: BOFH
21 Replies
7. Filesystems, Disks and Memory
Hi Folks,
This one has me a bit confused.
I have a large system running Reliant 5.45 with an EMC 3930 disk array fibre attached. As part of our requirement I implemented host level mirroring in addition to the BCV functionality provided by the 3930.
When the mirrors are split and the... (0 Replies)
Discussion started by: gull04
0 Replies
8. Solaris
:confused: Hello folks, my company had decided to migrate from Reliant Unix to Solaris. We have an amount of sources
that have to be changed a little, because these UNIX'es are slightly different. Is there a tool (hopefully free), which can do this job? Does anyone know the exactly differences, I... (2 Replies)
Discussion started by: MS-No
2 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I've got a problem with the copy - command (reliant unix 5.43). It appears to me rather difficult to copy large amount of data. A command like "cp *.jpg" is simply refused. Does anybody know something about such a kind of restriction? Something like ... only 256 files could be copied at... (2 Replies)
Discussion started by: sysadv
2 Replies
DMC(1) DMC(1)
NAME
dmc - controls the Disk Mount Conditioner
SYNOPSIS
dmc start mount [profile-name|profile-index [-boot]]
dmc stop mount
dmc status mount [-json]
dmc show profile-name|profile-index
dmc list
dmc select mount profile-name|profile-index
dmc configure mount type access-time read-throughput write-throughput [ioqueue-depth maxreadcnt maxwritecnt segreadcnt segwritecnt]
dmc help | -h
DESCRIPTION
dmc(1) configures the Disk Mount Conditioner. The Disk Mount Conditioner is a kernel provided service that can degrade the disk I/O being
issued to specific mount points, providing the illusion that the I/O is executing on a slower device. It can also cause the conditioned
mount point to advertise itself as a different device type, e.g. the disk type of an SSD could be set to an HDD. This behavior consequently
changes various parameters such as read-ahead settings, disk I/O throttling, etc., which normally have different behavior depending on the
underlying device type.
COMMANDS
Common command parameters:
o mount - the mount point to be used in the command
o profile-name - the name of a profile as shown in dmc list
o profile-index - the index of a profile as shown in dmc list
dmc start mount [profile-name|profile-index [-boot]]
Start the Disk Mount Conditioner on the given mount point with the current settings (from dmc status) or the given profile, if pro-
vided. Optionally configure the profile to remain enabled across reboots, if -boot is supplied.
dmc stop mount
Disable the Disk Mount Conditioner on the given mount point. Also disables any settings that persist across reboot via the -boot flag
provided to dmc start, if any.
dmc status mount [-json]
Display the current settings (including on/off state), optionally as JSON
dmc show profile-name|profile-index
Display the settings of the given profile
dmc list
Display all profile names and indices
dmc select mount profile-name|profile-index
Choose a different profile for the given mount point without enabling or disabling the Disk Mount Conditioner
dmc configure mount type access-time read-throughput write-throughput [ioqueue-depth maxreadcnt maxwritecnt segreadcnt segwritecnt]
Select custom parameters for the given mount point rather than using the settings provided by a default profile.
See dmc list for example parameter settings for various disk presets.
o type - 'SSD' or 'HDD'. The type determines how various system behaviors like disk I/O throttling and read-ahead algorithms affect the
issued I/O. Additionally, choosing 'HDD' will attempt to simulate seek times, including drive spin-up from idle.
o access-time - latency in microseconds for a single I/O. For SSD types this latency is applied exactly as specified to all I/O. For HDD
types, the latency scales based on a simulated seek time (thus making the access-time the maximum latency or seek penalty).
o read-throughput - integer specifying megabytes-per-second maximum throughput for disk reads
o write-throughput - integer specifying megabytes-per-second maxmimu throughput for disk writes
o ioqueue-depth - maximum number of commands that a device can accept
o maxreadcnt - maximum byte count per read
o maxwritecnt - maximum byte count per write
o segreadcnt - maximum physically disjoint segments processed per read
o segwritecnt - maximum physically disjoint segments processed per write
dmc help | -h
Display help text
EXAMPLES
dmc start / '5400 HDD'
Turn on the Disk Mount Conditioner for the boot volume, acting like a 5400 RPM hard drive.
dmc configure /Volumes/ExtDisk SSD 100 100 50
Configure an external disk to use custom parameters to degrade performance as if it were a slow SSD with 100 microsecond latencies,
100MB/s read throughput, and 50MB/s write throughput.
IMPORTANT
The Disk Mount Conditioner is not a 'simulator'. It can only degrade (or 'condition') the I/O such that a faster disk device behaves like a
slower device, not vice-versa. For example, a 5400 RPM hard drive cannot be conditioned to act like a SSD that is capable of a higher
throughput than the theoretical limitations of the hard disk.
In addition to running dmc stop, rebooting is also a sufficient way to clear any existing settings and disable Disk Mount Conditioner on
all mount points (unless started with -boot).
SEE ALSO
nlc(1)
January 2018 DMC(1)