Sponsored Content
Top Forums UNIX for Advanced & Expert Users Linux Thin Lun space reclamation Post 302962155 by Peasant on Wednesday 9th of December 2015 03:27:10 AM
Old 12-09-2015
Hitachi has reclaim zero pages on enterprise level storage (VSP)

This is mostly used in combination with software on the machine.
For instance, with ASM, you can reclaim zero pages from ASM, then reclaim on storage.

A nice document :
https://www.hds.com/assets/pdf/recla...on-utility.pdf

There is an article on RHEL network regarding :
https://access.redhat.com/solutions/45514

It involves creating a lvol with all free space from volume group, dd-ing the lvol with using /dev/zero, removing the lvol, remount with discard and running fstrim.
After that you can reclaim the storage space from storage GUI/command line.

Dunno how would you apply the same on raw volume tho (no VG).

Hope that helps.
Regards
Peasant.

Last edited by Peasant; 12-09-2015 at 04:34 AM..
This User Gave Thanks to Peasant For This Post:
 

9 More Discussions You Might Find Interesting

1. Linux

BOOTP on HP Thin clients

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

volume group space addition after LUN creation

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

Finding SAN Lun's on Linux.

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 LUN ID, how to find disk relate to that LUN ID?

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

using jdbc:thin in bash

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

Grow LUN presented on Linux host

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

Need to mount LUN on two linux boxs (one rw the other ro) caveat details inside

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

adding LUN to linux server

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

Mount a newly added LUN on a GNU/Linux distro

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
Sys::Virt::StorageVol(3)				User Contributed Perl Documentation				  Sys::Virt::StorageVol(3)

NAME
Sys::Virt::StorageVol - Represent & manage a libvirt storage volume DESCRIPTION
The "Sys::Virt::StorageVol" module represents a storage volume managed by libvirt. A storage volume is always associated with a containing storage pool ("Sys::Virt::StoragePool"). METHODS
my $name = $vol->get_name() Returns a string with a locally unique name of the storage vol my $name = $vol->get_key() Returns a string with a globally unique key for the storage vol my $name = $vol->get_path() Returns a string with a locally unique file path of the storage vol my $xml = $vol->get_xml_description() Returns an XML document containing a complete description of the storage vol's configuration $vol->delete($flags) Immediately delete the storage volume freeing its storage resources. The "flags" parameter indicates any special action to be taken when deleting the volume. $vol->resize($newcapacity, $flags=0) Adjust the size of the storage volume. The $newcapacity value semantics depend on the $flags parameter. If $flags specifies "RESIZE_DELTA" then the $newcapacity is relative to the current size. If $flags specifies "RESIZE_SHRINK" then the $newcapacity value is the amount of space to remove $vol->wipe($flags = 0) Clear the data in the storage volume to avoid future information leak. The "flags" parameter is currently unused and defaults to zero. $vol->wipe_pattern($algorithm, $flags = 0) Clear the data in the storage volume to avoid future information leak. The $algorithm parameter specifies the data pattern used to erase data, and should be one of the WIPE ALGORITHM CONSTANTS listed later. The "flags" parameter is currently unused and defaults to zero. my $info = $vol->get_info() Retrieve live information about the storage volume. The returned $info hash reference contains three keys. "type" indicates whether the volume is a file or block device. "capacity" provides the maximum logical size of the volume. "allocation" provides the current physical usage of the volume. The allocation may be less than the capacity for sparse, or grow-on-demand volumes. The allocation may also be larger than the capacity, if there is a metadata overhead for the volume format. $vol->download($st, $offset, $length); Download data from $vol using the stream $st. If $offset and $length are non-zero, then restrict data to the specified volume byte range. $vol->upload($st, $offset, $length); Upload data to $vol using the stream $st. If $offset and $length are non-zero, then restrict data to the specified volume byte range. CONSTANTS
The following sets of constants are useful when dealing with storage volumes VOLUME TYPES The following constants are useful for interpreting the "type" field in the hash returned by the "get_info" method Sys::Virt::StorageVol::TYPE_FILE The volume is a plain file Sys::Virt::StorageVol::TYPE_BLOCK The volume is a block device Sys::Virt::StorageVol::TYPE_DIR The volume is a directory Sys::Virt::StorageVol::TYPE_NETWORK The volume is a network source CREATE MODES The following constants are useful for the "flags" parameter of the "create" method Sys::Virt::StorageVol::CREATE_PREALLOC_METADATA Preallocate header metadata when creating the volume. DELETE MODES The following constants are useful for the "flags" parameter of the "delete" method Sys::Virt::StorageVol::DELETE_NORMAL Do a plain delete without any attempt to scrub data. Sys::Virt::StorageVol::DELETE_ZEROED Zero out current allocated blocks when deleteing the volume WIPE ALGORITHM CONSTANTS The following constants specify the algorithm for erasing data Sys::Virt::StorageVol::WIPE_ALG_BSI 9-pass method recommended by the German Center of Security in Information Technologies Sys::Virt::StorageVol::WIPE_ALG_DOD 4-pass Dod 5220.22-M section, 8-306 procedure Sys::Virt::StorageVol::WIPE_ALG_GUTMANN The canonical 35-pass sequence Sys::Virt::StorageVol::WIPE_ALG_NNSA 4-pass NNSA Policy Letter NAP-14.1-C (XVI-8) Sys::Virt::StorageVol::WIPE_ALG_PFITZNER7 7-pass random Sys::Virt::StorageVol::WIPE_ALG_PFITZNER33 33-pass random Sys::Virt::StorageVol::WIPE_ALG_RANDOM 1-pass random Sys::Virt::StorageVol::WIPE_ALG_SCHNEIER 7-pass method described by Bruce Schneier in "Applied Cryptography" (1996) Sys::Virt::StorageVol::WIPE_ALG_ZERO 1-pass, all zeroes VOLUME RESIZE CONSTANTS The following constants control how storage volumes can be resized Sys::Virt::StorageVol::RESIZE_ALLOCATE Fully allocate the extra space required during resize Sys::Virt::StorageVol::RESIZE_DELTA Treat the new capacity as a delta to the current capacity Sys::Virt::StorageVol::RESIZE_SHRINK Treat the new capacity as an amount to remove from the capacity AUTHORS
Daniel P. Berrange <berrange@redhat.com> COPYRIGHT
Copyright (C) 2006-2009 Red Hat Copyright (C) 2006-2009 Daniel P. Berrange LICENSE
This program is free software; you can redistribute it and/or modify it under the terms of either the GNU General Public License as published by the Free Software Foundation (either version 2 of the License, or at your option any later version), or, the Artistic License, as specified in the Perl README file. SEE ALSO
Sys::Virt, Sys::Virt::Error, "http://libvirt.org" perl v5.16.3 2013-07-30 Sys::Virt::StorageVol(3)
All times are GMT -4. The time now is 10:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy