Hello AFPers,
Hope someone can help… One of my users called me about a DVD taking forever to burn, remoting to his screen I was a little surprised to see the folder he was trying to burn reported as 6EB (actually reported as 6,654,841TB in the finder).
A short discussion later it was decided that seeing as the files weren’t actually required after all and seemed to be corrupt they were pitched into the trash, this quickly locked his Finder up, then his Mac etc.
About this time I started worrying about exactly how the Server would go about deleting several million TB off a 1.5TB RAID, not for long though as seconds later the server crashed & restarted, then froze before hitting the login screen.
I talked the client through force shutting down the server, restarted it again, then inspected the problem files in the finder and terminal:
Enclosing Folder now down to a paltry 4.6TB (only three times the size of the RAID it sits on), it contains 2 files: a 280MB autocad DWG and a 1.6MB autocad BAK.
Files can be moved to another folder which then reports the same massive size, leaving the original folder at zero K. problem file is the DWG, which still seems to have a hidden 4.6TB attached to it somehow.
Anyway, while I pondered this the server kernal paniced then restarted itself, freezing during startup as earlier. I had the user shut everything down, wait a bit, then power things up one by one. I gave him strict instructions not to even look at the dodgy file. That was an hour ago and he’s not called back, looks like I’ll be going onsite tomorrow to check it out regardless.
Does anyone have any experience, ideas or theories as to what’s going on and whether I should do anything more sophisticated/kinky than rm’ing that naughty file when I get there?
Server is a G5, running 10.4.9 server unlimited.
RAID is external, 6 SATA drives connected to an Areca ARC-1120ML Card.
~30 users, 9:1 ratio Mac to PC, although most Mac’s are running Autocad in parallels.
.
.
Comments are closed