- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- 4.5 TB lvm on RHEL 5.3
Operating System - Linux
1821541
Members
2144
Online
109633
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2010 10:24 PM
тАО01-22-2010 10:24 PM
4.5 TB lvm on RHEL 5.3
Hi,
I have 4.5TB volume on storage. i want to use all the space on RHEL5.3 for storing oracle database. since its more than 2TB so i used parted.
root#parted /dev/sdc
(parted)mklabel gpt
(parted)
(parted) mkpart lvm 0 4501G
(parted) quit
Information: Don't forget to update /etc/fstab, if necessary.
since the partition id is "ee EFI GPT". i want to know do i have to change partition id to "8e".
i want to use this partition for oracle cluster.
Thanks
I have 4.5TB volume on storage. i want to use all the space on RHEL5.3 for storing oracle database. since its more than 2TB so i used parted.
root#parted /dev/sdc
(parted)mklabel gpt
(parted)
(parted) mkpart lvm 0 4501G
(parted) quit
Information: Don't forget to update /etc/fstab, if necessary.
since the partition id is "ee EFI GPT". i want to know do i have to change partition id to "8e".
i want to use this partition for oracle cluster.
Thanks
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2010 01:57 AM
тАО01-23-2010 01:57 AM
Re: 4.5 TB lvm on RHEL 5.3
Hello,
LVM partitions need to be type '8e', otherwise they'll not be found.
By the way, the valid partitions you are
mentioned in your question are:
ee GPT
ef EFI (FAT-12/16/,,,)
Cheers,
VK2COT
LVM partitions need to be type '8e', otherwise they'll not be found.
By the way, the valid partitions you are
mentioned in your question are:
ee GPT
ef EFI (FAT-12/16/,,,)
Cheers,
VK2COT
VK2COT - Dusan Baljevic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2010 04:28 AM
тАО01-23-2010 04:28 AM
Re: 4.5 TB lvm on RHEL 5.3
Which tool are you using to check the partition type?
If it's fdisk, you're not seeing the real partition table, but the "protective MBR" that is part of the GPT partitioning system. Do not change the partition ID.
http://en.wikipedia.org/wiki/GUID_Partition_Table
The GPT partitioning scheme includes the protective MBR because without it, the tools that only understand the old PC partition table would regard the GPT disk as unpartitioned. Those tools would then allow the creation of old-style partitions... which would be overlapping the real GPT partition(s).
To prevent this, the GPT creates a *fake* MBR that indicates the first 2 TB of the disk (which is all that the traditional MBR partition table can address) is occupied a partition of type 0xee. In effect, this is like posting a notice: "This disk is occupied. If you don't understand what EFI GPT means, don't touch it."
The GPT partitioning scheme includes a different system of partition types. The old partition IDs like 8e are specific to the old PC partitioning scheme: GPT uses different type identifiers.
MK
If it's fdisk, you're not seeing the real partition table, but the "protective MBR" that is part of the GPT partitioning system. Do not change the partition ID.
http://en.wikipedia.org/wiki/GUID_Partition_Table
The GPT partitioning scheme includes the protective MBR because without it, the tools that only understand the old PC partition table would regard the GPT disk as unpartitioned. Those tools would then allow the creation of old-style partitions... which would be overlapping the real GPT partition(s).
To prevent this, the GPT creates a *fake* MBR that indicates the first 2 TB of the disk (which is all that the traditional MBR partition table can address) is occupied a partition of type 0xee. In effect, this is like posting a notice: "This disk is occupied. If you don't understand what EFI GPT means, don't touch it."
The GPT partitioning scheme includes a different system of partition types. The old partition IDs like 8e are specific to the old PC partitioning scheme: GPT uses different type identifiers.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP