Sponsored Content
Operating Systems Solaris Relocating directory /export/home to a bigger filesystem Post 302092648 by RTM on Wednesday 11th of October 2006 10:52:52 AM
Old 10-11-2006
First off, you don't use ufsdump/ufsrestore - your filesystem is controlled by Volume Manager - all you need to do is grow the filesystem - see the man page for vxresize or vxassist.

From Sunsolve:

Quote:
To resize a UFS (grow only) or VXFS file system using Volume Manager 3.x/4.x,
you can use the vxresize command via the command line. This command will grow a
file system AND its underlying volume.

Here is an example of the vxresize command in its basic syntax:

# vxresize -g diskgroup_name volume_name new_length

To determine the amount of space available for a resize, you can use the
vxassist command:

# vxassist -g diskgroup_name maxgrow volume_name

The new_length can be specified as either the total volume length, or as an
addition or subtraction to the current size:

# vxresize -g diskgroup_name volume_name +additional_space

You can also use this command to specify which disks to use for the resize:
To find the space available on these disks:

# vxassist -g diskgroup_name maxgrow volume_name disk01 disk02

# vxresize -g diskgroup_name volume_name new_length disk01 disk02

For additional restrictions on the use of this command please reference the
Veritas Volume Manager Administration guide for the version you are running.

For information on resizing a file system by the CLI for Volume Manager < 3.0,
see Infodoc ID 14881.
man page for vxresize
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problems with /export/home

I'm having a problem with my /export/home directory. A few of my users are getting superblock problems when they try to save files. what's something I can do to fix the problem? I'm running Solaris 7 on an Intel so no Open Boot Prom... any help would be great. thanks.. ,AP (2 Replies)
Discussion started by: Anthony
2 Replies

2. Solaris

need script for locked and unused user accounts in /export/home directory

Hi all, i have to need one script: 1. it will capture the unused user accounts in /export/home directory. 2. it will capture the locked user accounts in /export/home directory. Note: locked accounts will show in /etc/passwd like /bin/false --> (instead of ksh it will show false) the... (1 Reply)
Discussion started by: krishna176
1 Replies

3. Solaris

automountd [24] : Mount of /export/home problem

Hi Guys, Thanks for taking the time to read the problem i having outlined below: Before i go into the problem can you please tell me what the following means? a. "dt" stands for and what does it means? Configuration Below: 1x Unix Server 2x Unix Terminals (both systems are... (3 Replies)
Discussion started by: tlee
3 Replies

4. Filesystems, Disks and Memory

NFS export filesystem with several partitions

I want to export the file system which consist of several partition. For example I export / and there are /home, /usr partitions. On client side I can see all files in /, but /home and /usr are empty. So far I failed to find the way to make other partitions visible in one mount. :confused: Of... (2 Replies)
Discussion started by: fmtu2005
2 Replies

5. UNIX for Dummies Questions & Answers

/export/home question

please could someone explain what is /export/home used for ? (1 Reply)
Discussion started by: venhart
1 Replies

6. Solaris

How do I export a zfs filesystem that I created?

I created a zpool and two ZFS volumes in OpenSolaris. I would like both ZFS volumes to be exportable. However, I don't know how to set that up. These are the steps I did: 1) Create the zpool using raidz1 across five disks. I have six disks and created a zpool across 5 of them. c4t0d0... (3 Replies)
Discussion started by: sqa777
3 Replies

7. Solaris

A query regarding /export/home in Solaris

Friends, I am new to Solaris, but familiar with Linux. Could you throw some light on the need for /export/home directory in Solaris. In Linux, the default home directory for a normal user is /home/<username>. If domain concept is implemented, then the /home directory of server will be mounted... (4 Replies)
Discussion started by: saagar
4 Replies

8. Solaris

Quotas on /export/home

Hello all, I am trying to set quotas on /export/home filesystem for some of our users on a Solaris Zone I know that you would be redirecting me to some of the documentation pages, but I have already done that. The /export/home on the Zone is a Veritas FS and I cannot see an entry for... (4 Replies)
Discussion started by: grajp002
4 Replies

9. Solaris

how to change /export/home/user dir to /home /user in solaris

Hi all i am using solaris 10, i am creating user with useradd -d/home/user -m -s /bin/sh user user is created with in the following path /export/home/user (auto mount) i need the user to be created like this (/home as default home directory ) useradd -d /home/user -m -s /bin/sh... (2 Replies)
Discussion started by: kalyankalyan
2 Replies

10. HP-UX

directory space bigger than lvol?

hi everybody, i know my question is maybe stupid, but see this sr597:#/ipos# du -ks 6994419 . sr597:#/ipos# bdf . Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol3 2097152 482448 1602192 23% / if i do du-ks its about 7gb, but it supposed due to the next... (0 Replies)
Discussion started by: pabloli150
0 Replies
vxresize(1M)															      vxresize(1M)

NAME
vxresize - change the length of a volume containing a file system SYNOPSIS
/etc/vx/bin/vxresize [-bfnsx] [-F fstype] [-g diskgroup] [-o {override|verify}] [-t tasktag] volume new_length [[!]medianame...] [specification_arguments] DESCRIPTION
The vxresize command either grows or shrinks both the file system and its underlying volume to match the specified new volume length. The ability to grow or shrink is file system dependent. Some file system types may require that the file system be unmounted for the operation to succeed, as shown in the following table: ______________________________________________________________ | | Online JFS | Base JFS | HFS | | | (Full-VxFS) | (Lite-VxFS) | | |______________|_______________|_______________|_______________| | Mounted FS |Grow and shrink| Not allowed | Not allowed | | | (uses fsadm) | | | |______________|_______________|_______________|_______________| | Unmounted FS | Grow only | Grow only | Grow only | | |(uses extendfs)|(uses extendfs)|(uses extendfs)| |______________|_______________|_______________|_______________| Note: o vxresize works with JFS (derived from Veritas File System (VxFS)) and HFS file systems only. o In some situations, when resizing large volumes, vxresize may take a long time to complete. o Resizing a volume with a usage type other than FSGEN or RAID5 can result in loss of data. Use the -f option to force resizing of such a volume. o You cannot resize volumes comprised of different layout types. If you try to do so, an error message displays stating that the volume contains a different organization. The new_length operand can begin with a plus (+) or minus (-) to indicate that the new length is added to or subtracted from from the cur- rent volume length. Specify the new length, or change in length, in Veritas Volume Manager standard length units (see vxintro(1M)). The vxresize command accepts the Intelligent Storage Provisioning (ISP) storage specification arguments that are used with the vxassist command, and other vxassist specification arguments such as mirror, stripe and alloc if the volume is not an ISP volume. The arguments are passed unmodified to the vxassist command. For example, medianame operands can be specified to name the disks that are to be used for allocating new space for a volume. These argu- ments can be a simple name for a disk media record, or they can be of the form medianame, offset to specify an offset within the named disk. If an offset is specified, then regions from that offset to the end of the disk are considered candidates for allocation. If a medianame operand is prefixed by !, the specified storage is excluded from the allocation process. See the vxassist(1M) manual page for information about storage specification arguments. OPTIONS
-b Performs the resize operation in the background. The command returns quickly, but the resize will be in progress. Use the vxprint command to determine when the operation completes. Note: This option is only honored for grow operations on non-RAID5 volumes. Otherwise, it is ignored. -f Forces a operation that is usually disallowed by vxresize. -F fstype Supplies the type of the file system to be resized. -g diskgroup Limits operation of the command to the given disk group, as specified by disk group ID or disk group name. The volume operand is evaluated relative to the given disk group. -n Prevents resizing of a volume if it does not contain a file system. -s Requires that the operation represent a decrease in the volume length. -t tasktag If any tasks are registered to track the progress of the operation, mark them with the tag tasktag. The tag specified by tasktag is a sequence of up to 16 alphanumeric characters. -x Requires that the operation represent an increase in the volume length. Fail the operation otherwise. Hardware-Specific Options Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM follows the guidelines when creating volumes or allocating space for volumes. By default, vxresize only resizes volumes such that the vol- umes conform with these guidelines. The following options change the behavior of vxresize: -o override Resizes the specified volume and ignores any storage-specific guidelines. Overriding the guidelines is not recommended as it can result in incompatible objects, or objects that cannot be administered by VxVM and any associated software that exploit storage- specific features. -o verify Verifies that the specified volume can be resized without violating any storage-specific guidelines, but does not resize the vol- ume. If any guidelines are violated, vxresize exits with an error message. Note: These options need a specific license. Without the license, vxresize ignores the specified option. NOTES
When a non-ISP volume is grown, its layout may be converted as a side effect if vxassist determines that the new volume is too large for the original layout. The values of the stripe-mirror-col-trigger-pt and stripe-mirror-col-split-trigger-pt attributes (by default, 1 giga- byte) control whether a new layout will be applied. A mirror-stripe volume that is larger than the value of stripe-mirror-col-trigger-pt is converted to a stripe-mirror volume. If each column of a stripe-mirror-col volume is larger than the value of stripe-mirror-col-split- trigger-pt, the volume is converted to a stripe-mirror-sd volume where the individual subdisks, rather than the columns, are mirrored. A mirror-concat volume that is larger than the value of stripe-mirror-col-split-trigger-pt is converted to a concat-mirror volume where the individual subdisks, rather than the plexes, are mirrored. When a non-ISP volume is shrunk, its layout may be converted as a side effect if vxassist determines that the new volume is too small for the original layout. The values of the stripe-mirror-col-trigger-pt and stripe-mirror-col-split-trigger-pt attributes (by default, 1 giga- byte) control whether a new layout will be applied. A stripe-mirror volume that is smaller than the value of stripe-mirror-col-trigger-pt is converted to a mirror-stripe volume. A concat-mirror volume that is smaller than the value of stripe-mirror-col-split-trigger-pt is converted to a mirror-concat volume. If the new layout of a non-ISP volume is inappropriate, use the vxassist convert operation to change the layout after the grow or shrink operation has finished. For a CFS file system, the vxresize command must be executed on the CVM master node (as indicated by vxdctl -c mode), which must also be the CFS primary (as indicated by fsclustadm -v showprimary mount_point). If the master node is not the same node as the CFS primary, you can grow a CFS file system by running the vxassist growto or growby command on the CVM master node, followed by the fsadm -b command on any CFS node. To shrink a CFS file system, run the fsadm -b command on any CFS node, and then run the vxassist shrinkto or shrinkby command on the CVM master node. It is not possible to resize a component volume of a volume set that has an unmounted file system. This is because the extendfs command is not supported for volume sets with unmounted file systems. SEE ALSO
extendfs_vxfs(1M), fsadm_vxfs(1M), vxassist(1M), vxintro(1M), vxprint(1M), vxtask(1M) Veritas Volume Manager Administrator's Guide Veritas Storage Foundation Intelligent Storage Provisioning Administrator's Guide VxVM 5.0.31.1 24 Mar 2008 vxresize(1M)
All times are GMT -4. The time now is 06:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy