Sponsored Content
Operating Systems Solaris Fiber Channel StorageTek Array Visible to OS Post 302242241 by photon on Wednesday 1st of October 2008 01:07:03 PM
Old 10-01-2008
Apparently ZFS is not needed at all.

You create more space with sscs or CAM then you have to use growfs.
 

8 More Discussions You Might Find Interesting

1. HP-UX

Fiber Channel statistic & error level

I need information what maximum error level on FC card need clasification of critical level (SAN mass storidge) Please write screenshot from utility fcutil whith test option. Pawel (0 Replies)
Discussion started by: pawel_ul
0 Replies

2. Filesystems, Disks and Memory

Configure large volume on Sun StorageTek 2540 array

Hi, We have 12x1TB SATA disks in our array and I need to create 10TB volume. I defined new storage profile on array and when I tried to add volume, I faced with ~2TB limit for new volumes. I didn't find how to set another limit on my storage profile. Is there is a way to configure one large... (3 Replies)
Discussion started by: Sapfeer
3 Replies

3. Solaris

Accessing a StorageTek 2530 Disk array from SUN, SPARC Enterprise T2000

Hello, Wondering if anyone can help me with mounting a file share from my Sun T2000 server running Solaris 10 to my connected 2530 disk array? I believe I've connected the disk array correctly and I have created a volume on the array using the filesystem (Sun_SAM-FS, RAID-5). The T2000... (15 Replies)
Discussion started by: DundeeDancer
15 Replies

4. Solaris

Sun StorageTek Common Array Manager 6.0 works very slowly

Hi! I have Sun StorageTek 2540 FC array and CAM works very slowly - I can wait for software response even more than 2 minutes... I run this software on Windows machine with Firefox Web Browser but speed is terrible... How can I make it works at least a little bit faster?.. (2 Replies)
Discussion started by: Sapfeer
2 Replies

5. Filesystems, Disks and Memory

Backup Sun StorageTek Common Array Manager's configuration

In Sun manuals, I didn't find how to backup Sun StorageTek Common Array Manager's configuration. Is there a way to do it like backing up Brocade switch configuration? CAM is under Solaris 10. Thank you in advance! (0 Replies)
Discussion started by: aixlover
0 Replies

6. Filesystems, Disks and Memory

SAN questions about Sun StorageTek array

Hi, I have a question about Sun StorageTek Common Array Manager (CAM): What is the concept of 'host'? Is it the hostname of the server that has access to the managed array? If so, can I use its IP instead of its hostname? I've found a 'host' under CAM called XYZ (See below). In our... (7 Replies)
Discussion started by: aixlover
7 Replies

7. Solaris

StorageTek 2540 SAN array

Bought a Sun StorageTek 2540 SAN array a few years ago from a company that was going out of business. When we first set it up, we were able to get all the software (Common Array Manager) and firmware directly from Sun. We just upgraded the drives, but the array is too large for the firmware. Now... (6 Replies)
Discussion started by: edison303
6 Replies

8. Solaris

Issue with Fiber Channel cards in Solaris

hi everone i am experiencing disconnectivity from storage to My database machines. i have doubt on my FC cards in my sparc T4-2 machines. i want to know how should i check from my solaris that whether the cards are ok or not because once the disks get disconnect from SAN so it come back again but... (5 Replies)
Discussion started by: janakors
5 Replies
growfs(1M)						  System Administration Commands						growfs(1M)

NAME
growfs - non-destructively expand a UFS file system SYNOPSIS
/usr/sbin/growfs [-M mount-point] [newfs-options] [raw-device] DESCRIPTION
growfs non-destructively expands a mounted or unmounted UNIX file system (UFS) to the size of the file system's slice(s). Typically, disk space is expanded by first adding a slice to a metadevice, then running the growfs command. When adding space to a mirror, you expand each submirror before expanding the file system. growfs will ``write-lock'' (see lockfs(1M)) a mounted file system when expanding. The length of time the file system is write-locked can be shortened by expanding the file system in stages. For instance, to expand a 1 Gbyte file system to 2 Gbytes, the file system can be grown in 16 Mbyte stages using the -s option to specify the total size of the new file system at each stage. The argument for -s is the number of sectors, and must be a multiple of the cylinder size. Note: The file system cannot be grown if a cylinder size of less than 2 is specified. Refer to the newfs(1M) man page for information on the options available when growing a file system. growfs displays the same information as mkfs during the expansion of the file system. If growfs is aborted, recover any lost free space by unmounting the file system and running the fsck command, or run the growfs command again. OPTIONS
Root privileges are required for all of the following options. -M mount-point The file system to be expanded is mounted on mount-point. File system locking (lockfs) will be used. newfs-options The options are documented in the newfs man page. raw-device Specifies the name of a raw metadevice or raw special device, residing in /dev/md/rdsk, or /dev/rdsk, respectively, including the disk slice, where you want the file system to be grown. EXAMPLES
Example 1: Expanding nonmetadevice slice for /export file system The following example expands a nonmetadevice slice for the /export file system. In this example, the existing slice, /dev/dsk/c1t0d0s3, is converted to a metadevice so additional slices can be concatenated. # metainit -f d8 2 1 c1t0d0s3 1 c2t0d0s3 # umount /export Example 2: Associate /export with new metadevice Edit the /etc/vfstab file to change the entry for /export to the newly defined metadevice, d8. # mount /export # growfs -M /export /dev/md/rdsk/d8 The first example starts by running the metainit command with the -f option to force the creation of a new concatenated metadevice d8, which consists of the existing slice /dev/dsk/c1t0d0s3 and a new slice /dev/dsk/c2t0d0s3. Next, the file system on /export must be unmounted. The /etc/vfstab file is edited to change the entry for /export to the newly defined metadevice name, rather than the slice name. After the file system is remounted, the growfs command is run to expand the file system. The file system will span the entire metade- vice when growfs completes. The -M option enables the growfs command to expand a mounted file system. During the expansion, write access for /export is suspended until growfs unlocks the file system. Read access is not affected, though access times are not kept when the lock is in effect. Example 3: Dynamic Expansion of /export file system The following example picks up from the previous one. Here, the /export file system mounted on metadevice d8 is dynamically expanded. # metattach d8 c0t1d0s2 # growfs -M /export /dev/md/rdsk/d8 This example begins by using the metattach command to dynamically concatenate a new slice, /dev/dsk/c0t1d0s2, to the end of an existing metadevice, d8. Next, the growfs command specifies that the mount-point is /export and that it is to be expanded onto the raw metadevice /dev/md/rdsk/d8. The file system will span the entire metadevice when growfs completes. During the expansion, write access for /export is suspended until growfs unlocks the file system. Read access is not affected, though access times are not kept when the lock is in effect. Example 4: Expanding mounted file system to existing mirror The following example expands a mounted file system /files, to an existing mirror, d80, which contains two submirrors, d9 and d10. # metattach d9 c0t2d0s5 # metattach d10 c0t3d0s5 # growfs -M /files /dev/md/rdsk/d80 In this example, the metattach command dynamically concatenates the new slices to each submirror. The metattach command must be run for each submirror. The mirror will automatically grow when the last submirror is dynamically concatenated. The mirror will grow to the size of the smallest submirror. The growfs command then expands the file system. The growfs command specifies that the mount-point is /files and that it is to be expanded onto the raw metadevice /dev/md/rdsk/d80. The file system will span the entire mirror when the growfs command completes. During the expansion, write access for the file system is suspended until growfs unlocks the file system. Read access is not affected, though access times are not kept when the lock is in effect. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ SEE ALSO
fsck(1M), lockfs(1M), mkfs(1M), metattach(1M), newfs(1M), attributes(5) Solaris Volume Manager Administration Guide LIMITATIONS
Only UFS file systems (either mounted or unmounted) can be expanded using the growfs command. Once a file system is expanded, it cannot be decreased in size. The following conditions prevent you from expanding file systems: When acct is activated and the accounting file is on the target device. When C2 security is activated and the logging file is on the target file system. When there is a local swap file in the target file system. When the file system is root (/), /usr, or swap. SunOS 5.10 9 Dec 2003 growfs(1M)
All times are GMT -4. The time now is 10:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy