Prev: scrolling that doesn't accelerate
Next: ok let's try it this way
From: David Empson on 6 Jul 2010 20:10
Wes Groleau <Groleau+news(a)FreeShell.org> wrote:

> On 07-06-2010 12:22, David Empson wrote:
> > I can't think of a reasonable explanation for a file apparently
> > shrinking if you didn't do anything to it.
>
> I don't know much about Entourage, but it's common for a database
> to not do garbage collection until it actually runs out of space.
>
> In this case, it sounds like, "Oh, no, the Admiral's looking around!
> Everybody clean up FAST!"
>
> :-)

But this was a backup copy of the Entourage database, created using
methods outside the scope of Entourage.

The only explanations which occur to me are:

(a) File system corruption.

(b) The Entourage database really did grow to 470-odd GB, was copied by
the backup mechanism. While Nick Naym was investigating where the disk
space went, the backup mechanism happened to run again, copying the
Entourage database again, and in the meantime it had shrunk to a normal
size.

Need more information to know whether (b) is feasible.

(c) Something is seriously screwed up with that backup mechanism.

--
David Empson
dempson(a)actrix.gen.nz
First  |  Prev  | 
Pages: 1 2
Prev: scrolling that doesn't accelerate
Next: ok let's try it this way