![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I'm working with a Windows "server" here, as a front-end to a SAN. On this *shiver* ntfs SAN is a directory with thousands of lost files. Our direction: Find out where they go, and put them there.
The three of us are unix geeks, and we knew we could do this with shell scripts and simple unix commands. None of us are DOS guys. The SAN is mapped to two servers, the production and the test. We were not to touch the prod server, and told not to break the test server. Hmmm.
Because we all knew this would be so much easier with unix, I turned to a tool I had never used before - but didn't want to install it on the test server, and access it via Terminal Server...just in case. The local IT guy added my laptop to the local domain, mapped the SAN drives directly to it, and I installed cygwin. I now had a unix commands I could run against windows files! I feel alive again; using unix to troubleshoot difficult issues.
As great as this news was, it uncovered some unsettling information. Running our commands, we identified several sub-directories in which were identically named files of different sizes. At long last, I settled on a recursive long-listing of every file in the main directory. Because the size difference of these files were significant, I was hoping the long list, if sorted by size, would reveal what the majority of these file sizes were - so we could choose the correct one, and dismiss the other. That's when a planned power-outage had the unfortunate side-effect of removing our access to the server. So here we sit.
In other news, my boss referred to us to as "Team Daedalus" (from Space Cowboys) when he introduced us to the Regional CIO. I couldn't believe it.
The three of us are unix geeks, and we knew we could do this with shell scripts and simple unix commands. None of us are DOS guys. The SAN is mapped to two servers, the production and the test. We were not to touch the prod server, and told not to break the test server. Hmmm.
Because we all knew this would be so much easier with unix, I turned to a tool I had never used before - but didn't want to install it on the test server, and access it via Terminal Server...just in case. The local IT guy added my laptop to the local domain, mapped the SAN drives directly to it, and I installed cygwin. I now had a unix commands I could run against windows files! I feel alive again; using unix to troubleshoot difficult issues.
As great as this news was, it uncovered some unsettling information. Running our commands, we identified several sub-directories in which were identically named files of different sizes. At long last, I settled on a recursive long-listing of every file in the main directory. Because the size difference of these files were significant, I was hoping the long list, if sorted by size, would reveal what the majority of these file sizes were - so we could choose the correct one, and dismiss the other. That's when a planned power-outage had the unfortunate side-effect of removing our access to the server. So here we sit.
In other news, my boss referred to us to as "Team Daedalus" (from Space Cowboys) when he introduced us to the Regional CIO. I couldn't believe it.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
(no subject)
You know the balding blind one.
(no subject)
(no subject)
No, that was Scurvydurx I hate the bolshevicks!!!!
(no subject)
(no subject)
(no subject)
Did you tell him about your post?
(no subject)
(no subject)
Thanks. :)
(no subject)
(no subject)
me want to watch it again. :)
(no subject)
(no subject)