This message was deleted.
# microsoft-fslogixs
Slackbot
02/19/2020, 4:19 PMThis message was deleted.
b
Brandon Mitchell
02/19/2020, 4:49 PMWe have some o365 containers on our Isilon without issue however we’re moving those workloads to NetApp.
n
Nick Panaccio
02/19/2020, 5:26 PMI ask because the only people I've found using Isilon are in this thread: https://social.msdn.microsoft.com/Forums/en-US/8afb3426-a214-4d27-8bc2-9cfcae6c9592/fslogix-not-creating-vhdx-volume-type?forum=FSLogix. Not exactly inspiring...
r
Ray Davis
02/19/2020, 5:32 PMIts only been thoughts over here. Waiting you u to test it lol
n
Nick Panaccio
02/19/2020, 5:32 PMIf we go with EMC, I'll be forced to go that route instead of VMware and S16/CA.
Nick Panaccio
02/27/2020, 6:51 PMSounds like EMC resolved that issue with .vhdx containers:
After working a bit further with support we were able to identify the issue and mount .vhdx files using Isilon from Windows 10 and Server 2016 clients. We had to upgrade to a later version of OneFS which included a fix for the following. We are currently running 8.2.1 with the February (02/2020) UDA patch.
The issue is listed as Bug 259538 - : Incorrect response to FileFsSizeInformation request from SMB client.
Nick Panaccio
02/27/2020, 6:51 PMGood to know, since that's the route it looks like we're going as of today.
r
Ray Davis
02/28/2020, 1:36 AMOh this is great news man.