Sponsored Content
Top Forums UNIX for Advanced & Expert Users jfs (jfs2) for AIX versus Veritas Post 20589 by Kelam_Magnus on Monday 29th of April 2002 04:26:39 PM
Old 04-29-2002
Word of caution about reduce BACKUP, BACKUP, BACKUP...

Let me just issue a word of caution... about "on the fly". Also, I understand that some applications don't allow for downtime and you must do some things in full production. So this argument may not work in all situations.

Sure you can do many things "on the fly".

For HPUX, JFSOnline has many functions that can be performed while the box is in full production. However, no SA worth his/her salt, me included, will perform these functions while the box is in full production mode. I will find a time that is low utilization or arrange downtime, which I know is not always possible in some environments.

Any time you intend to reduce a filesytem, you are in danger of destroying data. Granted that Veritas does a great job of handling the reduce functionality. My vendor HPUX has warned that reduction with JFSOnline is risky at best, and granted that their tool in less functional than Veritas Volume Manager /Volume manager. They recommend to backup, blowaway the Volume and then rebuild it (without Vertias).

Please backup all data before you attempt this!!

Even with Veritas products, I am sure that if you read the fine print for your version of Veritas Volume manger, there will be a caution for reducing... and a possible recommendation to backup, and recreate the volume group.

Don't misunderstand, I LOVE VERITAS products!!!!!! They are great, BUT just don't take a vendor's word for the functionality of a product because they won't be responsible for restoring the data that may be lost by the product not performing up to it's billing.

Please Just BE CAREFUL!! Okay!!
In the final analysis, Veritas is by far a better tool than JFS (which is nothing more than a cheap imitation of Veritas)



Smilie Smilie Smilie
 

10 More Discussions You Might Find Interesting

1. AIX

AIX versus Networks

HI folks, Actually i have a network engineer having 2 and 1/2 years of experience in cisco having CCNA certification also. Now my company offering me to move to AIX field. I am new to AIX and do not know more about that field. So i want a suggestion from you peoples, that I have to join AIX or... (5 Replies)
Discussion started by: rawatmohinder
5 Replies

2. AIX

JFS and JFS2

hi all, can sumbody give me a link which gives the basic layout of JFS, JFS2 and the veritas file system. and i also want to know about the data structures used in this filsystem thanx in advance (0 Replies)
Discussion started by: anwerreyaz
0 Replies

3. AIX

(URGENT) Mounting JFS2 FileSystem on AIX 4.3

Hi Every body, I created Volume Group & FileSystem of type JFS2 with size 1.3 TB on AIX 5.2. I want to import this VG on another system AIX 4.3. It is imported successfully & I can varyon the VG but unfourtantly I couldn't mount the FileSystem. Is it possible to mount a JFS2 FileSystem on AIX... (3 Replies)
Discussion started by: aldowsary
3 Replies

4. UNIX for Advanced & Expert Users

AIX 5.2 using jfs2 file system

We are using AIX 5.2 using jfs2 almost all excpt one mount. Is it possible for a non root user id to mount one file system without journaling turned on, perform some activities and then remount (un-mount and mount) the same file system again. Please advise if this is possible Thanks (2 Replies)
Discussion started by: jerardfjay
2 Replies

5. AIX

AIX 5.3 & Veritas Backup with Tape Library

hello, I am facing this problem when trying to prepare AIX 5.3 for Veritas Backup: Veritas Software is not able to communicate properly with our tape library When we tried to run these commands here's the output # cfgmgr -l fscsi0 # cfgmgr -l fscsi2 # cfgmgr -l fscsi1 cfgmgr:... (3 Replies)
Discussion started by: filosophizer
3 Replies

6. AIX

Cannot grow jfs file system on AIX 5.2

Hello all, I'm trying to grow a file system by 500MB using SMIT on AIX 5.2 but I receive this error: "0516-404 allocp: This system cannot fulfill the allocation request. There are not enough free partitions or not enough physical volumes to keep strictness and satisfy allocation requests.... (3 Replies)
Discussion started by: need2bageek
3 Replies

7. AIX

Jfs and jfs2

Hi all, Can anyone define the difference between jfs and jfs2 filesystem as well as usage of jfs log files.... Thanks.... (7 Replies)
Discussion started by: sumathi.k
7 Replies

8. AIX

AIX JFS2 content

Hello! I have a LPAR with 51GB RAM topas shows 21% of memory for client pages (~11Gb) svmon -G show 2906772 client pages in use (~11Gb) but then i try to investigate per process client memory usage svmon -P -O filtertype=client and summarize inuse column, i get only 347880 pages... (1 Reply)
Discussion started by: sys
1 Replies

9. AIX

Creating AIX LV VG and JFS2 issues?

Can someone please help me understand what it is I am doing incorrectly? I have 22 PVs (disks) assigned to a VG, the stats on the disks: # lspv hdisk1 PHYSICAL VOLUME: hdisk1 VOLUME GROUP: vg_usr1 PV IDENTIFIER: 0000150179158027 VG IDENTIFIER ... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

10. AIX

Has anyone created JFS2 file system on a USB drive attached to AIX server?

We have an IBM Power 710. It has a USB port on the front. I have done some searching and see that there is information out there on how to create a JFS2 file system on USB drives. A few have commented that they would not recommend it, if the server is important, may crash the server... Just... (0 Replies)
Discussion started by: mbenedi
0 Replies
vxtrace(1M)															       vxtrace(1M)

NAME
vxtrace - trace operations on volumes SYNOPSIS
vxtrace [-aeEls ] [-b buffersize] [-c eventcount] [-d outputfile] [-f inputfile] [-g diskgroup] [-k buffersize] [-m millisec_delay] [-o objtype [,objtype]...] [-t timeout] [-w waitinterval] [name | device]... DESCRIPTION
The vxtrace utility prints kernel error or I/O trace event records on the standard output or writes them to a file in binary format. Binary trace records written to a file can be read back and formatted by vxtrace as well. If no arguments are specified, vxtrace reports either all error trace data or all I/O trace data on all virtual disk devices. With error trace data, it is possible to select all accumulated error trace data, to wait for new error trace data, or both (the default). Selection can be limited to a specific disk group, to specific types of Veritas Volume Manager (VxVM) kernel I/O objects, or to particular named objects or devices. Under heavy loads, the kernel may discard one or more records before they can be reported to vxtrace. Even though the contents of the records are lost, the kernel keeps track of the number of lost records and reports this to vxtrace. as a record. vxtrace displays this record indicating that records were lost. You can increase the size of the kernel buffer using the -k buffersize option to reduce the likelihood of the kernel discarding records. OPTIONS
-a Appends to the outputfile instead of truncating it. By default, the output file is truncated. -b buffersize Sets the size of the buffer used by vxtrace when it obtains trace records from the kernel, or from a file when the -f option is specified. The buffer size is specified as a standard Veritas Volume Manager length (see vxintro(1M)). The default buffer size is 8K. -c eventcount Accumulates at most eventcount events and then exits. The timeout and eventcount options can be used together. -d outputfile Writes (dumps) binary trace data to the specified output file. -e Selects new error trace data. The default is to select I/O trace data. -E Selects pre-existing error trace data. This can be combined with -e to get both pre-existing trace data and new trace data. -f inputfile Reads binary trace data from the specified input file, instead of from the Veritas Volume Manager kernel. -g diskgroup Selects objects from the specified disk group. The disk group can be specified either by disk group ID or by disk group name. With no name or device arguments, all appropriate objects in the disk group are selected. With the name argument, diskgroup specifies the disk group that contains the named configuration record. -k buffersize Sets the kernel I/O trace buffer size. The Veritas Volume Manager kernel allocates a private kernel space to buffer the I/O trace records for each vxtrace command. The default buffer size is 8K bytes. Some trace records may be discarded if the trace buffer is too small. This option can be used to set a larger or a smaller kernel trace buffer size. The buffer size is speci- fied as a standard Veritas Volume Manager length (see vxintro(1M)). Depending on the Veritas Volume Manager kernel configura- tion, usually only a maximum buffer size of 1 megabyte is granted. -l Long format. Prints all available fields for all tracing records, instead of a subset of the available fields. The default is to use the short format. -m millisec_delay Pauses vxtrace for the specified period to allow more records to accumulate. name | device If name or device are specified, Veritas Volume Manager kernel objects of the requested types are selected if they are associated with the configuration records or virtual disk devices indicated by those arguments. -o objtype [,objtype]... Selects object based on the objtype option arguments. Multiple types of objects can be specified with one or several -o options. The possible object selection types are: all | ALL Selects all possible virtual disk devices, kernel objects, and physical disks. dev | logical Selects virtual disk devices. disk | physical Selects Veritas Volume Manager physical disks. log Selects all log objects. logplex Selects RAID-5 log plexes. logsd Selects DRL (dirty region logging) or RAID-5 log subdisks. logvol Selects DRL or RAID-5 log volumes. m | mv | mirror Selects mirrored volume kernel objects. p | pl | plex Selects striped or concatenated plex kernel objects. rl | rlink Selects RLINK kernel objects. If an RVG (replicated volume group) is specified, all RLINKs associated with that RVG are selected. s | sd | subdisk Selects subdisk kernel objects. v | vol | volume Selects mirrored or RAID-5 volume kernel objects. -s Specifies using synchronous writes to the outputfile instead of asynchronous writes. Asynchronous writes is the default. -t timeout Accumulates trace data for at most timeout seconds, then exits. -w waitinterval If vxtrace waits for waitinterval seconds without receiving any new events, prints waiting... to allow scripts to wake up and process previously accumulated events. This is useful for processing errors. The waiting... message does not count as an event for the purposes of the -c option. ARGUMENTS
Arguments specify configuration record names, or physical or virtual disk device nodes (by device path). If no object types were selected with the -o option, only trace records corresponding to the indicated configuration records or devices are selected; otherwise, objects of the requested types are selected if they are associated in any way with the named configuration record or device. If a name argument does not match a regular configuration record, but does match a disk access record, the indicated physical disk is selected. Physical disks can also be selected by the disk media record name. By default, name arguments are searched for in the default disk group (defaultdg) unless a disk group is specified using the -g option. The disk group for any individual name argument can be overridden using the form: diskgroup/recordname Note: When reading trace data from a file with the -f option, association information is not available. EXAMPLES
To trace all physical disk I/Os, enter: vxtrace -o disk To trace virtual disk device I/Os to the device associated with volume testvol, use either of the commands: vxtrace -g testdg -o dev testvol vxtrace /dev/vx/dsk/testdg/testvol To trace all log subdisks associated with volume testvol, enter: vxtrace -g testdg -o logsd testvol To trace all log objects, enter: vxtrace -o log To accumulate ten seconds worth of trace data for disk04 and then format that data, use: vxtrace -t 10 -d /tmp/tracedata disk04 vxtrace -l -f /tmp/tracedata To read error trace data into a script for processing, using ten second pauses to generate mail messages, use the command: vxtrace -leE -w 10 | while read ... FILES
/dev/vx/trace SEE ALSO
vxintro(1M), vxstat(1M), vxtrace(7) VxVM 5.0.31.1 24 Mar 2008 vxtrace(1M)
All times are GMT -4. The time now is 02:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy