Re: Question on Mac files on a Windows 2003 Server
- From: "Jim Seifert [MSFT]" <jimsei@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 23 May 2005 08:06:44 -0700
The volume index size is the size of the index file - it is larger the more
files you have in a volume. Over say 300k files in a volume makes a large
index file that will likely require a rebuild on reboot. Based on your list
I suspect the backup program is touching the files after the Macfile service
shuts down on a reboot resulting in a mismatch and index rebuild on restart.
There is nothing wrong with the index rebuilds, it will take a little more
time but does not impact the files.
--
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Adam Raff" <adam@xxxxxxxxxxxxxxxx> wrote in message
news:%23eqP7cYXFHA.3228@xxxxxxxxxxxxxxxxxxxxxxx
>
> Hi Jim,
>
> Thanks for respond back to me on this.
>
> To answer your question No. The Mac people seem to be able to get into
> the files with no issue. What bothers me is that it seems to be all over
> and random when it comes to files. It seems to be affecting from what the
> log file says even users files that don't use the Mac just PC.
>
> So would you recommend a reboot of the server just to see what happens?
>
> What do you mean by Volume index size?
>
> We are using Trend Antivirus and had no issues with it.
>
> We use Vertas backup with Open file option and have had no issues with
> that either
>
> Thanks
> Adam Raff
>
> "Jim Seifert [MSFT]" <jimsei@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:O$hbb9VXFHA.2348@xxxxxxxxxxxxxxxxxxxxxxx
>> This looks like index files for the various volumes is corrupt and being
>> rebuilt on reboot. The index file is a mapping of the file and resource
>> forks present in the Mac file system but not in the NTFS file system.
>> Previous releases of Windows Server have rebuilt this index every time
>> the machine was rebooted and this can make reboots take a very long time
>> to complete. There are a number of things that can cause this index
>> corruption to be reported: 1.) Antivirus program activity. 2.) Open
>> files on shutdown. 3.) Disk errors 4.) Volume index size. - this list
>> probably isn't complete but should be the main suspects. The easiest
>> one to address is the open files on reboot. Just making sure the all
>> sessions are closed can help. Are you having any problems with the
>> shared volumes or access?
>> --
>> Please do not send e-mail directly to this alias. This alias is for
>> newsgroup purposes only.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Adam Raff" <adam@xxxxxxxxxxxxxxxx> wrote in message
>> news:uk40L$HXFHA.2996@xxxxxxxxxxxxxxxxxxxxxxx
>>> Good Day,
>>>
>>> I hope somebody here can shed some light on some things for me. First I
>>> would like to give you some history on my problem
>>>
>>> We have two Mac running OS 10.3 they are connected to our domain which
>>> is a Windows 2003. We started out on a Windows NT4.0 went to 2K and now
>>> we are up to Windows 2003. A Mac Volume was created on our NT4.0 server
>>> and it seemed to move over to 2000 fine.
>>>
>>> During Boots on the 2000 server I would get a warning saying that I may
>>> be over the limit on files and I may have connectivity issues because of
>>> the amount of files
>>>
>>> These errors would come up every time I would Boot the server ( and
>>> Reboot). The clients from what I understood never had any issues
>>> connecting.
>>>
>>> When we upgraded to 2003 I started getting new errors which are as
>>> follows ( I have placed four examples here for you to look at)
>>> -----------------------------------------------------------------------
>>> Event Type: Error
>>>
>>> Event Source: MacFile
>>>
>>> Event Category: None
>>>
>>> Event ID: 12042
>>>
>>> Date: 5/18/2005
>>>
>>> Time: 5:47:29 PM
>>>
>>> User: N/A
>>>
>>> Computer: HSMAIN
>>>
>>> Description:
>>>
>>> Internal server information for file "\S Drive\Production &
>>> Traffic\Production\Micah\Micah Quotes\49731200:AFP_AfpInfo"
>>>
>>> was corrupted. Setting default information.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> Data:
>>>
>>> 0000: 35 01 04 00 00 00 00 00 5.......
>>>
>>>
>>>
>>>
>>>
>>> Event Type: Error
>>>
>>> Event Source: MacFile
>>>
>>> Event Category: None
>>>
>>> Event ID: 12042
>>>
>>> Date: 5/18/2005
>>>
>>> Time: 4:31:56 PM
>>>
>>> User: N/A
>>>
>>> Computer: HSMAIN
>>>
>>> Description:
>>>
>>> Internal server information for file "\S Drive\Compcomg\Finance\Shared
>>> Files\Job File\4E74A100:AFP_AfpInfo"
>>>
>>> was corrupted. Setting default information.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> Data:
>>>
>>> 0000: 35 01 04 00 00 00 00 00 5.......
>>>
>>>
>>>
>>>
>>>
>>> Event Type: Error
>>>
>>> Event Source: MacFile
>>>
>>> Event Category: None
>>>
>>> Event ID: 12042
>>>
>>> Date: 5/18/2005
>>>
>>> Time: 3:08:02 PM
>>>
>>> User: N/A
>>>
>>> Computer: HSMAIN
>>>
>>> Description:
>>>
>>> Internal server information for file "\S Drive\Creative
>>> Department\Artcommg\Art Folder\1-Creative Dept Files
>>>
>>> (3D Studio Max)\2005\01-template\Design\Freelancer:AFP_AfpInfo" was
>>> corrupted. Setting default information.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> Data:
>>>
>>> 0000: 35 01 04 00 00 00 00 00 5.......
>>>
>>>
>>>
>>>
>>>
>>> Event Type: Error
>>>
>>> Event Source: MacFile
>>>
>>> Event Category: None
>>>
>>> Event ID: 12042
>>>
>>> Date: 5/17/2005
>>>
>>> Time: 4:14:39 PM
>>>
>>> User: N/A
>>>
>>> Computer: HSMAIN
>>>
>>> Description:
>>>
>>> Internal server information for file "\S Drive\Production &
>>> Traffic\Production\Micah\Micah Quotes\AB4A9100:AFP_AfpInfo"
>>>
>>> was corrupted. Setting default information.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> Data:
>>>
>>> 0000: 35 01 04 00 00 00 00 00 5.......
>>>
>>> ---------------------------------------------------------------
>>>
>>>
>>>
>>> As you can see all the errors have the same ID number and event source
>>> and I have looked them up on the web most of the errors point to Windows
>>> NT so I am stumped on what to do or even how to do it.
>>>
>>>
>>>
>>> So here are my questions
>>>
>>>
>>>
>>> What is the MacVol on Windows 2003, can somebody give me a little
>>> information on what it does or point me somewhere where I can find info
>>> on it?
>>>
>>>
>>>
>>> What is the amount of files that a Windows 2003 Enterprise Server can
>>> handle when it comes to the Mac and or MacVol
>>>
>>>
>>>
>>> Has anybody ever seen this and if so how do I fix this problem
>>>
>>>
>>>
>>> Is this a problem or just information that the server is giving me in
>>> 2003
>>>
>>>
>>>
>>> Any advise would be much appreciated
>>>
>>>
>>>
>>> Thank You
>>>
>>> Adam Raff
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
.
- Follow-Ups:
- Re: Question on Mac files on a Windows 2003 Server
- From: Adam Raff
- Re: Question on Mac files on a Windows 2003 Server
- References:
- Question on Mac files on a Windows 2003 Server
- From: Adam Raff
- Re: Question on Mac files on a Windows 2003 Server
- From: Jim Seifert [MSFT]
- Re: Question on Mac files on a Windows 2003 Server
- From: Adam Raff
- Question on Mac files on a Windows 2003 Server
- Prev by Date: Re: Mac OS X with Windows 2003 Server
- Next by Date: Re: Question on Mac files on a Windows 2003 Server
- Previous by thread: Re: Question on Mac files on a Windows 2003 Server
- Next by thread: Re: Question on Mac files on a Windows 2003 Server
- Index(es):
Relevant Pages
|