Re: Exchange Server defrag (defragmenting), repair very slow with ESEUTIL, ISINTEG
- From: Martin Chisholm [MSFT] <martinc@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 26 Jan 2006 21:08:18 +0000 (UTC)
I'm glad you mentioned Exchange 2000, it gives me a good idea about
the vintage of it. In Exchange 2003 ESE will write an event to the
envent log if an IO operation takes a long time (not present in 2000).
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. If it did do this for every write,
things would become quite slow. It will update the size value if the
volume is flushed (FlushFileBuffers() ), but this is an expensive
operation so ESE tries to avoid calling it unless necessary.
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.
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.
I just took a very quick look at how the progress bar is updated with
the current code (it should be the same for 2000), and I think it's
only updated once per database table. Although each mail folder in
Outlook corresponds to a table, there are some incredibly large tables
like the message table. My guess is that it looked like it was stuck
at 4% because it was defragmenting one of those large tables.
-martin
Boring-but-necessary-disclaimer: This posting is provided "AS IS" with
no warranties, and confers no rights.
In article <MPG.1e404921ce418f4a98969d@xxxxxxxxxxxxxxxxxxxx>,
Michael Salem <newsms.nospam@xxxxxxxxxx> wrote:
>
>(Followup to my post "Defrag very very slow?")
>
>Summary: ESEUTIL may seem to be hung with no signs of progress, but it
>may simply be taking its time.
>
>Following some trouble with ESEUTIL after a routine Exchange Server 2000
>problem, I'll make some comments that might help others who find this
>posting as the result of a search.
>
>I ran the off-line ESEUTIL on a 16GB Exchange Server database (default
>name PRIV1.EDB). It ran for a few hours. At first it showed no dots on
>the progress bar; after some time (not hours), one and then two dots
>appeared (4 percent?). When checking the sizes of the output files in a
>My Computer window, they increased for a while, then remained steady at
>about 1GB. After relatively fast progress to the 1GB/2 dots mark, there
>was no sign of progress for many hours (8 hours?).
>
>I aborted processes a couple of times after several hours of no visible
>progress. Later, I made a run over a weekend. Initial progress was as
>before, but after leaving ESEUTIL to run for a longer period, it had
>completed when I checked about 9 hours after starting. I wasn't
>watching, so don't know when and how the progress indicators woke up.
>I'm not sure of the hardware configuration; a fairly old dual-CPU
>machine with, I think, 7200 or 10000 rpm RAID5 SCSI drives.
>
>I had similar behaviour with ISINTEG.EXE
>
>Unfortunately I can't give any detailed observations or precise times,
>but do be aware that ESEUTIL.EXE can behave this way, and give it lots
>of time before giving up. I don't know if the same holds for ESEUTIL as
>supplied with Exchange Server 2003 or other versions.
>
>I've posted this message for those who might find it as the result of a
>search; if anyone has anything to add, supporting, contradicting, or
>clarifying this message even after a long time, it may be worth posting
>a followup.
>
>Best wishes,
>--
>Michael Salem
.
- Follow-Ups:
- References:
- Defrag very very slow?
- From: Michael Salem
- Exchange Server defrag (defragmenting), repair very slow with ESEUTIL, ISINTEG
- From: Michael Salem
- Defrag very very slow?
- Prev by Date: Event 12003 fills 1MB Event Log in 4 sec's
- Next by Date: Re: ESEUTIL /g error -1206 (JET_errDatabaseCorrupted.....)
- Previous by thread: Exchange Server defrag (defragmenting), repair very slow with ESEUTIL, ISINTEG
- Next by thread: Re: Exchange Server defrag (defragmenting), repair very slow with ESEUTIL, ISINTEG
- Index(es):
Relevant Pages
|
Loading
