snyderkv
asked on
VMware RDM lun out of space?
EE,
I'm having a hard time determining where my out of space issues on my RDM file server lun are coming from. Here are the results of df -h on my storage server.
RDM_vol = 7TB Total 7TB used
RDM_lun = 5TB occupied
File Server windows OS shows 1TB on that RDM attached lun
The mapping resides on a VMFS datastore with 50% free space. Everything is thin provisioned
So does the problem have to do with space reclamation? I didn't think that would be effective because fileservers always grow and never shrink thus the size should reflect the real size. Is there an alternative other then installing snapdrive?
Thanks again in advance
I'm having a hard time determining where my out of space issues on my RDM file server lun are coming from. Here are the results of df -h on my storage server.
RDM_vol = 7TB Total 7TB used
RDM_lun = 5TB occupied
File Server windows OS shows 1TB on that RDM attached lun
The mapping resides on a VMFS datastore with 50% free space. Everything is thin provisioned
So does the problem have to do with space reclamation? I didn't think that would be effective because fileservers always grow and never shrink thus the size should reflect the real size. Is there an alternative other then installing snapdrive?
Thanks again in advance
ASKER
Yes the RDM is attached via vSphere ESXi 5.5 and the windows operating system obviously sees it as a 5TB lun as it is directly attached to the guest VM. The RDM is also in physical mode but that doesn't matter.
The OS sees 1TB but the vol status -v RDM_lun shows 5TB occupied. I don't get it. Any other caveats? Otherwise, I'm going to snapdrive and reclaim space to see if that helps. Looks like VSC only works with NFS datastores so I can't use that.
The OS sees 1TB but the vol status -v RDM_lun shows 5TB occupied. I don't get it. Any other caveats? Otherwise, I'm going to snapdrive and reclaim space to see if that helps. Looks like VSC only works with NFS datastores so I can't use that.
If the NTFS 5TB drive has been formatted as 5TB, it will occupy 5TB.
I would attach directly via Microsoft iSCSI initiator, and use Snapdrive in the VM.
I would attach directly via Microsoft iSCSI initiator, and use Snapdrive in the VM.
ASKER
Even if it's thin provisioned?
ASKER
Even so, you can see the RDM volume is 7TB. 5TB should not offline the volume. Where is the extra 2TB going? The more time passes the more I forget about the situation so I might just have to close the thread.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
200g of snapshots and snapshot autodelete is enabled with defaults.
df -h reports 7TB used all it has in it is the 5TB lun plus 200gb snapshot. I may have missed something. I fixed it too quickly by increasing the size of the volume unfortunately so now I just can't see anything unsuaul
df -h reports 7TB used all it has in it is the 5TB lun plus 200gb snapshot. I may have missed something. I fixed it too quickly by increasing the size of the volume unfortunately so now I just can't see anything unsuaul
ASKER
I'm wondering if the volume offlined for some other reason now. Anyways closing thread
We have our volumes set to Autogrow to prevent LUNs going OFFLINE.
Back in the LAB tomorrow, so I'll try some examples, with 7TB volume, and 5TB LUN, RDM to VM.
Back in the LAB tomorrow, so I'll try some examples, with 7TB volume, and 5TB LUN, RDM to VM.
ASKER
Ok let me know of any interesting findings but don't sweet it. I may not have all the informaiton needed to provide you a starting point for troubleshooting. All I know for now is that I have 9TB volume that says 7TB used. The LUN shows 5TB occupied when I run lun show -v <volume>. Snaps = 200GB on that volume with 0% reserve. Here are the errors in the log file
vol is full (using or reserving 99% of space and 0% of inodes, using 99% of reserve).
Deleting snapshot 'hourly.0' in volume vol' to recover storage
Snap Delta hourly.1 hourly.0 114180092kb = 200gb
Even with Autodelete, it seemed to have went offline? But my eyes weren't on it when it was recovered so I may not have all the details.
vol is full (using or reserving 99% of space and 0% of inodes, using 99% of reserve).
Deleting snapshot 'hourly.0' in volume vol' to recover storage
Snap Delta hourly.1 hourly.0 114180092kb = 200gb
Even with Autodelete, it seemed to have went offline? But my eyes weren't on it when it was recovered so I may not have all the details.
ASKER
I meant 7TB volume
And you don't need a 7tb volume if you were going to play with it. It could be a 7gb volume and 5gb store. Oh I have vsim on my laptop so I'll see what I can find.
And you don't need a 7tb volume if you were going to play with it. It could be a 7gb volume and 5gb store. Oh I have vsim on my laptop so I'll see what I can find.
ASKER
Deleting snapshot 'hourly.0' in volume 'vol' to recover storage
Insufficient space on volume 'vol" to perform operation. 64.0KB was requested but only 8.00KB was available.
LUN 'vol/rdm' has run out of space
LUN rdm has been taken offline
Here is the rest of the errors. You can see snapshot autodelete just deleted a snapshot before the rdm went offline. The RDM itself is 1TB on the windows filesystem and shows 5TB occupied on netApp "being an RDM" Autogrow was on but grew to it's max size. Audodelete settings are on default. I'll lab it tonight.
Insufficient space on volume 'vol" to perform operation. 64.0KB was requested but only 8.00KB was available.
LUN 'vol/rdm' has run out of space
LUN rdm has been taken offline
Here is the rest of the errors. You can see snapshot autodelete just deleted a snapshot before the rdm went offline. The RDM itself is 1TB on the windows filesystem and shows 5TB occupied on netApp "being an RDM" Autogrow was on but grew to it's max size. Audodelete settings are on default. I'll lab it tonight.
ASKER
Quitting on this since my Ontap vsims crashed again. But what I did learn is that sis stores a copy of metadata in the volume and could have had stuff there as well as snaps. Also could have been fragmentation or free blocks. Maybe reallocation and reclamation would have helped. Anyways, moving on.
Is the LUN 5TB ?
How is this connected to the VM?
directly via Software iSCSI in the VM or via RDM through vSphere ESXi ?
So the size of RAW disk presented to VM, is also 5TB ?