08-06-2008
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 recognise the increase in LUN size on the fly? I don't really want to have to unmount the file system or reboot the server as it is a failry important oracle server. Your help is much appreciated. Thanks.
9 More Discussions You Might Find Interesting
1. Solaris
Hi,
I'm connecting a Solaris 10 server to a Netapp filer with two single port Emulex (Sun StorageTek PCI-X Enterprise 4GB FC HBA) HBAs. After physically installing both these HBAs what do I ned to do within Solaris 10 to enable them and configure them with persistent bindings.
Do I need... (6 Replies)
Discussion started by: gwhelan
6 Replies
2. Solaris
Hi,
I've just edited this post. I found the solution for this. Thanks. (0 Replies)
Discussion started by: gwhelan
0 Replies
3. AIX
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
4. AIX
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
5. AIX
Hi,
I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name.
Please share me the steps to complete this requirements.
Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies
6. Red Hat
Is it possible to resize a filesystem by resizing the LUN on RHEL 6.4 64-bit with LVM and no impact to running applications? The research I have done so far seems to take the approach of adding a new LUN and then expaning the volume group to the new LUN. I'm looking for an approach that avoids a... (7 Replies)
Discussion started by: aenagy
7 Replies
7. Solaris
What command can I use to find out details about a netapp filer.
I have a directory that is a filer i would like to know details about the source host/folder that it points to.
Thanks. (2 Replies)
Discussion started by: jjohnson
2 Replies
8. Solaris
So,
We have a Netapp storage solution. We have Sparc T4-4s running with LDOMS and client zones in the LDOMS, We are using FC for storage comms. So here's the basic setup
FC luns are exported to the primary on the Sparc box. using LDM they are then exported to the LDOM using vdisk. at the... (4 Replies)
Discussion started by: os2mac
4 Replies
9. Linux
Hi
I need to identify a newly attached LUN from NetApp on a linuxserver running uname -o
GNU/Linux
I have first run the df -h and got the following:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_outsystemdb-lv_root
50G 2.7G 45G ... (3 Replies)
Discussion started by: fretagi
3 Replies
LEARN ABOUT HPUX
nfs3_max_transfer_size_cots
nfs3_max_transfer_size_cots(5) File Formats Manual nfs3_max_transfer_size_cots(5)
NAME
nfs3_max_transfer_size_cots - controls the data portion size of a NFS version 3 read, write, readdir, or readdirplus request over TCP
VALUES
Failsafe
Default
Allowed values
Recommended values
A warning will be issued at runtime if the tunable is set to a value greater than 1048576 since this is outside the tested limits. This is
not a serious warning but just an information message for the administrator.
DESCRIPTION
controls the maximum size of the data portion of a NFS version 3 read, write, readdir, or readdirplus request over TCP. This parameter con-
trols both the maximum size of a request that the server returns as well as the maximum size of a request that the client generates.
Who Is Expected to Change This Tunable?
Distributed file system administrators should examine this value if they want to decrease or increase the default size of a NFS version 3
packet over TCP.
Restrictions on Changing
The tunable is dynamic; however, the transfer size for a file system is set when the file system is mounted. To affect a particular file
system, unmount and mount the file system after changing this parameter.
The actual NFS version 3 transfer size over TCP is controlled by these tunable parameters: and The actual transfer size will depend on the
tunable with the smallest value. For NFS TCP traffic increase and to the same value to increase the transfer size. To decrease the transfer
size, just changing is sufficient.
When Should the Value of This Tunable Be Raised?
An increase in the transfer size will result in fewer requests to the NFS server at the expense of system resources on both the NFS client
and NFS server.
What Are the Side Effects of Raising the Value?
Setting the limit large causes more system resources to be consumed by both the NFS client and NFS server.
When Should the Value of This Tunable Be Lowered?
In the event of NFS communication failures, the value should be changed back to the default value.
What Are the Side Effects of Lowering the Value?
An increase in NFS version 3 network traffic over TCP caused by an increase in the number of I/O requests.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
kctune(1M), sam(1M), gettune(2), settune(2), nfs3_bsize(5), nfs3_max_transfer_size(5), values(5).
Tunable Kernel Parameters nfs3_max_transfer_size_cots(5)