Sponsored Content
Operating Systems Solaris How to grow a zfs file system? Post 302993087 by jlliagre on Monday 6th of March 2017 05:24:36 PM
Old 03-06-2017
Another comment about your ZFS pools.

Your root pool is almost full, has only 4% left:
Code:
rpool     136G   132G  4.10G  96%  1.00x    ONLINE  -

You are strongly advised to leave more free space in active ZFS pools as otherwise, the performance will suffer a lot due to the system trying to find free space and the data fragmentation resulting from the lack of contiguous areas. Not exceeding 80% is a safe bet.

Back to the topic, the "long" name reported for the oradata disk (c4t500A09828DE3E799d0) suggests a storage array is used to build this pool.

Exanding the oradata1 pool might then be achieved simply by enlarging the underlying LUN. Depending on your ZFS settings, nothing more might be required.

You might want to post these commands output for us to get a better idea about your configuration:
Code:
cat /etc/release
zpool status oradata1
zpool get autoexpand oradata1
cfgadm -al -o show_SCSI_LUNS c4

 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

zfs file system

Hi, I try add a new file system: #zfs create dsk1/mqm it came back with: #cannot create 'dsk1/mqm': no such pool 'dsk1' what do I have to do? Kind regards Mehrdad (2 Replies)
Discussion started by: mehrdad68
2 Replies

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

3. Solaris

How to grow my files System?

Dear Gurus of Unix. When I Put this command: # iostat -E cmdk0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Model: SAMSUNG SV4012H Revision: Serial No: 0540J1BTC53208 Size: 40.06GB <40060403712 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal... (6 Replies)
Discussion started by: andresguillen
6 Replies

4. Shell Programming and Scripting

ZFS file system - memory monitoring

I am working on a server where the 'root' user ZFS filesystem. Now when I do Top commands it says only 750M free .But when I count the actual memory utilized it comes only to 12 GB and the total size of the server is 32G. I think rest of the space is held up by ZFS file system. Is there a... (5 Replies)
Discussion started by: prasperl
5 Replies

5. Solaris

increase SWAP on ZFS file system

Hi All, I am using this commands to dynamically increase ZFS swap space on Solaris my question is: 1- after i make these commands it will permanent or it will remove after restart 2- how to make it permanent # swap -l swapfile dev swaplo bloques libre /dev/zvol/dsk/rpool/swap... (4 Replies)
Discussion started by: osmanux
4 Replies

6. Solaris

Patching on ZFS file-system

Hi, I have Solaris-10 (Update-7). This is having ZFS file-system and 10 sparse-root zones are there. I want to install Solaris-10 recommended patch cluster on it, but not sure, how to go ahead with procedure. I want to patch one side of the mirror and keep intact another side safe in case of... (6 Replies)
Discussion started by: solaris_1977
6 Replies

7. Solaris

Grow / expand a ZFS volume

Hi, I need to expand a ZFS volume from 500GB to 800GB. I'd like to ask your help to confirm the following procedure: Can I do it on the fly without bothering the users working on this volume? Thank you in advance! (6 Replies)
Discussion started by: aixlover
6 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

2540 volume expand and solaris zfs grow

Hello I hope everyone is having a good day! Situation: 2540 with 3.6TB of usable space volume A is 2.6TB volume B was 1TB Volume A is mounted via a single lun on a solaris server and is running out of space. Volume B was used on another server but is no longer, I deleted the volume in... (7 Replies)
Discussion started by: Metasin
7 Replies
cvmkfile(1)                                                        cvmkfile(1)

NAME
cvmkfile - Create a pre-allocated file SYNOPSIS
cvmkfile [-k <key>] [-p] [-s] [-w] [-z] <size>[k|m|g] <filename> DESCRIPTION
cvmkfile can be used to pre-allocate a file on the Xsan volume. This is useful and preferable when preparing a file for use in a real-time or streaming environment as the entire file is represented in only one file system extent. Additionally, a file can be placed onto a specific storage pool by specifying the <key> value, which is used as the affin- ity locator. See cvfs_config(4) for more details about affinities. USAGE
The -k <key> optionally tells the file system where to place the data file. If an Affinity Key is specified, the file is placed on storage pools that are specified to support this key. If there is no storage pool with the key specified, then the file is placed in non-exclusive data pools. If there are no non-exclusive data pools, then ENOSPC (no space) is returned. The -p option forces the allocation and any subsequent expansions to be fitted "perfectly" as multiples of the InodeExpandMin configuration parameter. The allocation extent will always line up on and be a per- fect multiple of the blocks specified in InodeExpandMin. The -s option forces the allocation to line up on the beginning block modulus of the storage pool. This can help performance in situations where the I/O size perfectly spans the width of the storage pool's disks. The -w option sets the file size to be equal to <size>. Without this option the blocks are allocated but the size is set to zero. NOTE: Unless the -z option is used, the new file will contain undefined data. Using the -w option is not recommended unless absolutely needed. The -z option causes the file to be physically zeroed out. This can take a significant amount of time. The <size> argument specifies the number of bytes, kilobytes(k), megabytes(m) or gigabytes(g) to allocate for the file. There is no guarantee that all requested space will be allocated. If there is insufficient contiguous available space to satisfy the requested amount then a "best effort" will be performed. In this case a success value is returned even though not all of the requested amount is allocated to the file. Even though the allocation may not be fully satisfied, if the -w option is specified then the file size will still reflect the requested <size> value. EXAMPLES
Make a file of one gigabyte with zero length. Allocate it on a storage pool that favors the media type 6100_n8. rock # cvmkfile -k 6100_n8 1g foobar SEE ALSO
cvfs_config(4), cvmkdir(1) Xsan File System December 2005 cvmkfile(1)
All times are GMT -4. The time now is 10:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy