I want to start by saying I already resolved my issue but I want to understand why I am seeing what I am seeing.
I have a server with a RAID controller two 500GB drives and six 600GB drives. The two 500GB drives are mirrored and have the OS installed on them. The six 600GB they wanted set as RAID0 and wanted them in a new volume group. My issue was getting the full size out of the RAID0 Virtual Disk.
On boot I saw the disk:
sd 0:2:1:0: [sdb] 7025983488 512-byte logical blocks: (3.59 TB/3.27 TiB)
I work mostly with LUNs and generally I can just do a pvcreate and I am ready to use the disk. But I could not issue a pvcreate on /dev/sdb and it seemed to need to be partitioned. So I used fdisk using this procedure, which I found to be the same on Red Hat's website: Create Linux Partition
Once I had a partition I was issuing a pvcreate /dev/sdb1 and each time I ended up with only 2TB of usable space.
I ended up just issuing a pvremove, removing the partition and issueing a vgcreate against the raw device. I noticed that the vgcreate created the physical volume for me and it was the correct size.
My question is, what am I missing? I am completely fine with just skipping the fdisk and pvcreate steps but I thought I had to do those steps. What was I doing wrong? What is the proper procedure when taking a Virtual Disk presented by a RAID controller and creating or adding it to a volume group? I guess my own answer would be the procedure that works, but since I found so many references to using fdisk and partitioning the disk I am curious why that was not working for me. Thanks.
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)
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)
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)
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)
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)
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)
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)
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)
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 FREEBSD
mlxcontrol
MLXCONTROL(8) BSD System Manager's Manual MLXCONTROL(8)NAME
mlxcontrol -- Mylex DAC-family RAID management utility
SYNOPSIS
mlxcontrol <command> [args]
mlxcontrol status [-qv] [drive]
mlxcontrol rescan controller [controller ...]
mlxcontrol detach drive [drive ...]
mlxcontrol detach -a
mlxcontrol check drive
mlxcontrol config controller
mlxcontrol help command
DESCRIPTION
The mlxcontrol utility provides status monitoring and management functions for devices attached to the mlx(4) driver.
Controller names are of the form "mlxN" where N is the unit number of the controller. Drive names are of the form "mlxdN" where N is the
unit number of the drive. Do not specify the path to a device node.
status Print the status of controllers and system drives. If one or more drives are specified, only print information about these drives,
otherwise print information about all controllers and drives in the system. With the -v flag, display much more verbose informa-
tion. With the -q flag, do not print any output. 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 Rescan one or more controllers for non-attached system drives (e.g. drives that have been detached or created subsequent to driver
initialisation). If the -a flag is supplied, rescan all controllers in the system.
detach Detach one or more system drives. Drives must be unmounted and not opened by any other utility for this command to succeed. If the
-a flag is supplied, detach all system drives from the nominated controller.
check Initiate a consistency check and repair pass on a redundant system drive (e.g. RAID1 or RAID5). The controller will scan the system
drive and repair any inconsistencies. This command returns immediately; use the status command to monitor the progress of the
check.
rebuild Requires two arguments, controller and physdrive as specified in the output of the status command. All system drives using space on
the physical drive physdrive are rebuilt, reconstructing all data on the drive. Note that each controller can only perform one
rebuild at a time. This command returns immediately; use the status command to monitor the progress of the rebuild.
config Print the current configuration from the nominated controller. This command will be updated to allow addition/deletion of system
drives from a configuration in a future release.
help Print usage information for command.
AUTHORS
The mlxcontrol utility was written by Michael Smith <msmith@FreeBSD.org>.
BUGS
The config command does not yet support modifying system drive configuration.
Error log extraction is not yet supported.
BSD April 10, 2000 BSD