2017-06-08 08:05 AM
When I click the button "Expand Disk..." to expand the lun with SnapDrive GUI, I got following error:
Unable to reseize disk. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
SnapDrive Version: 7.1.4
OS: Windows Server 2016
Volume for the LUN is 250GB large.
::> lun show -vserver xx -lun userdblog_L.lun -instance
Vserver Name: xx
LUN Path: /vol/xx__usrdblog_01/q_userdblog/userdblog_L.lun
Volume Name: xx__usrdblog_01
Qtree Name: q_userdblog
LUN Name: userdblog_L.lun
LUN Size: 150.0GB
OS Type: windows_2008
Space Reservation: enabled
Serial Number: ds/ea4q8-Ed8
Serial Number (Hex): 64732f65613471382d456438
Space Reservations Honored: false
Space Allocation: disabled
LUN UUID: 55799008-8d97-4c84-b780-51ae83a5952c
Block Size: 512
Device Legacy ID: -
Device Binary ID: -
Device Text ID: -
Read Only: false
Fenced Due to Restore: false
Used Size: 139.3GB
Maximum Resize Size: 1.47TB
Creation Time: 4/24/2015 16:16:46
Node Hosting the LUN: xx
QoS Policy Group: -
Caching Policy Name: -
Clone Autodelete Enabled: false
Inconsistent Import: false
Solved! SEE THE SOLUTION
2017-06-09 04:24 AM
Which type of LUN is that one?
Is this a dynamic disk?
Looks like a kind of comunication issue between the windows machine and the virtual environemtn (i guess this is an RDM lun). Did you already try to restart the SD service?
2017-06-13 03:14 AM - edited 2017-06-13 03:15 AM
Rebooting the Windows-Server solved the problem.
From SnapDrive created LUN's should be never changed with other tools like OnCommand System Manager or windows disk management.
These LUN's have have a special disk geometry from SnapDrive.
Example: Resizing a Snapdrive-LUN with OnCommand System Manager create huge "busy" snapshots in a Snapmirror-Relationship, that cannot be deleted!
2017-06-13 03:48 AM
Thanks for the hin but i've never heard of one special disk geometry from SnapDrive.
But my lun initial not created with snapdrive, that could be the rasion i have not seen any issues.