Sponsored Content
Operating Systems AIX Extend a Filesystem with other LV Post 302143338 by aldowsary on Wednesday 31st of October 2007 07:06:55 PM
Old 10-31-2007
PORTER Smilie ???

Thanks a lot bakunin for your replay that has very useful information especially for me. Really, I appreciate replies like this, because it includes the answer (problem's solution) & the useful knowledge.
Thanks again. Smilie


I asked the above question because I faced a problem. I have a Filesystem which mounted over a specific LV. This LV belongs to a VG that consists of 2 PVs. This VG has MAX PVs = 8, and this is the main reason for my problem & I will explain why later.
Recently, the percentage of used space from this FS reached 90% & to increase this FS a new storage has been allocated to my system on SAN. This new storage consists of 9 PVs. Obviously it isn't possible to add all these PVs & this my problem.
Unfortunately, the SAN admin restricted with a policy that prevent him from giving me the required size divided into less than 7 PVs. Also I don't think it is possible to change the MAX PVs for the VG, because I didn't see this option except during the VG creation.

Finally, how can I add these PVs to increase the FS size? According to my knowledge I think the solution is to recreate the VG.
If am right & the only way is to recreate the VG what is the best scenario to do that without losing the existing data?

Thanks in advance
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

how can I extend /usr filesystem

How can extend /usr filesystem in hp-ux 11.11 (I'm not using online JFS) ? (0 Replies)
Discussion started by: pedro_lezaeta
0 Replies

2. Solaris

How to extend a filesystem

I am running solaris 10 with Veritas. I want to extend a filesystem. It's an oracle partition (/ora12). How can I find out if there is space available to expand the filesystem and then how does one extend it. I'm from the HPUX world and so LVM was always how I did things. Thanks jackie (5 Replies)
Discussion started by: jackiebaron
5 Replies

3. Filesystems, Disks and Memory

How to extend a filesystem??

OK I'm sure this question has been posed far too many times. I have solaris 10 x86 with NO Veritas or Disksuite filesystems. Below is the output of df -k # df -k Filesystem kbytes used avail capacity Mounted on / 10485760 547513 9317128 6% / /dev... (1 Reply)
Discussion started by: jackiebaron
1 Replies

4. Solaris

Filesystem - error when extend the filesystem

Hi all, currently , my root filesystem already reach 90 ++% I already add more cylinder in the root partition as below Part Tag Flag Cylinders Size Blocks 0 root wm 67 - 5086 38.46GB (5020/0/0) 80646300 1 swap wu 1 - ... (11 Replies)
Discussion started by: SmartAntz
11 Replies

5. Solaris

I need expand or extend a filesystem dfsk.

Hello I need to expand a filesystem is full, but I understand that for this I need a volume manager like SVM or Veritas. I have installed solaris 10 but I give it a metastat and tells me there is no database, as if the installation does not have the sudmirrors attachments. The filesystem... (1 Reply)
Discussion started by: cata
1 Replies

6. 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

7. AIX

choosing correct VG for Filesystem extend

Hi Gurus, I have Aix 5.3 server and would like to extend the following filesystem. Filesystem GB blocks Free %Used Iused %Iused Mounted on /dev/lv_mecdr 120.00 12.04 90% 560973 14% /home/mecdrBut there's only 16G for the VG, may be i can expand it... (11 Replies)
Discussion started by: thepurple
11 Replies

8. Solaris

Solaris Filesystem vs. Windows FileSystem

Hi guys! Could you tell me what's the difference of filesystem of Solaris to filesystem of Windows? I need to compare both. I have read some over the net but it's so much technical. Could you explain it in a more simpler term? I am new to Solaris. Hope you help me guys. Thanks! (4 Replies)
Discussion started by: arah
4 Replies

9. 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

10. Solaris

Extend zfs storage filesystem

Hello, Need to ask the question regarding extending the zfs storage file system. currently after using the command, df -kh u01-data-pool/data 600G 552 48G 93% /data /data are only 48 gb remaining and it has occupied 93% for total storage. zpool u01-data-pool has more then 200 gb... (14 Replies)
Discussion started by: shahzad53
14 Replies
Sys::Filesystem(3pm)					User Contributed Perl Documentation				      Sys::Filesystem(3pm)

NAME
Sys::Filesystem - Retrieve list of filesystems and their properties SYNOPSIS
use strict; use Sys::Filesystem (); # Method 1 my $fs = Sys::Filesystem->new(); my @filesystems = $fs->filesystems(); for (@filesystems) { printf("%s is a %s filesystem mounted on %s ", $fs->mount_point($_), $fs->format($_), $fs->device($_) ); } # Method 2 my $weird_fs = Sys::Filesystem->new( fstab => '/etc/weird/vfstab.conf', mtab => '/etc/active_mounts', xtab => '/etc/nfs/mounts' ); my @weird_filesystems = $weird_fs->filesystems(); # Method 3 (nice but naughty) my @filesystems = Sys::Filesystem->filesystems(); DESCRIPTION
Sys::Filesystem is intended to be a portable interface to list and query filesystem names and their properties. At the time of writing there were only Solaris and Win32 modules available on CPAN to perform this kind of operation. This module hopes to provide a consistant API to list all, mounted, unmounted and special filesystems on a system, and query as many properties as possible with common aliases wherever possible. INHERITANCE
Sys::Filesystem ISA UNIVERSAL METHODS
new Creates a new Sys::Filesystem object. new() accepts 3 optional key pair values to help or force where mount information is gathered from. These values are not otherwise defaulted by the main Sys::Filesystem object, but left to the platform specific helper modules to determine as an exercise of common sense. fstab Specify the full path and filename of the filesystem table (or fstab for short). mtab Specify the full path and filename of the mounted filesystem table (or mtab for short). Not all platforms have such a file and so this option may be ignored on some systems. xtab Specify the full path and filename of the mounted NFS filesystem table (or xtab for short). This is usually only pertinant to Unix bases systems. Not all helper modules will query NFS mounts as a separate exercise, and therefore this option may be ignored on some systems. supported Returns true if the operating system is supported by Sys::Filesystem. Unsupported operating systems may get less information, e.g. the mount state couldn't determined or which file system type is special ins't known. Listing Filesystems filesystems() Returns a list of all filesystem. May accept an optional list of key pair values in order to filter/restrict the results which are returned. The restrictions are evaluated to match as much as possible, so asking for regular and special file system (or mounted and special file systems), you'll get all. For better understanding, please imagine the parameters like: @fslist = $fs->filesystems( mounted => 1, special => 1 ); # results similar as SELECT mountpoint FROM filesystems WHERE mounted = 1 OR special = 1 If you need other selection choices, please take a look at DBD::Sys. Valid values are as follows: device => "string" Returns only filesystems that are mounted using the device of "string". For example: my $fdd_filesytem = Sys::Filesystem->filesystems(device => "/dev/fd0"); mounted => 1 Returns only filesystems which can be confirmed as actively mounted. (Filesystems which are mounted). The mounted_filesystems() method is an alias for this syntax. unmounted => 1 Returns only filesystems which cannot be confirmed as actively mounted. (Filesystems which are not mounted). The unmounted_filesystems() method is an alias for this syntax. special => 1 Returns only filesystems which are regarded as special in some way. A filesystem is marked as special by the operating specific helper module. For example, a tmpfs type filesystem on one operating system might be regarded as a special filesystem, but not on others. Consult the documentation of the operating system specific helper module for further information about your system. (Sys::Filesystem::Linux for Linux or Sys::Filesystem::Solaris for Solaris etc). This parameter is mutually exclusive to "regular". The special_filesystems() method is an alias for this syntax. regular => 1 Returns only fileystems which are not regarded as special. (Normal filesystems). This parameter is mutually exclusive to "special". The regular_filesystems() method is an alias for this syntax. mounted_filesystems() Returns a list of all filesystems which can be verified as currently being mounted. unmounted_filesystems() Returns a list of all filesystems which cannot be verified as currently being mounted. special_filesystems() Returns a list of all fileystems which are considered special. This will usually contain meta and swap partitions like /proc and /dev/shm on Linux. regular_filesystems() Returns a list of all filesystems which are not considered to be special. Filesystem Properties Available filesystem properties and their names vary wildly between platforms. Common aliases have been provided wherever possible. You should check the documentation of the specific platform helper module to list all of the properties which are available for that platform. For example, read the Sys::Filesystem::Linux documentation for a list of all filesystem properties available to query under Linux. mount_point() or filesystem() Returns the friendly name of the filesystem. This will usually be the same name as appears in the list returned by the filesystems() method. mounted() Returns boolean true if the filesystem is mounted. label() Returns the fileystem label. This functionality may need to be retrofitted to some original OS specific helper modules as of Sys::Filesystem 1.12. volume() Returns the volume that the filesystem belongs to or is mounted on. This functionality may need to be retrofitted to some original OS specific helper modules as of Sys::Filesystem 1.12. device() Returns the physical device that the filesystem is connected to. special() Returns boolean true if the filesystem type is considered "special". type() or format() Returns the type of filesystem format. fat32, ntfs, ufs, hpfs, ext3, xfs etc. options() Returns the options that the filesystem was mounted with. This may commonly contain information such as read-write, user and group settings and permissions. mount_order() Returns the order in which this filesystem should be mounted on boot. check_order() Returns the order in which this filesystem should be consistency checked on boot. check_frequency() Returns how often this filesystem is checked for consistency. OS SPECIFIC HELPER MODULES
Dummy The Dummy module is there to provide a default failover result to the main Sys::Filesystem module if no suitable platform specific module can be found or successfully loaded. This is the last module to be tried, in order of platform, Unix (if not on Win32), and then Dummy. Unix The Unix module is intended to provide a "best guess" failover result to the main Sys::Filesystem module if no suitable platform specific module can be found, and the platform is not 'MSWin32'. This module requires additional work to improve it's guestimation abilities. Darwin First written by Christian Renz <crenz@web42.com>. Win32 Provides "mount_point" and "device" of mounted filesystems on Windows. AIX Please be aware that the AIX /etc/filesystems file has both a "type" and "vfs" field. The "type" field should not be confused with the filesystem format/type (that is stored in the "vfs" field). You may wish to use the "format" field when querying for filesystem types, since it is aliased to be more reliable accross different platforms. Other Linux, Solaris, Cygwin, FreeBSD, NetBSD, HP-UX. OS Identifiers The following list is taken from perlport. Please refer to the original source for the most up to date version. This information should help anyone who wishes to write a helper module for a new platform. Modules should have the same name as ^O in title caps. Thus 'openbsd' becomes 'Openbsd.pm'. REQUIREMENTS
Sys::Filesystem requires Perl >= 5.6 to run. TODO
Add support for Tru64, MidnightBSD, Haiku, Minix, DragonflyBSD and OpenBSD. Please contact me if you would like to provide code for these operating systems. SUPPORT
You can find documentation for this module with the perldoc command. perldoc Sys::Filesystem You can also look for information at: o RT: CPAN's request tracker <http://rt.cpan.org/NoAuth/Bugs.html?Dist=Sys-Filesystem> o AnnoCPAN: Annotated CPAN documentation <http://annocpan.org/dist/Sys-Filesystem> o CPAN Ratings <http://cpanratings.perl.org/s/Sys-Filesystem> o Search CPAN <http://search.cpan.org/dist/Sys-Filesystem/> SEE ALSO
perlport, Solaris::DeviceTree, Win32::DriveInfo VERSION
$Id: Filesystem.pm 141 2010-05-14 16:04:41Z trevor $ AUTHOR
Nicola Worthington <nicolaw@cpan.org> - <http://perlgirl.org.uk> Jens Rehsack <rehsack@cpan.org> - <http://www.rehsack.de/> ACKNOWLEDGEMENTS
See CREDITS in the distribution tarball. COPYRIGHT
Copyright 2004,2005,2006 Nicola Worthington. Copyright 2008-2010 Jens Rehsack. This software is licensed under The Apache Software License, Version 2.0. <http://www.apache.org/licenses/LICENSE-2.0> perl v5.10.1 2010-05-18 Sys::Filesystem(3pm)
All times are GMT -4. The time now is 06:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy