12-12-2006
this is from my experience
This is from my experience. I recommend not using internals for major apps. Sometimes small things can creep up and need to go on internal, small things can be dismissed.
There is no doc. This is my experience. Putting things on internal disks can cause many issues, just one of which is performance issues. You dont want to put a major database on there. Of course, you have to strike a balance. I was merely stating that major apps should not really go on internals. I wont budge from this stance.
You dont have to do anything. The previous thread states all the info you need. I clearly stated that this is my opinion. Not sure why you are antagonizing me.
-Sowser
9 More Discussions You Might Find Interesting
1. Solaris
Hi Guys,
Need to add 2 disks into a JBOD array (3310).
Does anyone see anything wrong with my Procedure / Doco below?
1> Logon to system, check system logs for abnormal entries.
2> Make backups of related system files:
A>cp -p /etc/system /etc/system.backup.081505
B>cp -p /etc/vfstab... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
2. Solaris
Hi all,
we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this?
In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies
3. Solaris
Dear All,
Please help me to configure root mirroring using SVM in Solaris 9.
Thanks and Regards,
Lakkireddy BR (3 Replies)
Discussion started by: lbreddy
3 Replies
4. Solaris
Hello All,
I am trying to mirror two non-root hard drives using zfs. But "fmthard" fails when I try to copy the vtoc due to disk mismatch. Please help me.
--- iostat command shows the disk to be similiar
--- format command shows disk to be different :confused:
--- c1t2d0 is the active... (8 Replies)
Discussion started by: pingmeback
8 Replies
5. Solaris
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies
6. Solaris
I tried doing rootdisk mirroring in my local host , i added a new Ide disk in my system
and copied the prtvtoc from root disk to the newly added disk, and then when i tried to add database replicas on both the disks, it was added for boot disk but for the newly added disk i gave the error, which... (6 Replies)
Discussion started by: Laxxi
6 Replies
7. Solaris
I would like to perform root disk mirroring task. Can someone please help me out on this.
Thanks !!
Regards,
Rama (2 Replies)
Discussion started by: ramagore85
2 Replies
8. UNIX for Beginners Questions & Answers
Hi Experts,
I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system.
#hastatus -sum
-- System State Frozen
A node1 running 0
A node2 running 0
-- Group State
-- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
9. Solaris
I need to increase the /var (UFS) filesystem and root disk under veritas control or root disk is encapsulated
# df -k /var
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/var 13241195 12475897 674524 96% /var
# fstyp /dev/vx/dsk/var
ufs
# pkginfo... (1 Reply)
Discussion started by: amity
1 Replies
LEARN ABOUT FREEBSD
minor
MAKEDEV(3) BSD Library Functions Manual MAKEDEV(3)
NAME
makedev, major, minor -- device number conversion
SYNOPSIS
#include <sys/types.h>
dev_t
makedev(int major, int minor);
int
major(dev_t dev);
int
minor(dev_t dev);
DESCRIPTION
The makedev() macro allows a unique device number to be generated based on its major and minor number. The major() and minor() macros can be
used to obtain the original numbers from the device number dev.
In previous implementations of FreeBSD all block and character devices were uniquely identified by a pair of major and minor numbers. The
major number referred to a certain device class (e.g. disks, TTYs) while the minor number identified an instance within the device class.
Later versions of FreeBSD automatically generate a unique device number for each character device visible in /dev/. These numbers are not
divided in device classes.
On FreeBSD these macros are only used by utilities that need to exchange numbers with other operating systems that may use different encod-
ings for dev_t, but also applications that present these numbers to the user in a more conventional way.
RETURN VALUES
The major() macro returns a device major number that has a value between 0 and 255. The minor() macro returns a device minor number whose
value can span the complete range of an int.
SEE ALSO
mknod(2), devname(3), devfs(5)
BSD
September 28, 2008 BSD