NickF
Guru
- Joined
- Jun 12, 2014
- Messages
- 763
In the UI in TN you are exposed several options which are not exposed in volume creation wizard in TrueCommand
Notably, I almost always use Sparse and Force when I am building an iSCSI LUN for VMWare or Windows to talk to. Those options are not present here:
When trying to make a 400GiB iSCSI LUN following the Wizard in TC below:
I get this error:
I should be able to bypass this with a tooltip warning
I should also be able to make it thin:
There’s also literally no point to dedupe and compression if these features are not available…And Those features should also be available?
lol @morganL I'm at it again...
ixsystems.atlassian.net
Also nothing stops me from making one bigger after the fact:
And TC isn't even aware that I did that
So now, I have a 400GiB LUN mapped and formatted in windows:
When only 1 of the 3 nodes can actually provide a backing LUN that is 400GiB
So...I made a file that was huge and over 300
I turned off the node I made bigger than 300 GiB
The other nodes think its still 300 GiB
And then the drive gets disconnected
Interesting. At least it's not going to let me write data to never never land.
After restarting TC becomes aware that the LUN us bigger on one than the other:
ISCSI is stopped on that node:
I can start it:
I'm home with COVID. I'm going to try and break more things.....
https://ixsystems.atlassian.net/browse/TC-2613
Made the rest of them bigger now, and Turned off the original node I messed with.
Now the disk is uninitialized as if I had never written data to it. Data loss is possible here
Notably, I almost always use Sparse and Force when I am building an iSCSI LUN for VMWare or Windows to talk to. Those options are not present here:
When trying to make a 400GiB iSCSI LUN following the Wizard in TC below:
I get this error:
I should be able to bypass this with a tooltip warning
I should also be able to make it thin:
There’s also literally no point to dedupe and compression if these features are not available…And Those features should also be available?
lol @morganL I'm at it again...
Log in with Atlassian account
Log in to Jira, Confluence, and all other Atlassian Cloud products here. Not an Atlassian user? Sign up for free.
Also nothing stops me from making one bigger after the fact:
And TC isn't even aware that I did that
So now, I have a 400GiB LUN mapped and formatted in windows:
When only 1 of the 3 nodes can actually provide a backing LUN that is 400GiB
So...I made a file that was huge and over 300
I turned off the node I made bigger than 300 GiB
The other nodes think its still 300 GiB
And then the drive gets disconnected
Interesting. At least it's not going to let me write data to never never land.
After restarting TC becomes aware that the LUN us bigger on one than the other:
ISCSI is stopped on that node:
I can start it:
I'm home with COVID. I'm going to try and break more things.....
https://ixsystems.atlassian.net/browse/TC-2613
Made the rest of them bigger now, and Turned off the original node I messed with.
Now the disk is uninitialized as if I had never written data to it. Data loss is possible here
Last edited:
