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


 
Thread Tools Search this Thread
Operating Systems Solaris Netapp filer LUN Resize. Commands to run on Solaris afterwards.
Prev   Next
# 1  
Old 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.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Linux

Identify newly attached LUN from NetApp

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

2. Solaris

Restore of Netapp FC lun targets used as the disks for a zpool with exported zfs file systems

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

3. Solaris

Netapp filer details - command?

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

4. Red Hat

How to resize filesystem by resizing the LUN without impact to applications.?

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

5. AIX

Netapp iscsi lun

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

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

8. Solaris

Can't see Netapp LUN on Solaris using LPFC after reboot.

Hi, I've just edited this post. I found the solution for this. Thanks. (0 Replies)
Discussion started by: gwhelan
0 Replies

9. Solaris

Connect Solaris 10 to NetApp filer using Emulex single port HBAs.

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
Login or Register to Ask a Question
NetApp::Aggregate(3pm)					User Contributed Perl Documentation				    NetApp::Aggregate(3pm)

NAME
NetApp::Aggregate -- OO class for creating and managing NetApp filer aggregates SYNOPSIS
use NetApp::Filer; use NetApp::Aggregate; my $filer = NetApp::Filer->new({ .... }); my @aggregate_names = $filer->get_aggregate_names; my @aggregates = $filer->get_aggregates; my $aggregate = $filer->get_aggregate( 'aggr01' ); DESCRIPTION
This class encapsulates a single NetApp filer aggregate, and provides methods for querying information about the aggregate and it's sub- objects (eg. volumes), as well as methods for managing the aggregate itself. INSTANCE METHODS
General Instance Methods get_filer Returns the NetApp::Filer object representing the filer on which the aggregate exists. get_name Returns the name of the aggregate as a string. get_states, get_statuses, get_options Each of these methods returns a list of strings, each of which represents a single state, status, or option for the aggregate. NOTE: All you English grammar pluralization rules fanatics can give up trying to convince the author to call that one method get_stati. get_state( $state ), get_status( $status ), get_option( $option ) Each of these methods returns the value for the specified state, status or option. If that particular key wasn't present, then this method will return undef. This makes it easy to tell the difference between a key that doesn't exist, and one that has a false value. get_plex Returns the NetApp::Aggregate::Plex object representing the plex on which the aggregate lives. Volume Specific Methods get_volume_names Returns a list of the volume names which are contained within this aggregate. get_volumes Returns a list of NetApp::Volume objects, each of which represents one of the volumes in the aggregate. get_volume( $name ) Returns a single NetApp::Volume object representing the specified volume. If that volume doesn't exist on the aggregate, then a fatal exception is raised. create_volume( %args ) This method creates a flexible volume in the aggregate, and returns the NetApp::Volume object representing the new volume. The arguments are as follows. All values are simple strings, unless otherwise noted. $aggregate->create_volume( # Required arguments name => $name, size => $size, # Optional arguments space => 'none' | 'file' | 'volume', language => $language, source_filer => $source_filer, source_volume => $source_volume, ); Both the source_filer and source_volume arguments must be given when creating a flexcache volume. The space and language arguments may not be specified with the source_filer/source_volume arguments. destroy_volume( %args ) Destroys the specified volume. Note that since this API is not designed to be used interactively, the -f (force) argument is always used. Be sure you really want to destroy the volume, programatically. $aggregate->destroy_volume( # Required argument name => $name, ); The $name must be a string, and it must be one of the volumes in the $aggregate. Qtree Specific Methods get_qtree_names Returns a list of strings, each of which is the name of a qtree on the aggregate. get_qtrees Returns a list of NetApp::Qtree objects, each of which represents a single qtree on the aggregate. get_qtree( $name ) Returns a single NetApp::Qtree object for the specified qtree name. The name must in the form of a pathname, for example: /vol/volume_name/qtree_name The qtree_name is optional if querying the object for a volume's qtree. This method simply returns nothing if the specified qtree doesn't exist on the aggregate. Snapshot Specific Methods get_snapshots Returns a list of NetApp::Snapshot objects for each of the snapshots of the aggregate. get_snapshot( $name ) Returns a single NetApp::Snapshot object matching the specified name, if it exists for the aggregate. create_snapshot( $name ) Creates a snapshot of the aggregate with the specified name. delete_snapshot( $name ) Deletes a snapshot of the aggregate with the specified name. get_snapshot_deltas Returns a list of NetApp::Snapshot::Delta objects for each snapshot delta for the aggregate. get_snapshot_reserved Returns a string representing the amount of reserved space, as a percentage. This string does NOT include the % sign. set_snapshot_reserved( $percentage ) Sets the snapshot reserved space to the specified percentage, which should also NOT include the % sign. get_snapshot_schedule Returns a NetApp::Snapshot::Schedule object representing the snapshot schedule for the aggregate. set_snapshot_schedule( %args ) Sets the snapshot schedule for the aggregate based on the arguments passed. The argument syntax is: $aggregate->set_snapshot_schedule( weekly => $weekly, daily => $daily, hourly => $hourly, hourlist => [ $hour1, $hour2, $hour3, .... ], ); TO BE IMPLEMENTED
NOTE: Currently, all of the following methods have yet to be implemented, but will be soon. This documentation serves as a guideline for how to implement the perl API for each associates CLI function. NetApp::Aggregate->create( ... ) my $aggregate = NetApp::Aggregate->create( # Required arguments filer => $filer, # NetApp::Filer object name => $aggregate_name, # Required but mutually exclusive arguments # Either 'disks' OR 'diskcount and/or disksize' disks => [ [ $disk1, $disk2, .... ], [ $diskn, $diskn+1, .... ], ], diskcount => $diskcount, disksize => $disksize, # Optional arguments raidtype => 'raid0' | 'raid4' | 'raid-dp', raidsize => $raidsize, disktype => 'ATA' | 'FCAL' | 'LUN' | 'SAS' | 'SATA' | 'SCSI', rpm => $rpm, mirrored => $boolean, ); $aggregate->add( ... ) $aggregate->add( # Required arguments name => $aggregate_name, # Required but mutually exclusive arguments # Either 'disks' OR 'diskcount and/or disksize' disks => [ [ $disk1, $disk2, .... ], [ $diskn, $diskn+1, .... ], ], diskcount => $diskcount, disksize => $disksize, # Optional arguments raidgroup => $raidgroup, force => 1, ); $aggregate->destroy() NOTE: This always uses the -force option, since this API is not interactive. $aggregate->offline() $aggregate->offline( # Optional arguments cifsdelaytime => $cifsdelaytime, ); $aggregate->online() NOTE: It is unclear whether or not we should always imply -f (force => 1), or whether we should treat the prompted scenario as an error, and raise an exception. Since forcing an aggregate online can result in data loss when -f is used, perhaps we should force that state to be cleaned up first. $aggregate->rename( $newname ) $aggregate->restrict( ... ) $aggregate->restrict( # Optional arguments cifsdelaytime => $cifsdelaytime, ); perl v5.14.2 2008-11-26 NetApp::Aggregate(3pm)