Sponsored Content
Operating Systems AIX Can not extend a JFS file system Post 80731 by Can on Thursday 11th of August 2005 06:00:39 AM
Old 08-11-2005
Can not extend a JFS file system

Hi,
I am getting an error message when i try to increase the size of a filesystems
under AIX 4.3.3:

chfs: 0506-932 Can not extend a JFS file system with nbpi = 4096
and frag = 4096 past 134217728 (512 byte blocks).

-> Characteristics Journaled File System

[Entry Fields]
File system name /u04/db/TRAINING
NEW mount point [/u04/db/TRAINING]
SIZE of file system (in 512-byte blocks) [163840000]
Mount GROUP []
Mount AUTOMATICALLY at system restart? yes +
PERMISSIONS read/write +
Mount OPTIONS [] +
Start Disk Accounting? no +
Fragment Size (bytes) 4096
Number of bytes per inode 4096
Compression algorithm no
Large File Enabled true
Allocation Group Size (MBytes) 64

-->

* Logical volume NAME nlv_training
Logical volume TYPE [jfs]
POSITION on physical volume middle +
RANGE of physical volumes minimum +
MAXIMUM NUMBER of PHYSICAL VOLUMES [32]
to use for allocation
Allocate each logical partition copy yes +
on a SEPARATE physical volume?
RELOCATE the logical volume during yes +
reorganization?
Logical volume LABEL [/u04/db/TRAINING]
MAXIMUM NUMBER of LOGICAL PARTITIONS [4096]
SCHEDULING POLICY for reading/writing parallel +
logical partition copies
PERMISSIONS read/write +
Enable BAD BLOCK relocation? yes +
Enable WRITE VERIFY? no +
Mirror Write Consistency? yes +
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

creating jfs

Need help, I have read the docs but need some better understanding. Can someone explain the reasons behind setting the values for fragement size, i-node and allocation group size? Thanks, (6 Replies)
Discussion started by: kburrows
6 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

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

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

5. Solaris

How to extend 2 GB file size limitation

Hello All, I am using a SunOS machine. My application creates output files for the downstream systems. However output files are restricted to 2GB of file size in SunOS due to which I am forced to create multiple files which is not supported by the downstream due to some limitations. Is... (5 Replies)
Discussion started by: pasupuleti81
5 Replies

6. AIX

Help with jfs

how to change the filesystem from jfs to jfs2 in ibm aix6.1 please tell me command for that. thank you, paandu (2 Replies)
Discussion started by: paandur
2 Replies

7. HP-UX

Unable To Extend the Size of a Logical Volume File System

Background: # uname -a HP-UX deedee B.11.23 U ia64 4294967295 unlimited-user license deedee.rsn.hp.com:/ # bdf /opt Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol6 6553600 6394216 158144 98% /opt /opt is almost full... (3 Replies)
Discussion started by: Rob Sandifer
3 Replies

8. Emergency UNIX and Linux Support

Not able to extend ZFS file system

Hi All, I have Solaris-10 configured with two non-global zones. All file-systems are mounted on global zone and data file-systems are mounted on non-global zone as lofs. I have added 4 luns of 100 GB each and still not able to extend a file-system. This is production server, so I can not... (5 Replies)
Discussion started by: solaris_1977
5 Replies

9. Solaris

How to extend an existing file system using SVM in solaris 10

Hi All I want to extend this file system to 120Gb: df -h /xyz Filesystem size used avail capacity Mounted on /dev/md/dsk/d80 98G 35G 62G 37% /xyzand the NetApp admin is going to give me an LUN with 22Gb. This file system is mounted on: metastat d80... (1 Reply)
Discussion started by: fretagi
1 Replies

10. AIX

Unable to extend file system

Hi, I have inherited this AIX 5.3 host. I'm unable to increase the /usr file system. It gives me this error. What needs to be done to remove this error? vios:/home/padmin$ chfs -a size=+128M /usr 0516-304 lquerypv: Unable to find device id 0002ef4df616f9690000000000000000 in the Device ... (14 Replies)
Discussion started by: dn888
14 Replies
lvdisplay(1M)															     lvdisplay(1M)

NAME
lvdisplay - display information about LVM logical volumes SYNOPSIS
lv_path ... Remarks If the logical volume input arguments belong to a combination of volume groups versions 1.0 and 2.0 or higher, the arguments may not be processed in the order they are listed on the command line. Mirrored disk information requires the installation of the optional HP MirrorDisk/UX software, which is not included in the standard HP-UX operating system. DESCRIPTION
The command displays the characteristics and status of each logical volume specified by lv_path. Options and Arguments recognizes the following options and arguments: lv_path The block device path name of a logical volume, for example, Produce a compact listing of fields described in The output is a list of colon separated fields formatted as value...]. For each logical volume, display the physical volume distribution, and the mapping of the logical extents onto the physical extents of the physical volumes. This option displays the same information as the option, except in the column where is displayed, the (Physical Volume Number in VG) will be displayed instead. Use this option with the option. Display Without -v Option If you omit the option, displays the following information for each logical volume: The block device path name of the logical volume. The path name of the volume group. The access permission and quiesce mode: The access permission is either: or If the VG containing the LV is quiesced, the quiesce mode is displayed on the same line. The quiesce mode is either: or State of the logical volume: Available but contains physical extents that are not current. Available with no stale extents. Not available for use. Number of mirror copies. Mode of mirror consistency recovery which determines how LVM performs mirror consistency recovery during volume group activation: Recover mirror consistency by using the Mirror Write Cache and Mirror Consistency Record. Implies that Mirror Write Cache is on. Recover mirror consistency by going through all logical extents and copying data from a non-stale copy to the other mirror copies. Implies that Mirror Write Cache is off. No mirror consistency recovery during volume group activation on this logical volume following a system crash. The user of the logical volume is responsible for ensuring mirror consistency. Implies that Mirror Write Cache is off. Striped, sequential or parallel scheduling policy. Striped policy is by default parallel scheduling for mirrored I/O. Size of the logical volume in megabytes (MB). Number of logical extents currently in the logical volume. Number of physical extents allocated to the logical volume. The number of stripes. If this field is 0, then the logical volume is not striped. The size of each stripe in kilobytes (KB). Bad block relocation policy. Current allocation state, displayed as one of: Physical extents are allocated in an ascending order without any gap between adjacent extents. All physical extents of a given mirror are contained in a single physical volume. Distributed allocation is turned on and any two consecutive logical extents are guaranteed to be located on different physical volumes. See lvcreate(1M) for more information. Distributed allocation is turned on but any two consecutive logical extents are NOT guaranteed to be located on different physical volumes. See lvchange(1M) for more information. Physical extents that belong to the same logical extent can be allocated on the same physical volume or physical volume group. Mirror copies for a logical extent are not allocated on the same physical volume group. Mirror copies for a logical extent are not allocated on the same physical volume. The IO timeout used by LVM for all IO to this logical volume. A value of default, indicates that the system will use the value of "forever". (Note: the actual duration of a request may exceed this timeout value when the underlying physical volume(s) have timeouts which either exceed this value or are not integer multiples thereof.) Display With -v Option If you specify the option, also lists the distribution of each logical volume across the physical volumes of the volume group and the map- ping of each logical extent of the logical volume on the physical extents of the physical volume. The distribution of logical volume lv_path across the physical volumes of the volume group, displayed in the following columns: The block device path name of the physical volume where the logical extents are allocated. The Physical Volume Number in VG (if option is specified). Number of logical extents allocated on the physical volume. Number of physical extents allocated on the physical volume. The mapping of logical extents onto physical extents, displayed in the following columns: Logical extent number. The block device path name of the physical volume that corresponds to the location of the first physical extent of the logical extent. First physical extent number allocated to the logical extent. Status of the first physical extent: or The following columns are displayed if there is at least one mirror copy: The block device path name of the physical volume that corresponds to the location of the second physical extent (first copy) of the logical extent. Second physical extent number allocated to the logical extent. Status of the second physical extent: or The following columns are displayed if there are at least two mirror copies: The block device path name of the physical volume that corresponds to the location of the third physical extent (second copy) of the logical extent. Third physical extent number allocated to the logical extent. Status of the third physical extent: or If there are more than 3 physical extents associated with one logical extent (applicable for logical volumes created within volume groups versions 2.0 or higher only), then a second line of physical extent(s) is displayed for the logical extent. The rest of the line contains the following columns: The following columns are displayed if there are at least three mirror copies: Logical extent number. The block device path name of the physical volume that corresponds to the location of the fourth physical extent(third copy) of the logical extent. Fourth physical extent number allocated to the logical extent. Status of the fourth physical extent: or The following columns are displayed if there are at least four mirror copies: The block device path name of the physical volume that corresponds to the location of the fifth physical extent (fourth copy) of the logical extent. Fifth physical extent number allocated to the logical extent. Status of the fifth physical extent: or The following columns are displayed if there are five mirror copies: The block device path name of the physical volume that corresponds to the location of the sixth physical extent(fifth copy)of the logical extent. Sixth physical extent number allocated to the logical extent. Status of the sixth physical extent: or Compact Listing (-F Option) The option generates a compact and parsable listing of the command output in colon separated fields formatted as value...]. The option is designed to be used by scripts. The resulting command output may be split across multiple lines. The output may include new keys and/or values in the future. If a key is deprecated, its associated value is set to For the current version of the command, the lines format is: The format of Line 1 is as follows: lv_name=value:vg_name=value:lv_permission=value:lv_status=value: mirror_copies=value:consistency_recovery=value:schedule=value: lv_size=value:current_le=value:allocated_pe=value:stripes=value: stripe_size=value:bad_block=value:allocation=value:used_pv=value: io_timeout=value The format of Line 2 is as follows: pv_name=value:le_on_pv=value:pe_on_pv=value The above line may be repeated with different values. The format of Line n is as follows: le=value:pv1=value:pe1=value:status_1=value[:...:pvN=value:peN=value: status_N=value] The above line may be repeated with different values. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Display information about a logical volume: Display all the available information about a logical volume, including the characteristics, status and distribution map: Display all the available information about a logical volume, but display instead of in the status and distribution map. SEE ALSO
lvchange(1M), lvcreate(1M), lvextend(1M), lvmadm(1M), lvreduce(1M), lvm(7), pvdisplay(1M), vgdisplay(1M). lvdisplay(1M)
All times are GMT -4. The time now is 12:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy