12-08-2015
Linux Thin Lun space reclamation
Hello,
We have IBM storwize v7000 storage. I have created thin provisioned LUN and attached it to my server(dell r910, Centos 7).
Whenever I copy files in that LUN correspondingly Thin provisioned LUN's used space increases but when I remove files to free up space the LUN's size isn't decreased.
I have opened case to IBM to address the issue but they stated that there is nothing wrong with the storage and that I should follow OS instructions to release removed blocks whenever files are removed .
Please share your opinion about this and pls let me know if you faced the same issue and how did you solve it.
Thanks in advance dear forum members
9 More Discussions You Might Find Interesting
1. Linux
Please m new around here! Can anyone take me thru implementing bootp on my thin clients via my central server?
Preciate ur assistance. Thanks folks! (2 Replies)
Discussion started by: chuk_uka
2 Replies
2. AIX
Hi, I was told that 300GB of LUN has been allocated to my server by the SAN group. apart from rootvg i have 2 volume groups(oracle) for which i need to add space as follows:
oradbvg 250GB to be added
oralvg 50GB
what are the steps that i should follow after iam being told that LUN has been... (4 Replies)
Discussion started by: karthikosu
4 Replies
3. Filesystems, Disks and Memory
Am trying to differentiate between the local disks and LUN's presented from SAN onto the server. Have Tried fdisk -l, however I quite cudn't differentiate the local disks from SAN presented LUN's.
Can you pls. let me know the procedure and commands to find this.
OS - RHEL 4
SAN - EMC... (3 Replies)
Discussion started by: Crazy_murli
3 Replies
4. Solaris
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Discussion started by: uuontario
4 Replies
5. Shell Programming and Scripting
Hi
I want to include in my script a test for DB connection with jdbc:thin connection string(not using tnsnames.ora)
For example:... (3 Replies)
Discussion started by: gdan2000
3 Replies
6. Red Hat
Hi,
I have a SAN LUN of 550 GB created as an ext3 partition of the entire lun and need to make the lun and partition larger... 600 GB
# fdisk -l /dev/sdj
Disk /dev/sdj: 590.5 GB, 590558003200 bytes
255 heads, 63 sectors/track, 71797 cylinders
Units = cylinders of 16065 * 512 = 8225280... (3 Replies)
Discussion started by: jamba1
3 Replies
7. Red Hat
Calling all Linux GURU's.
The purpose of this thread is to try an recreate what we already have stood up in my environment, however the steps i am having to produce my own.
I have got multiple applications that dump the data to various LUNs, the LUNs are managed by an Enterprise SAN... (11 Replies)
Discussion started by: jcejka
11 Replies
8. Red Hat
Hi All,
I am new for this blog and this is my first Query on this blog. I would like to dael with graet masters on linux.
Here we go,
After storage people created the LUN, How to add that LUN to Linux server. (Make that LUN visibility on linux server.) ?
How to view the LUN... (5 Replies)
Discussion started by: abhay1983
5 Replies
9. Linux
Hi
I am not familiar with the linux, but I was asked to create a file system on a LUN from the NetApp that was mapped to the linux server.
The server is runing:
uname -a
Linux localhost.localdomain 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
and now... (6 Replies)
Discussion started by: fretagi
6 Replies
LEARN ABOUT CENTOS
thin_metadata_size
THIN_METADATA_SIZE(8) System Manager's Manual THIN_METADATA_SIZE(8)
NAME
thin_metadata_size - thin provisioning metadata device/file size calculator.
SYNOPSIS
thin_metadata_size [options]
DESCRIPTION
thin_metadata_size calculates the size of the thin provisioning metadata based on the block size of the thin provisioned devices, the size
of the thin provisioning pool and the maximum number of all thin prisioned devices and snapshots. Because thin provisioning pools are
holding widely variable contents, this tool is needed to provide sensible initial default size.
-b, --block-size BLOCKSIZE[bskKmMgGtTpPeEzZyY]
Block size of thin provisioned devices in units of bytes,sectors,kilobytes,kibibytes,... respectively. Default is in sectors with-
out a block size unit specifier. Size/number option arguments can be followed by unit specifiers in short one character and long
form (eg. -b1m or -b1megabytes).
-s, --pool-size POOLSIZE[bskKmMgGtTpPeEzZyY]
Thin provisioning pool size in units of bytes,sectors,kilobytes,kibibytes,... respectively. Default is in sectors without a pool
size unit specifier.
-m, --max-thins #[bskKmMgGtTpPeEzZyY]
Maximum sum of all thin provisioned devices and snapshots. Unit identifier supported to allow for convenient entry of large quanti-
ties, eg. 1000000 = 1M. Default is absolute quantity without a number unit specifier.
-u, --unit {bskKmMgGtTpPeEzZyY}
Output unit specifier in units of bytes,sectors,kilobytes,kibibytes,... respectively. Default is in sectors without an output unit
specifier.
-n, --numeric-only [short|long]
Limit output to just the size number with the optional unit specifier character/string.
-h, --help
Print help and exit.
-V, --version
Output version information and exit.
EXAMPLES
Calculates the thin provisioning metadata device size for block size 64 kilobytes, pool size 1 terabytes and maximum number of thin provi-
sioned devices and snapshots of 1000 in units of sectors with long output:
thin_metadata_size -b64k -s1t -m1000
Or (using the long options instead) for block size 1 gigabyte, pool size 1 petabytes and maximum number of thin provisioned devices and
snapshots of 1 million with numeric only output in units of gigabytes:
thin_metadata_size --block-size=1g --pool-size=1p --max-thins=1M --unit=g --numeric-only
Same as before (1g,1p,1M,numeric-only) but with unit specifier character appended:
thin_metadata_size --block-size=1giga --pool-size=1petabytes --max-thins=1mebi --unit=g --numeric-only=short
Or with unit specifier string appended:
thin_metadata_size --block-size=1giga --pool-size=1petabytes --max-thins=1mebi --unit=g -nlong
DIAGNOSTICS
thin_metadata_size returns an exit code of 0 for success or 1 for error.
SEE ALSO
thin_dump(8) thin_check(8) thin_repair(8) thin_restore(8) thin_rmap(8)
AUTHOR
Joe Thornber <ejt@redhat.com>
Heinz Mauelshagen <HeinzM@RedHat.com>
Red Hat, Inc. Thin Provisioning Tools THIN_METADATA_SIZE(8)