Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My 64bit Dell box with RHEL5.5 came with 4 500GB HDs (SCSI), so I expected to have 2TB of storage space. So I was surprized that I run out of storage space when I tried to download human genome data (about 10 GB) . Since then I am trying to figure out where is all this extra space. Here what I tried:
Check physical presence of disks - dmesg report shows presence of 4 Seagate 500GB disks
Check partitions - parted print shows the following output:
Number--Start-----End------Size-----Type------File System--Flags
1-------32.3kB----82.3MB---82.2MB---primary---fat16
2-------82.3MB----5453MB---5371MB---primary----------------lvm
3-------5651MB----5914MB---263MB----primary---ext3---------boot
4-------5914MB----1499GB---1493GB---extended
5-------5980MB----38.2GB---32.2GB---logical----------------lvm
So, it comes to about 1.5TB total, not 2TB, but it still should be plenty.
Checking LVM - this is the summary what is shown in the LVM vindows:
Second - I tried to follow RedHat Deployment Guide (LVM section) with no avail. Uninitialized partition 4 is not initializable (already initialized as Extended?), but it is not shown as Unallocated, so I cannot do anything with it - it just sits there with all buttons greyed out. Cannot do anything with Unpartitioned space either - all buttons greyed out; and where these extra 0.8TB came from? For making a new LogVol I have only 5GB free space and migrating Extents is allowed only within the allocated ~35GB space.
Perhaps there is no issue at all, but I cannot quite figure it out by myself, so I would appreciate someone more experienced shows me a way out of this maze. If this is not of a general interest, please use my e-mail.
This is definitely of general interest. This is an LVM issue.
I'm not an expert in LVM but here's what I noticed when I read your post.
Quote:
VolGroup00 has 2 Physical Volumes
That accounts for two of the four disks. The other two aren't mentioned. That's half of your space right there.
Quote:
Unpartitioned Space (/dev/sda, 1360.17GB, no partition, unmounted, no filesystem, Not Initializable:Partition manually)
Unpartitioned Space (/dev/sda, 0.06GB, no partition, unmounted, no filesystem, Not Initializable:Partition manually)
Unpartitioned Space (/dev/sda, 0.18GB, no partition, unmounted, no filesystem, Not Initializable:Partition manually)
Maybe you need to create partitions in this space using LVM. Or maybe you can extend an existing partition into this space.
My limited understanding of LVM includes the notion that you can dynamically resize LVM partitions without losing data. Maybe these uninitialized spaces are part of the LVM smoke and mirrors that allows dynamic partition resizing.
I assumed that too at first, but I cannot figure out how to make usable both the partitioned and unpartitioned space. Even if I am logged in as root all options are greyed out...
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
An extended partition is used to create more than four partitions on a physical drive. Each partition table has room for four primary partitions. So, the extended partition allows you to make logical volumes while using only one primary partition. You must make logical volumes inside the extended partition, and then format them with whichever file system you want to use--which is another discussion. Gparted or qtparted should help you out. Then, if you want to add the new storage to the volume group, you use special tools designed for that purpose.
That looks like incomplete information about a single storage volume. Are the physical HDDs being combined into a single volume? RAID? What was the exact parted command line? Please post all the output of parted -l. BTW, it is easier to read that sort of output when it is posted in code tags (that's a link to instructions or you may prefer to use "Advanced Edit" mode which has a # button for code tags).
Quote:
Originally Posted by yaximik
Checking LVM - this is the summary what is shown in the LVM vindows:
That doesn't make sense; it says there's ~30 GB of LVs in 5GB of space! Please post the output of pvdisplay and vgdisplay (in code tags!).
Quote:
Originally Posted by yaximik
Uninitialized partition 4 is not initializable (already initialized as Extended?)
The extended partition is simply a container for the logical partition table so has no usable storage space.
Quote:
Originally Posted by yaximik
For making a new LogVol I have only 5GB free space and migrating Extents is allowed only within the allocated ~35GB space.
That is correct but there's a lot of unused space which could be used -- either directly, or given that LVM is already in use, for the LVM storage "pool".
Quote:
Originally Posted by yaximik
For making a new LogVol I have only 5GB free space and migrating Extents is allowed only within the allocated ~35GB space.
The simplest, most flexible configuration would be to have a single partition for LVM, using all the space in the extended partition. The steps to get there would be (subject to verification, especially you may not have the pvresize command; IDK RHEL5.5):
Extend the logical partition (sda5) to take up the whole of the extended partition.
pvresize it.
lvmove the LVs from the sda2 PV to the sda5 PV.
pvremove sda2.
It is always prudent to have a tested backup (one you have restored from); it is especially prudent when manipulating LVM which very occasionally goes wrong.
Oops, that was mistake, /dev/sda5 has 6 logical volumes, not sda2. Certaily it did not make sense.
I have no previous exposure to Linux, so perhaps one cannot be newbeer than I am. Our IT folks do not support Linux, so I am banging my head as I am learning on fly how to deploy RHEL5.5 that came preinstalled on the 64-bit Dell box. It certanly would be more informative to post screenshoots or command outputs, but I need to learn first how to do all that on the Linux box. Right now I communicate from my Windows laptop simply repeating what I see on Linux screen.
I know what should be done, the problem I do not yet know HOW to do that. I have no idea what factory folks were thinking when making partitions the box came with - why only 35 GB out of 2TB was allocated the way it is, and the rest of space is visible but unreachable. Like I said, I followed RedHat deployment guide, which says how to use LVM to manage space. But the problem is that instruction in the guide seem useless since all the buttons and menus in the LVM window are greyed out. There would not be a need to come here for help if I could proceed as instructed. I used parted with default options to get that output I provided - /sbin/parted -I followed by pprint produces the same output. I just omitted the following top lines of the output:
Model: DELL PERC 6/1 (scsi)
Disk /de/sda: 1499GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Then goes the table I provided above. Why only 1499GB is listed instead of 2000GB? Perhaps one of four 500GB HDs is not partitioned, but in the LVM window Unpartitioned space is ~1400GB in total, not 500GB. In total, it looks like Uninitialized Entities (partitionad and unpartitioned) hold ~2800GB space (as per LVM window), but the box came with four 500GB HDs, so numbers do not add up. Any advice?
Anyway I downloaded Gparted, so I try it first after I install it and figure out how to use it. I also found the qtparted site, so I am going have more headbanging fun today.
Thanks for your input, folks. Please be patient with my naivety.
Our IT folks do not support Linux, so I am banging my head as I am learning on fly how to deploy RHEL5.5 that came preinstalled on the 64-bit Dell box. It certanly would be more informative to post screenshoots or command outputs, but I need to learn first how to do all that on the Linux box. Right now I communicate from my Windows laptop simply repeating what I see on Linux screen.
Hopefully we can help you along and you will enjoy the learning adventure. Interesting to learn this is a default factory installation. Ouch! Hard work typing all that -- the sooner you find out how to copy and paste the better. In most graphical terminal emulators you highlight the text with the mouse. Sometimes that alone automatically copies it to the paste buffer, sometimes you need something like Ctrl+Shift+C to copy it. Once in a web browser it's the usual Ctrl+V to paste.
Quote:
Originally Posted by yaximik
I have no idea what factory folks were thinking when making partitions the box came with - why only 35 GB out of 2TB was allocated the way it is, and the rest of space is visible but unreachable. Like I said, I followed RedHat deployment guide, which says how to use LVM to manage space. But the problem is that instruction in the guide seem useless since all the buttons and menus in the LVM window are greyed out.
They probably did it that way to give the customer choice in how to use the remaining space. IDK RHEL5.5 but graphical LVM front ends generally are not very robust. Mostly VM is advantageous on high-availability servers and sysadmins on that type of machine tend to use the command line so the graphical LVM front ends don't get that much testing and, if they don't work as expected, it's no big deal. The greyed out extended partition is correctly greyed out.
Quote:
Originally Posted by yaximik
I used parted with default options to get that output I provided - /sbin/parted -I followed by pprint produces the same output. I just omitted the following top lines of the output:
Model: DELL PERC 6/1 (scsi)
Disk /de/sda: 1499GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Then goes the table I provided above. Why only 1499GB is listed instead of 2000GB? Perhaps one of four 500GB HDs is not partitioned, but in the LVM window Unpartitioned space is ~1400GB in total, not 500GB. In total, it looks like Uninitialized Entities (partitionad and unpartitioned) hold ~2800GB space (as per LVM window), but the box came with four 500GB HDs, so numbers do not add up. Any advice?
So the physical HDDs have been agglomerated into a single volume which is normally done for resilience using RAID but taking 4x500 physical HDDs and ending up with a 1500 volume is strange. Is there anything in the documentation about this for this specific model? Could it be that the missing capacity is used for parity-checking?
Quote:
Originally Posted by yaximik
Anyway I downloaded Gparted, so I try it first after I install it and figure out how to use it. I also found the qtparted site, so I am going have more headbanging fun today.
Many people are happy with gparted but I have found it unreliable and prefer the command line tools.
Quote:
Originally Posted by yaximik
Thanks for your input, folks. Please be patient with my naivety.
Has anyone figured this out?
I got a redhat system from Dell for the first time yesterday, so I am a complete noob when it comes to RedHat. I have been using Gentoo for years and years now, and have never had to deal with this "logical volume" stuff. Fdisk is out of the question becuase if you change the type of partition 4, it destroys partition 5. I cant believe that right out of the box they would give you a system where most of the primary drive is tied up in a format where you cant get to it, and they dont leave you even basic instructions or tools for how to access it!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.