way back in the mists of time, we adjusted filesystem properties for our win32 VMs to disable indexing on the E drive, as well as the equivalent of turning off "noatime". This doesn't seem to be the case on this ix box, and I fear on other ix slaves as well. we should a) make sure our ix slaves have E: properly configured b) make sure our imaging process preserves this
Same on win32-ix-ref and w32-ix-slave10 and 11, based on the Properties of the E drive having indexing enabled, and the output of fsutil behavior query disable8dot3 fsutil behavior query disablelastaccess on an administrator temirnal session. But the 'Indexing Service' appears to be disabled in the list of services, and both C:\System Volume Information and the same on E:\ appear to be empty. So I think we just want the two NTFS tweaks, which can probably be done using OPSI.
OS: Linux → Windows Server 2003
Priority: -- → P3
Hardware: x86_64 → x86
Summary: w32-ix-slave34's E drive has indexing enabled → w32-ix-* E drives should have last access time and 8dot3 filenames disabled
Created attachment 557259 [details] [diff] [review] Disable 8dot3 and lastaccess
Attachment #557259 - Flags: review?(bhearsum)
Comment on attachment 557259 [details] [diff] [review] Disable 8dot3 and lastaccess Do we need to specify a drive here, or change to it or something? Or is this global?
Attachment #557259 - Flags: review?(bhearsum) → review+
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.