Defrag very very slow?
- From: Michael Salem <msnews@xxxxxxxxxx>
- Date: Fri, 20 Jan 2006 13:15:54 -0000
Exchange Server standard stopped working with errors about the database
exceeding 16GB in size. This is a known issue, and not what I'm asking
about.
I ran ESEUTIL /d /p (this is a defragment, storing the defragmented file
in a specified location instead of overwriting the original; it is not a
true repair like /p). There is plenty of space on the disc for an extra
copy of the database.
The process started; after a couple of hours I had two dots (about 4%)
and the new priv1.edb was about 1 GB (aS shown on a directory listing of
the destination drive). After 6 more hours it had not moved on at all -
I killed the process. I tried this twice; in each case the process
stopped
ESEUTIL /ms runs (in about 6 minutes), and produces what looks like sane
output.
The diagnostic ESEUTIL /G had made has made no visible progress (no
dots) after about an hour.
isinteg -test alltests has run tests 1-6 with no errors reported, and is
hanging at 18% on test 7 (folder).
How long should these processes take on an adequately fast machine (I
don't have the specifications to hand)? I believe the drives are a RAID
5 SCSI array. The machine generally seems to be working OK. I understood
that ESEUTIL should typically process about 4GB/hour.
Best wishes,
--
Michael Salem
.
- Follow-Ups:
- Exchange Server defrag (defragmenting), repair very slow with ESEUTIL, ISINTEG
- From: Michael Salem
- Re: Defrag very very slow?
- From: Eric Tam [MSFT]
- Exchange Server defrag (defragmenting), repair very slow with ESEUTIL, ISINTEG
- Prev by Date: RE: offline defrag using ESEUtil
- Next by Date: Re: Defrag very very slow?
- Previous by thread: Exchange 2000 email process time
- Next by thread: Re: Defrag very very slow?
- Index(es):