September 28, 201510 yr Upgraded this weekend from 5.0.6 to 6.1.3. Having an issue with share minimum free space setting and cache drive use. IIRC, in 5.0.6 the share minimum free space setting only affected the array drives and had no effect on the cache drive (share set to use cache). In 6.1.3, I have the settings of share 'minimum free space' of 200GB (as I had on 5.0.6) on several shares and my current cache drive free space is ~175GB. When I write to those shares that have a min free space setting of 200GB syslog reports "shfs/user: share cache full" and it writes the data directly to the array. If I reduce the share min free to a lower number than 175GB the new data will go to the cache drive. Is this a 'new normal' behavior or a bug? In 5.0.6, data would be written to the cache drive until the drive was really out of space, then it would go to the array. I had used the min free space setting and the split levels in 5.0.6 to keep a set minimum amount of free space on any one array data drive so that no one drive would go completely full. tower-diagnostics-20150928-0012.zip
Archived
This topic is now archived and is closed to further replies.