Sponsored Content
Operating Systems HP-UX Steps to Create a FileSystem HP-UX Post 302216408 by granador on Friday 18th of July 2008 08:59:29 PM
Old 07-18-2008
Steps to Create a FileSystem HP-UX

Steps to create FileSystem, and later to modify size in HP-UX. Please
 

9 More Discussions You Might Find Interesting

1. Solaris

How to create a 2 TB UFS filesystem?

Hi, I have a 2,1 TB RAID0 Array (3- 750GB discs). I have Solaris 10 x86 installed. When I try to create a volume on this drive I receive the following error: " WARNING: /pci@0/pci8086/..../sd@6,0 (sd7) disk capacity is too large for current cbd length " I assume I can not format... (5 Replies)
Discussion started by: narrok
5 Replies

2. SCO

create filesystem on file

Hello, iam pretty new to SCO, installed it yesterday in vm. Now, i'd like to create a filesystem on a file like you can do on lnx or bsd. But seems not possible for me to do so on SCO OpenServer 6.0.0. Thats what i get: bash-3.00# uname -a SCO_SV scosysv 5 6.0.0 i386 bash-3.00# mkfs... (0 Replies)
Discussion started by: user5
0 Replies

3. Solaris

what command was used to create a filesystem

How do we determine what command was used (either newfs or mkfs) to create a filesystem? Thanks, (2 Replies)
Discussion started by: Pouchie1
2 Replies

4. Shell Programming and Scripting

How to create ext3 filesystem on regular file?

After doing something like: dd if=/dev/zero of=ext3.img bs=1024 count=1048576 I'd like to put an ext3 filesystem on ext3.img. What should I run? Thanks (2 Replies)
Discussion started by: stevenswj
2 Replies

5. Red Hat

how to create a Filesystem

Hi everybody, I work with UNIX-AIX OS, I have to install db2 connect , somebody could explain to me how to create a Filesystem?, user, group, and password? ( I read a little and I know there many types of Filesystems) I have no idea how to do it, Linux version 2.6.18-92.el5... (2 Replies)
Discussion started by: lauelmar
2 Replies

6. AIX

How to create a filesystem with the correct computation of PP

Hi everyone, im having a problem with the computation of the PP size for creating a filesystem. for example my requirement is to create a new filesystem with 10gig of system on aix 5.1 and aix 5.3 system. here's the result when i run lsvg vgSAN-sparkle could any provide me an exact... (3 Replies)
Discussion started by: cwiggler
3 Replies

7. UNIX for Dummies Questions & Answers

hwo to find shared filesystem and local filesystem in AIX

Hi, I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local. Please tell me the commands which I can run... (2 Replies)
Discussion started by: kamranjalal
2 Replies

8. AIX

Mount Filesystem in AIX Unable to read /etc/filesystem

Dear all, We are facing prolem when we are going to mount AIX filesystem, the system returned the following error 0506-307The AFopen call failed : A file or directory in the path name does not exist. But when we ls filesystems in the /etc/ directory it show -rw-r--r-- 0 root ... (2 Replies)
Discussion started by: m_raheelahmed
2 Replies

9. Solaris

ZFS flash install "Unable to create Filesystem error"

Hi, I am trying to get an HPz420 workstation instaled (zfs root pool) via a jump-start server. I have a zfs image (from this workstation) the Solaris release is 10 1/13 update 11. I use a sparc U25 install server, upgraded to the same solaris build 10 1/13. This server is configured to install... (8 Replies)
Discussion started by: sc0rpie
8 Replies
LVM(8)							      System Manager's Manual							    LVM(8)

NAME
lvm - Linux Logical Volume Manager DESCRIPTION
lvm is a logical volume manager for Linux. It enables you to concatenate several physical volumes (hard disks etc.) into a so called vol- ume group (VG, see pvcreate(8) and vgcreate(8) ) forming a storage pool, like a virtual disk. IDE, SCSI disks as well as multiple devices (MD) are supported. The storage capacity of a volume group can be divided into logical volumes (LVs), like virtual disk partitions. The size of a logical volume is in multiples of physical extents (PEs, see lvcreate(8) ). The size of the physical extents can be configured at volume group creation time. If a logical volume is too small or too large you can change its size at runtime ( see lvextend(8) and lvreduce(8) ). lvcreate(8) can be used to create snapshots of existing logical volumes (so called original logical volumes in this context) as well. Creating a snapshot logical volumes grants access to the contents of the original logical volume it is associated with and exposes the read only contents at the creation time of the snapshot. This is useful for backups or for keeping several versions of filesystems online. If you run out of space in a volume group it is possible to add one or more pvcreate'd disks to the system and put them into an existing volume group ( see vgextend(8) ). The space on these new physical volumes can be dynamically added to logical volumes in that volume group ( see lvextend(8) ). To remove a physical volume from the system you can move allocated logical extents to different physical volumes ( see pvmove(8) ). After the pvmove the volume group can be reduced with the vgreduce(8) command. Inactive volume groups must be activated with vgchange(8) before use. vgcreate(8) automatically activates a newly created volume group. Abbreviations PV for physical volume, PE for physical extent, VG for volume group, LV for logical volume, and LE for logical extent. Command naming convention All command names corresponding to physical volumes start with pv, all the ones concerned with volume groups start with vg and all for log- ical volumes with lv. General purpose commands for the lvm as a whole start with lvm. VGDA
The volume group descriptor area (or VGDA for short) holds the necessary metadata to handle the LVM functionality. It is stored at the beginning of each pvcreate'd disk. It contains four parts: one PV descriptor, one VG descriptor, the LV descriptors and several PE descriptors. LE descriptors are derived from the PE ones at vgchange(8) time. Automatic backups of the VGDA are stored in files in /etc/lvmconf/ (please see vgcfgbackup(8)/vgcfgrestore(8) too). Take care to include these files in your regular (tape) backups as well. Limits Currently up to 99 volume groups with a grand total of 256 logical volumes can be created. The limit for the logical volumes is not caused by the LVM but by Linux 8 bit device minor numbers. This means that you can have 99 volume groups with 1-3 logical volumes each or on the other hand 1 volume group with up to 256 logical vol- umes or anything in between these extreme examples. Depending on the physical extent size specified at volume group creation time (see vgcreate(8) ), logical volumes of between a maximum of 512 Megabytes and 1 Petabyte can be created. Actual Linux kernels on IA32 limit these lvm possibilities to a maximum of 2 Terabytes per logical and per physical volume as well. This enables you to have as much as 256 Terabytes under LVM control with all possible 128 scsi disk subsystems. You can have up to 65534 logical extents (on IA32) in a logical volume at the cost of 1 Megabyte in kernel memory. Phys- ical volumes can have up to 65534 physical extents. /proc filesystem support The operational state of active volume groups with their physical and logical volumes can be found in the /proc/lvm/ directory. /proc/lvm/global contains a summary of all available information regarding all VGs, LVs and PVs. The two flags for PV status in brackets mean A/I for active/inactive and A/N for allocatable or non-allocatable. The four flags for LV status in brackets mean A/I for active/inactive, R/W for read-only or read/write, D/C for discontiguous or contiguous and L/S for linear or striped. S can optionally be followed by the number of stripes in the set. At /proc/lvm/VGs/ starts a subdirectory hierarchy containing information about every VG in a different subdirectory named /proc/lvm/VGs/VolumeGroupName where VolumeGroupName stands for an arbitrary VG name. /proc/lvm/VGs/Vol- umeGroupName/ in turn holds a file group containing summary information for the VG as a total. /proc/lvm/VGs/VolumeGroupName/LVs/Logi- calVolumeName holds information for an arbitrary LV named LogicalVolumeName /proc/lvm/VGs/VolumeGroupName/PVs/PhysicalVolumeName contains information for an arbitrary PV named PhysicalVolumeName. All of the information in the files below /proc/lvm/VGs/ is presented in attribute/value pairs to be easyly parsable. Examples We have disk partitions /dev/sda3, /dev/sdb1 and /dev/hda2 free for use and want to create a volume group named "test_vg". Steps required: 1. Change partition type for these 3 partitions to 0x8e with fdisk. (see pvcreate(8): 0x8e identifies LVM partitions) 2. pvcreate /dev/sda3 /dev/sdb1 /dev/hda2 3. vgcreate test_vg /dev/sda3 /dev/sdb1 /dev/hda2 With our volume group "test_vg" now online, we can create logical volumes. For example a logical volume with a size of 100MB and standard name (/dev/test_vg/lvol1) and another one named "my_test_lv" with size 200MB striped (RAID0) across all the three physical volumes. Steps required: 1. lvcreate -L 100 test_vg 2. lvcreate -L 200 -n my_test_lv -i 3 test_vg Now let's rock and roll. For example create a file system with "mkfs -t ext2 /dev/test_vg/my_test_lv" and mount it with "mount /dev/test_vg/my_test_lv /usr1" See also e2fsadm(8), lvchange(8), lvcreate(8), lvdisplay(8), lvextend(8), lvmchange(8), lvmdiskscan(8), lvmcreate_initrd(8), lvmsadc(8), lvmsar(8), lvreduce(8), lvremove(8), lvrename(8), lvscan(8), pvchange(8), pvcreate(8), pvdata(8), pvdisplay(8), pvmove(8), pvscan(8), vgcfgbackup(8), vgcfgrestore(8), vgchange(8), vgck(8), vgcreate(8), vgdisplay(8), vgexport(8), vgextend(8), vgimport(8), vgmerge(8), vgmknodes(8), vgreduce(8), vgremove(8), vgrename(8), vgscan(8), vgsplit(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS LVM(8)
All times are GMT -4. The time now is 12:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy