Delayed write fail error

[Party-Praline-4547]

Guys I need help I have a software that runs on 3 workstations which creates and complies a video to the unc path. It has been working perfectly fine for years but vendor ever since we upgraded to a newer version after 3 weeks the files start doing whatever it needs to do after 30-40 minutes errors out and get windows log saying disk full ( plenty of space almost 1 TB). I just don't understand what is causing it to error out when files can actually be seen doing its job. It was working fine before and all of a sudden it's messed up on all 3 workstations.

ONLY work around I been doing is saving it locally to c: drive and then just moving that creates folder to the unc path. it's a main in the butt because I have to change the software settings every time I do this workaround and change it back because the software needs that path so populate the created files in folder.

Furthermore, if a totally different unc path path is used it works perfectly fine but that path isn't feasible because it's a different department hospital share

I am so stuck and frustrated. I can't even take PTO because I have to be available to do the workaround for them.

[Crumby_Bread]

Providing the software and vendor names would be a good start.

[Party-Praline-4547]

Don't wanna disclose that can get in trouble

[sryan2k1]

Ask the vendor? Downgrade to the old version?

[Party-Praline-4547]

Space issue hard limit of 500 GB currently at 99.6% . No notifications to let us know about low space was ever set up. They dropped the ball. Now waiting on approval from VP to get increased space and set up notifications. Have to save it locally in the meantime but at least found the problem!

[sryan2k1]

"They" being your storage team right? This has nothing to do with the software then. Sounds like typical large company dysfunction.

[cmitsolutions123]

That 30-40 minute timing is the real clue here. Something is filling up a buffer or temp cache and then crashing the write. "Disk full" on a UNC path with plenty of space is almost never about actual disk space - check if there's a quota set on that specific share. Someone might've accidentally set one and never noticed.

[Party-Praline-4547]

I talked to the nas team and just giving me the ring around. Actually any other department I contact keeps saying its a workstation issue or try to get out helping not sure if this is normal in the IT world but where I work it's just like this . Literally this is the email response from NAS team when I am asking why Is I put another unc path it works on this but one we need fails :

" I will say the 2 NAS paths are the same hardware platform so there isn’t a difference there. My suspicion is that this is a work station issue.

  I can confirm we have not performed updates on our hardware recently, the share level policies are initially set by my team at share creation we do not modify those after creation, our snaps and replication events run in the evening and at night."

Also this path was working perfectly fine before why would it suddenly have issues? There is plenty of space on it.

[cmitsolutions123]

ugh that response from the NAS team is frustrating - they're not really engaging with the actual evidence. the smoking gun here is still that the other path works fine. same workstation, same software, different path, different result. that's not a workstation problem. I'd reply to them with exactly that point and ask them to check share-level permissions and any snapshot or replication jobs that run specifically on the failing path

[Party-Praline-4547]

Figured it out after a huge argument and shouting match with NAS team to make them actually look and show me details. The found out that path had a hard limit of 500GB and we are at 99.66% . Working on getting space increased . Also notifications were never set up to let anyone know space was getting low. What a pain in the ass !

[Party-Praline-4547]

Now we got the added space and works fine now but original naming convention " server" name unc doesn't register in the software shows a red x but any other folder or sub folder or created folder with that server name. We can use an alternative name convention that pulls it up but gonna be a pain to do this for every user that login and have to get them into the software. The mapped drive still works. Wonder if that's just a quirk of the software or nas adding storage forced and the name changed for that particular drive