Sponsored Content
Operating Systems Linux Red Hat How to resize filesystem by resizing the LUN without impact to applications.? Post 302830245 by Peasant on Monday 8th of July 2013 10:52:48 AM
Old 07-08-2013
While in principal i agree with Just Ice, it should be doable on RHEL as per documentation.
https://access.redhat.com/site/docum...-logical-units

There is alot of work so be sure to read the entire thing.
Test it on some test environment multiple times.

I would not recommend it tho, since adding a new lun is much safer/easier operation and in these days with tiering and stuff going on on the storage performance wise probably the same.
 

10 More Discussions You Might Find Interesting

1. AIX

Filesystem resize (AIX 5.3)

Hi.. I have to resize a partition(filesystem). I mean reduce the size one particular partition and increase the size of another. What should I do?? Pls help Bala (5 Replies)
Discussion started by: balaji_prk
5 Replies

2. Solaris

VxVM filesystem resize

This is actually a VxVM question. I have a volume/filesystem spread over 4*146G disks. Now I want to shrink the filesystem - which I can do using vxresize. However, I want to shrink so that two of the four disks that the filesystem occupies are removed from the volume. Can I do that? (3 Replies)
Discussion started by: blowtorch
3 Replies

3. Solaris

Making filesystem on presented lun

Hi, I am working on SunOS perlrate 5.10 Generic_127111-09 sun4v sparc SUNW,SPARC-Enterprise-T5120. The server has an LSISAS3801E HBA card installed and is connected to a StorageTek 2530 array. I have made a volume on arrary using Common Array Manager. I can see the volume on server: ... (2 Replies)
Discussion started by: seanban
2 Replies

4. Solaris

Netapp filer LUN Resize. Commands to run on Solaris afterwards.

Hi, I need to increase a veritas filesystem I have currently mounted on a Solaris 10 server. We can resize the LUN on the NetApp filer no problem. What I need to know is what do I do next on the Solaris 10 server I have so that it will see the increase in size. Do I run 'devfsadm' to... (3 Replies)
Discussion started by: gwhelan
3 Replies

5. SuSE

Resize Root Filesystem in SUSE Linux

Hello Experts, I am very new to unix environment. Root filesystem in one of our Linux boxes has almost reached 100%. is there a procedure/ way to resize the root filesystem. ****************************************************** ld8331:/ # df -h|more Filesystem Size Used... (2 Replies)
Discussion started by: ashok1784
2 Replies

6. AIX

Dynamic LUN resize

Anyone know how to resize a LUN (if SAN disk array has increased the LUN size) and have AIX LVM know about it? Or is it automatic? Equivalent vxvm command is something like: vxdisk resize size= (3 Replies)
Discussion started by: apra143
3 Replies

7. UNIX for Dummies Questions & Answers

resize a filesystem in solaris 10

i am facing a problem, i would like to resize a file system called /pcard04 i am not useing any voulme manager and we have a NETAPP center storge. what i did is root@cms-dev # df -h | grep /pcard04 /dev/dsk/c4t60A9800043346C35636F2D6D4F354743d0s0 5.2G 4.0G 1.0G 80% /pcard04 then... (1 Reply)
Discussion started by: q8devilish
1 Replies

8. Red Hat

Creating filesystem on new LUN

I'm new to linux and need information on how do I create a filesytem on a dedicated on LUN for RHEL 4 and 5? I want the filesystem to be a ext3 ---------- Post updated at 10:00 AM ---------- Previous update was at 08:56 AM ---------- Found the answer. This thread can be closed. (1 Reply)
Discussion started by: soupbone38
1 Replies

9. Solaris

Resizing the Root Filesystem

Is it possible to increase the root filesystem size without reboot ?? (4 Replies)
Discussion started by: gowthamakanthan
4 Replies

10. AIX

Resize Lun

Good afternoon! Help with a solution I have AIX 7.1 works through vios I expanded Lun that it is necessary to make that aix saw this change and to expand the section lvm Sorry for my English (1 Reply)
Discussion started by: iformats
1 Replies
KDOC(1) 						     KDOC Documentation System							   KDOC(1)

NAME
KDOC -- Programmers' Documentation Extraction and Generation Tool SYNOPSIS
kdoc [-DqpieaP] [-f format] [-n libname] [-d outdir] [-u url] [-l lib] kdoc [--help] kdoc [--version] DESCRIPTION
KDOC uses specially formatted comments in your C++ headers and CORBA IDL files to create cross-referenced documentation in various formats. KDOC can also correctly handle "signal" and "slot" specifiers as used by the Qt GUI Toolkit. EXAMPLES
kdoc -f html -d /home/web/komdoc -n kom *.idl kdoc -d /home/web/kdecore -u "http://www.mydomain/kdecore/" -n kdecore ~/kdelibs/kdecore/*.h -lqt OPTIONS
--stdin, -i Read the filenames to process from standard input. Ignored if filenames are specified at the command line. --format <string>, -f <string> Generate output in the specific format. This can be used many times to generate documentation in multiple formats. The default format is "html". See the OUTPUT FORMAT OPTIONS section for a list of available formats. --outputdir <path>, -d <path> Write output in the specified path. --url <url>, -u <url> The URL which will be used for links when cross-referencing with this library. --name <string>, -n <string> Set the name of the library being processed, eg "kdecore" If no name is set, no index file is produced. --xref <library>, -l <library> Cross-reference with the specified library. This will allow referencing of classes etc that exist in the linked library. This option can be specified multiple times. For linking to work, you need to have generated documentation for the linked library with kdoc, so that the necessary index file is produced. --libdir <path>, -L <path> Set the directory that will be used to store the index files generated for cross-referencing. This is also used to search for index files for xref. The default is $HOME/.kdoc. If multiple paths are specified, each will be searched in order of specification on the command line. Unless --liboutdir is specified (see below), the generated .kdoc file will be written to the first path specified with this option. --liboutdir <path> Set the directory where newly created xref libraries (see above) will be written. The default is the libdir. --compress, -z Compress generated KDOC index files with gzip to save space. --private, -p Document all private members. These are not documented by default. --skip-internal, -i Do not document internal members. They are documented as internal by default. --skip-deprecated, -e Do not document deprecated members. They are documented as deprecated by default. --strip-h-path Strip the path from the filenames in the output. PREPROCESSOR OPTIONS
--cpp, -P Pass each source file through the C preprocessor. Currently g++ is required for this, but this requirement will change before 2.0. Directories for inclusion in the preprocessor header search path can be specified via the -I option. --docincluded Parse files that are included by the preprocessor #include macro. This is off by default. -cppcmd <command>, -C <command> Specify the preprocessor command that will be used. The default is: g++ -Wp,-C -E All specified -I paths will be appended to the command. This option quietly enables the -P option. --includedir <path>, -I <path> Add a directory to the preprocessor's header search paths. Requires the -P option. This option can be specified multiple times. OUTPUT FORMAT OPTIONS
html Output documentation in HTML format. This is the default. latex Output documentation as a LaTeX document. man Output documentation as man pages. texinfo Output documentation in texinfo format. You must set the library name with the -n option for the output to be generated. docbook Output documentation in the DocBook SGML format. You must set the library name with the -n option for the output to be generated. check Print a report about the documentation, eg undocumented classes and functions. Output format modifiers --html-css <url> In HTML format, the stylesheet specified by this option will be used by the generated documentation. --html-cols <1, 2 ..> In HTML format, set the number of columns for the Class Index. --html-logo <image url> In HTML format, specify the logo image to display on every page. It will appear to the left of the quick links. CROSS-REFERENCING LIBRARIES FILES
*.kdoc, *.kdoc.gz These are files that contain information about a library that has been processed with kdoc. It is read for cross-referencing with other libraries when the -l option is used. The .gz extension signifies gzipped cross-reference files. kdoc is capable of reading these, and generates them when the -z option is used. ENVIRONMENT
KDOCLIBS If this is set, it is used as the default for the directory where generated cross-reference index files are saved. See also the --lib- dir option. SEE ALSO
See qt2kdoc for info on linking with the Qt docs, and makekdedoc for info on generating documentation for the KDE libraries. BUGS
Lots and Lots. Please send reports to the address kdoc@kde.org. AUTHOR
Sirtaj Singh Kang <taj@kde.org>. KDOC has a web page at: http://www.ph.unimelb.edu.au/~ssk/kde/kdoc COPYRIGHT
The KDOC tool is Copyright (c) 1998 by Sirtaj Singh Kang. KDOC is free software under the conditions of the GNU Public License. 2.0a54 2001-05-20 KDOC(1)
All times are GMT -4. The time now is 09:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy