Sponsored Content
Operating Systems Linux Red Hat Physical Volume Create Conundrum Post 302852525 by verdepollo on Wednesday 11th of September 2013 05:27:45 PM
Old 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

physical volume and physical disk.

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

Physical volume- no free physical partitions

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

Basic Filesystem / Physical Volume / Logical Volume Check

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

trying to devide existing physical volume

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

How to determine the physical volume fo the disks

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

importing a Physical Volume

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

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

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

Create volume using LVM over 2 physical disks

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

Position of the logical volume on the physical volume

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

No space in volume group. How to create a file system using existing logical volume

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
KSC(1)								   User Commands							    KSC(1)

NAME
ksc - Linux kernel module source checker SYNOPSIS
ksc [ -d | --directory ] DIRECTORY ksc [ -k | --ko ] FILE OPTIONS
KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it checks for the specific architecture for which the binary was built. Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4 -h, --help show this help message and exit -c CONFIG, --config=CONFIG path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from /etc/ksc.conf -d DIRECTORY, --directory=DIRECTORY path to the directory -i, --internal to create text files to be used internally. -k KO, --ko=KO path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the same time then only -d is used and the -k option is discarded. -n RELEASENAME, --name=RELEASENAME Red Hat release against which the bug is to be filed. Default value is 6.5 -p PREVIOUS, --previous=PREVIOUS path to the previous resultset file and submit it as a bug to Red Hat Bugzilla. -r RELEASE, --release=RELEASE RHEL whitelist release used for comparison -s, --submit Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The tool will prompt for bugzilla password. The configuration file looks like below: [bugzilla] user=user@redhat.com partner=partner-name partnergroup=partner-group server=https://bugzilla.redhat.com/xmlrpc.cgi -v, --version Prints KSC version number ksc - Version 0.9.11 Feb 2014 KSC(1)
All times are GMT -4. The time now is 05:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy