Smalltalk › Gemtalk › GLASS

recover from full extent?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

10 messages Options

Johan Brichau-2

recover from full extent?

Hi,

I managed to fill an extent to it's maximum allowed size of 4Gb.
Trying an MFC does not work (see below). Is there a way I can shrink the repository anyway?

Johan

-------
topaz 1> printit
SystemRepository markForCollection
%
-----------------------------------------------------
GemStone: Error Fatal
The Repository is full and can no longer be expanded.,
Error Category: [GemStone] Number: 4002 Arg Count: 1

SeanTAllen

Re: recover from full extent?

You can do a full backup and restore into a virgin extent.

See section 6.6 ( step 3 ) of the attached system administration guide.

On Thu, Nov 18, 2010 at 3:14 PM, Johan Brichau <[hidden email]> wrote:

Hi,

I managed to fill an extent to it's maximum allowed size of 4Gb.
Trying an MFC does not work (see below). Is there a way I can shrink the repository anyway?

Johan

-------
topaz 1> printit
SystemRepository markForCollection
%
-----------------------------------------------------
GemStone: Error Fatal
The Repository is full and can no longer be expanded.,
Error Category: [GemStone] Number: 4002 Arg Count: 1

GS64-SysAdminGuide-2.4.pdf (7M) Download Attachment

SeanTAllen

Re: recover from full extent?

In reply to this post by Johan Brichau-2

You can do a full backup and restore into a virgin extent.

See section 6.6 ( step 3 ) of the system administration guide.

On Thu, Nov 18, 2010 at 3:14 PM, Johan Brichau <[hidden email]> wrote:

Hi,

I managed to fill an extent to it's maximum allowed size of 4Gb.
Trying an MFC does not work (see below). Is there a way I can shrink the repository anyway?

Johan

-------
topaz 1> printit
SystemRepository markForCollection
%
-----------------------------------------------------
GemStone: Error Fatal
The Repository is full and can no longer be expanded.,
Error Category: [GemStone] Number: 4002 Arg Count: 1

Dale Henrichs

Re: recover from full extent?

In reply to this post by Johan Brichau-2

You need a key file with a larger limit ... we had "emergency key files"
with larger limits, but now that the limit has been officially bumped,
you should use a new key file ...

You should be able to download a new keyfile from here:

http://seaside.gemstone.com/etc/

Dale

On 11/18/2010 12:14 PM, Johan Brichau wrote:

> Hi,
>
> I managed to fill an extent to it's maximum allowed size of 4Gb.
> Trying an MFC does not work (see below). Is there a way I can shrink the repository anyway?
>
> Johan
>
> -------
> topaz 1> printit
> SystemRepository markForCollection
> %
> -----------------------------------------------------
> GemStone: Error Fatal
> The Repository is full and can no longer be expanded.,
> Error Category: [GemStone] Number: 4002 Arg Count: 1
>
>

Ramon Leon-5

Re: recover from full extent?

In reply to this post by SeanTAllen

On 11/18/2010 01:26 PM, Sean Allen wrote:
> You can do a full backup and restore into a virgin extent.

I'd just go grab the free 16 gig license and install it; problem solved.

--
Ramon Leon
http://onsmalltalk.com

Johan Brichau-2

Re: recover from full extent?

In reply to this post by SeanTAllen

Thanks Dale for the pointer to the new key files.

Sean: do you mean I can skip the first 2 steps? Because that procedure is exactly what I was trying to do but the MFC did not want to go ahead (probably it needs extra space for the GC itself).

btw, it's OK to tell me the extent is doomed ;-) It's the result of running 20 times about a 1000 unit tests in SeasideTesting that each reset my entire 'test db'. I guess that at least means that SeasideTesting for Gemstone is working fine.

cheers
Johan

On 18 Nov 2010, at 21:53, Sean Allen wrote:

> You can do a full backup and restore into a virgin extent.
>
> See section 6.6 ( step 3 ) of the system administration guide.
>
> On Thu, Nov 18, 2010 at 3:14 PM, Johan Brichau <[hidden email]> wrote:
> Hi,
>
> I managed to fill an extent to it's maximum allowed size of 4Gb.
> Trying an MFC does not work (see below). Is there a way I can shrink the repository anyway?
>
> Johan
>
> -------
> topaz 1> printit
> SystemRepository markForCollection
> %
> -----------------------------------------------------
> GemStone: Error Fatal
> The Repository is full and can no longer be expanded.,
> Error Category: [GemStone] Number: 4002 Arg Count: 1
>
>
>

SeanTAllen

Re: recover from full extent?

i never ran mfc when doing a full backup and restore to reclaim 'free space' and it worked for me. ymmv.

On Fri, Nov 19, 2010 at 1:29 AM, Johan Brichau <[hidden email]> wrote:

Thanks Dale for the pointer to the new key files.

Sean: do you mean I can skip the first 2 steps? Because that procedure is exactly what I was trying to do but the MFC did not want to go ahead (probably it needs extra space for the GC itself).

btw, it's OK to tell me the extent is doomed ;-) It's the result of running 20 times about a 1000 unit tests in SeasideTesting that each reset my entire 'test db'. I guess that at least means that SeasideTesting for Gemstone is working fine.

cheers
Johan

On 18 Nov 2010, at 21:53, Sean Allen wrote:

> You can do a full backup and restore into a virgin extent.
>
> See section 6.6 ( step 3 ) of the system administration guide.
>
> On Thu, Nov 18, 2010 at 3:14 PM, Johan Brichau <[hidden email]> wrote:
> Hi,
>
> I managed to fill an extent to it's maximum allowed size of 4Gb.
> Trying an MFC does not work (see below). Is there a way I can shrink the repository anyway?
>
> Johan
>
> -------
> topaz 1> printit
> SystemRepository markForCollection
> %
> -----------------------------------------------------
> GemStone: Error Fatal
> The Repository is full and can no longer be expanded.,
> Error Category: [GemStone] Number: 4002 Arg Count: 1
>
>
>

Dale Henrichs

Re: recover from full extent?

In reply to this post by Johan Brichau-2

The backup saves all objects that are in the object table, so if you
have lots of potentially dead objects, but haven't run an MFC (and let
the reclaim process finished (possible dead dropped to zero) then the
potentially dead objects are backed up.

A backup and restore does tend to reduce the size of repository, because
the restore efficiently packs objects onto data base pages ... The
system tries to avoid mostly empty pages, but there is a threshold - I
don't recall the exact number, but for the sake of argument call it 75%
- which means in this case that you could potentially reduce the size of
the repository by 25% through a backup and restore.

Dale

On 11/18/2010 10:29 PM, Johan Brichau wrote:

> Thanks Dale for the pointer to the new key files.
>
> Sean: do you mean I can skip the first 2 steps? Because that procedure is exactly what I was trying to do but the MFC did not want to go ahead (probably it needs extra space for the GC itself).
>
> btw, it's OK to tell me the extent is doomed ;-) It's the result of running 20 times about a 1000 unit tests in SeasideTesting that each reset my entire 'test db'. I guess that at least means that SeasideTesting for Gemstone is working fine.
>
> cheers
> Johan
>
> On 18 Nov 2010, at 21:53, Sean Allen wrote:
>
>> You can do a full backup and restore into a virgin extent.
>>
>> See section 6.6 ( step 3 ) of the system administration guide.
>>
>> On Thu, Nov 18, 2010 at 3:14 PM, Johan Brichau<[hidden email]> wrote:
>> Hi,
>>
>> I managed to fill an extent to it's maximum allowed size of 4Gb.
>> Trying an MFC does not work (see below). Is there a way I can shrink the repository anyway?
>>
>> Johan
>>
>> -------
>> topaz 1> printit
>> SystemRepository markForCollection
>> %
>> -----------------------------------------------------
>> GemStone: Error Fatal
>> The Repository is full and can no longer be expanded.,
>> Error Category: [GemStone] Number: 4002 Arg Count: 1
>>
>>
>>
>

Jon Paynter-2

Re: recover from full extent?

Iive had great results doing a backup and restore with my very small repository. After several weeks of dev work, it was around 250mb, and after the backup/restore + GC cycle it came down to 30mb.

On Fri, Nov 19, 2010 at 10:07 AM, Dale Henrichs <[hidden email]> wrote:

The backup saves all objects that are in the object table, so if you have lots of potentially dead objects, but haven't run an MFC (and let the reclaim process finished (possible dead dropped to zero) then the potentially dead objects are backed up.

A backup and restore does tend to reduce the size of repository, because the restore efficiently packs objects onto data base pages ... The system tries to avoid mostly empty pages, but there is a threshold - I don't recall the exact number, but for the sake of argument call it 75% - which means in this case that you could potentially reduce the size of the repository by 25% through a backup and restore.

Dale

On 11/18/2010 10:29 PM, Johan Brichau wrote:

Thanks Dale for the pointer to the new key files.

Sean: do you mean I can skip the first 2 steps? Because that procedure is exactly what I was trying to do but the MFC did not want to go ahead (probably it needs extra space for the GC itself).

btw, it's OK to tell me the extent is doomed ;-) It's the result of running 20 times about a 1000 unit tests in SeasideTesting that each reset my entire 'test db'. I guess that at least means that SeasideTesting for Gemstone is working fine.

cheers
Johan

On 18 Nov 2010, at 21:53, Sean Allen wrote:

You can do a full backup and restore into a virgin extent.

See section 6.6 ( step 3 ) of the system administration guide.

On Thu, Nov 18, 2010 at 3:14 PM, Johan Brichau<[hidden email]> wrote:
Hi,

I managed to fill an extent to it's maximum allowed size of 4Gb.
Trying an MFC does not work (see below). Is there a way I can shrink the repository anyway?

Johan

-------
topaz 1> printit
SystemRepository markForCollection
%
-----------------------------------------------------
GemStone: Error Fatal
The Repository is full and can no longer be expanded.,
Error Category: [GemStone] Number: 4002 Arg Count: 1

Dale Henrichs

Re: recover from full extent?

Ah yes, I forgot to mention the other effect - empty data pages ....
over time the repository can have a fair number of completely empty data
pages (as objects are changed the old data pages become "empty"). During
normal operation these empty data pages take up space on disk.

A backup/restore cycle will completely eliminate the empty data pages,
which can lead to dramatic reductions in repository size ...

Dale

On 11/19/2010 10:16 AM, Jon Paynter wrote:

> Iive had great results doing a backup and restore with my very small
> repository. After several weeks of dev work, it was around 250mb, and
> after the backup/restore + GC cycle it came down to 30mb.
>
> On Fri, Nov 19, 2010 at 10:07 AM, Dale Henrichs <[hidden email]
> <mailto:[hidden email]>> wrote:
>
> The backup saves all objects that are in the object table, so if you
> have lots of potentially dead objects, but haven't run an MFC (and
> let the reclaim process finished (possible dead dropped to zero)
> then the potentially dead objects are backed up.
>
> A backup and restore does tend to reduce the size of repository,
> because the restore efficiently packs objects onto data base pages
> ... The system tries to avoid mostly empty pages, but there is a
> threshold - I don't recall the exact number, but for the sake of
> argument call it 75% - which means in this case that you could
> potentially reduce the size of the repository by 25% through a
> backup and restore.
>
> Dale
>
>
> On 11/18/2010 10:29 PM, Johan Brichau wrote:
>
> Thanks Dale for the pointer to the new key files.
>
> Sean: do you mean I can skip the first 2 steps? Because that
> procedure is exactly what I was trying to do but the MFC did not
> want to go ahead (probably it needs extra space for the GC itself).
>
> btw, it's OK to tell me the extent is doomed ;-) It's the result
> of running 20 times about a 1000 unit tests in SeasideTesting
> that each reset my entire 'test db'. I guess that at least means
> that SeasideTesting for Gemstone is working fine.
>
> cheers
> Johan
>
> On 18 Nov 2010, at 21:53, Sean Allen wrote:
>
> You can do a full backup and restore into a virgin extent.
>
> See section 6.6 ( step 3 ) of the system administration guide.
>
> On Thu, Nov 18, 2010 at 3:14 PM, Johan
> Brichau<[hidden email] <mailto:[hidden email]>> wrote:
> Hi,
>
> I managed to fill an extent to it's maximum allowed size of 4Gb.
> Trying an MFC does not work (see below). Is there a way I
> can shrink the repository anyway?
>
> Johan
>
> -------
> topaz 1> printit
> SystemRepository markForCollection
> %
> -----------------------------------------------------
> GemStone: Error Fatal
> The Repository is full and can no longer be expanded.,
> Error Category: [GemStone] Number: 4002 Arg Count: 1
>
>
>
>
>