09-11-2013
pvcreate has had some known issues in the past reporting wrong sizes, especially for disks larger than 1 TB.
It has been fixed in most recent RHEL releases. Which version are you using?
As for using raw devices vs partitions I'm gonna quote myself from another post in this forum:
Quote:
Red Hat strongly suggests not to use whole disks as PVs.
Using whole disks increases the risk of an external application overwriting the data under some rare circumstances.
Here's an example of this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=154841
Even though most of those problems have already been patched and fixed in latest RHEL releases, Red Hat still discourages that practice for production/critical systems.
Using partitions of type 8e is the preferred method.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
I need explanations about physical disks and physical volumes. What is the difference between these 2 things?
In fact, i am trying to understand what the AIX lspv2command does.
Thank you in advance. (2 Replies)
Discussion started by: VeroL
2 Replies
2. UNIX for Dummies Questions & Answers
I was in smit, checking on disc space, etc. and it appears that one of our physical volumes that is part of a large volume group, has no free physical partitions. The server is running AIX 5.1. What would be the advisable step to take in this instance? (9 Replies)
Discussion started by: markper
9 Replies
3. AIX
Hi!
Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes?
What items should I check, like where do I look at in smit? Or are there commands that I should execute?
I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies
4. UNIX for Dummies Questions & Answers
hi guys, i`m trying to take 40GB of my sda5 (/home mounted) to create new volume group(lvc)
here`s the df output:
/dev/sda2 7,9G 3,3G 4,3G 44% /
udevfs 5,0M 60K 5,0M 2% /dev
shmfs 379M 0 379M 0% /dev/shm
tmpfs 379M ... (2 Replies)
Discussion started by: neverhood
2 Replies
5. AIX
This is the report I got running the comand rptconf, but I would like to know what is the capacity of the disks installed into our server power 6 with AIX
System Model: IBM,7778-23X
Machine Serial Number: 1066D5A
Processor Type: PowerPC_POWER6
Processor Implementation Mode: POWER 6... (6 Replies)
Discussion started by: cucosss
6 Replies
6. UNIX for Dummies Questions & Answers
hi guys
I'm added a new disk to my server (virtual environment)
It used to be a Volume Group=Vol_Group01
and Logical Volume= Log_Vol_01_Data
and I see /dev/sdb
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc: 133.1 GB, 133143986176 bytes
255 heads, 63... (3 Replies)
Discussion started by: karlochacon
3 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies
1)Physical Volume
2)Volume Group
3)Logical Volume
4)Physical Partition
Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies
8. Red Hat
I wanted to know how we can combine volumes over 2 physical drives.
# fdisk -l
Disk /dev/sda: 42.9 GB, 42949672960 bytes
255 heads, 63 sectors/track, 5221 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 ... (16 Replies)
Discussion started by: ikn3
16 Replies
9. AIX
Hello everyone,
I just read that while creating a logical volume(LV) we can choose the region of the physical volume (PV) in which the LV should be created.
When I say region I mean: outer edge - outer middle - center - inner middle and inner edge.
Can anyone help me understand the utility... (11 Replies)
Discussion started by: adilyos
11 Replies
10. Red Hat
Hello Guys,
I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var.
I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
LEARN ABOUT NETBSD
mlxctl
MLXCTL(8) BSD System Manager's Manual MLXCTL(8)
NAME
mlxctl -- Mylex DAC960 family management utility
SYNOPSIS
mlxctl [-f dev] [-v] [-a] status [drive] [...]
mlxctl [-f dev] [-a] detach [drive] [...]
mlxctl [-f dev] [-a] check [drive] [...]
mlxctl [-f dev] rebuild channel:target
mlxctl [-f dev] cstatus
mlxctl [-f dev] rescan
mlxctl [-f dev] config
DESCRIPTION
The mlxctl utility performs status monitoring and management functions for Mylex DAC960 RAID controllers and attached devices.
The following options are available:
-a Apply the action to all drives attached to the controller.
-f dev Specify the control device to use. The default is /dev/mlx0.
-v Increased verbosity.
The following commands are available:
cstatus Display the controller's current status.
status Display the status of the specified drives. This command returns 0 if all drives tested are online, 1 if one or more drives are
critical and 2 if one or more are offline.
rescan Re-scan the logical drive table, and attach or detach devices from the system as necessary.
detach Detach the specified drives. Drives must be unmounted and unopened for this command to succeed.
check Initiate a consistency check and repair pass on a drive that provides redundancy (e.g., RAID1 or RAID5). This command returns imme-
diately. The status command can be used to monitor the progress of the check.
rebuild Rebuild onto the specified physical drive. Note that there can be only one running rebuild operation per controller at any given
time. This command returns immediately. The cstatus command can be used to monitor the progress of the rebuild.
config Write the current system drive configuration to stdout.
EXAMPLES
Display the status of drive ld3 attached to the controller mlx1:
mlxctl -f /dev/mlx1 -v status ld3
SEE ALSO
ld(4), mlx(4)
HISTORY
The mlxctl command first appeared in NetBSD 1.5.3, and was based on the mlxcontrol utility found in FreeBSD.
BUGS
Modifying drive configuration is not yet supported.
Some commands do not work with older firmware revisions.
Error log extraction is not yet supported.
BSD
April 10, 2000 BSD