Re: Exchange Server defrag (defragmenting), repair very slow with ESEUTIL, ISINTEG
- From: Michael Salem <msnews@xxxxxxxxxx>
- Date: Fri, 27 Jan 2006 01:52:25 -0000
Thanks to Martin Chisholm [MSFT] for his comments on my posting. I had
reported that ESEUTIL appeared to hang with no visible progress, but
eventually did complete after many hours. I'll make a few comments,
without quoting the entire message.
> I'm glad you mentioned Exchange 2000,
I seem to have omitted this vital fact in my original posting, sorry.
> NTFS works in an interesting manner. Even if you're writing to a file
> and making it larger, it will not bother to update the file size
> reported by 'dir' or explorer. ... It will update the size value if the
> volume is flushed (FlushFileBuffers()
> On a volume with other activity (like the OS drive), it's not uncommon
> for some program to call FlushFileBuffers(). But if all you have on
> the volume are Exchange files, then this might not happen.
Useful to know. I had noticed with many prograMS that the file size
reported by Explorer increases by fits and starts, but didn't know why.
The displayed size jumps similarly in FAT32, presumably for the same
reason.
> The bottom line is that in order to see if the file is getting any
> larger, you should look at something different. Like the amount of CPU
> or IO done by eseutil.exe using perfmon, or the IO columns is
> taskmgr. The free space on the volume (from dir) should probably get
> updated as well.
Indeed; but after a few hours you start to think that the program is
stuck in a loop even if executing, maybe generating rubbish output.
> ... I think [the progress bar] is only updated once per database table.
> ... there are some incredibly large tables like the message table.
That explains everything if the message table is a large fraction of the
total database size. It makes a complete nonsense of the "progress" bar.
Best wishes,
--
Michael Salem
.
- References:
- Defrag very very slow?
- From: Michael Salem
- Exchange Server defrag (defragmenting), repair very slow with ESEUTIL, ISINTEG
- From: Michael Salem
- Re: Exchange Server defrag (defragmenting), repair very slow with ESEUTIL, ISINTEG
- From: Martin Chisholm [MSFT]
- Defrag very very slow?
- Prev by Date: Re: Event 12003 fills 1MB Event Log in 4 sec's
- Next by Date: Re: Event 12003 fills 1MB Event Log in 4 sec's
- Previous by thread: Re: Exchange Server defrag (defragmenting), repair very slow with ESEUTIL, ISINTEG
- Next by thread: Exchange 2003 Public folders problem
- Index(es):
Relevant Pages
|