Restore from tranlogs problem

Ciao,

      
     i have a small ubuntu system configured for recovery  procedure.

     I do a test restoring from a full backup and after from tranlogs.

     The stone is based on gsDevKit 3.1.0.6
   
    The log relative to the Topaz command:    SystemRepository restoreFromCurrentLogs

         report:

                --- 10/13/15 01:09:41 CEST ---

    Opened a transaction log file for read_nolocks.
       filename = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog181.dbf

--- 10/13/15 01:37:21 CEST ---
    Opened a transaction log file for read_nolocks.
       filename = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog182.dbf

--- 10/13/15 02:09:07 CEST ---
    Opened a transaction log file for read_nolocks.
       filename = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
    Restore from logs took 32748.103 seconds
      29.810 seconds spent waiting for reclaiming dead oops
      32403.850 seconds spent in readThread waiting for free buffers

      Restore from logs to checkPoint 182.450231

    After when i do the topaz command:        SystemRepository commitRestore

        the logs report:

--- 10/13/15 09:16:36 CEST ---
    Creation of a new transaction log has failed,
    filename = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
    reason = File = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
DBF Op: Create; DBF Record: -1;
Error: The specified file already exists.; System Codes: No disk I/O error information is available.

    Creation of a new transaction log has failed,
    filename = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
    reason = File = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
DBF Op: Create; DBF Record: -1;
Error: The specified file already exists.; System Codes: No disk I/O error information is available.

    Creation of a new transaction log has failed,
    filename = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
    reason = File = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
DBF Op: Create; DBF Record: -1;
Error: The specified file already exists.; System Codes: No disk I/O error information is available.

    Creation of a new transaction log has failed,
    filename = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
    reason = File = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
DBF Op: Create; DBF Record: -1;
Error: The specified file already exists.; System Codes: No disk I/O error information is available.

    Creation of a new transaction log has failed,
    filename = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
    reason = File = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
DBF Op: Create; DBF Record: -1;
Error: The specified file already exists.; System Codes: No disk I/O error information is available.

    Creation of a new transaction log has failed,
    filename = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf

  Creation of a new transaction log has failed,
    filename = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
    reason = File = /opt/gsDevKitHome/gemstone/stones/gestionale/tranlogs/tranlog183.dbf
DBF Op: Create; DBF Record: -1;
Error: The specified file already exists.; System Codes: No disk I/O error information is available.
    Unable to re-originate log during commitRestore.  You may need to
    archive and delete some tranlogs to make space for new tranlogs.

    Terminating stone.

    SHUTDOWN command was generated by  re-originate log failed.
    Waiting for all tranlog writes to complete
    Waiting for Timer thread to stop
    Waiting for NetRead thread to stop

    Terminating stone.

    A this point after restart stone with the -R options into topaz i do:

 topaz 1> printit
SystemRepository restoreStatus
%
Restoring from transaction log files, restored to 09/10/15 20:27:33 CEST, file 182 record 450231, nextFileId 182, oldest fileId 182

topaz 1> printit
SystemRepository restoreFromCurrentLogs
%
Restore from transaction log(s) succeeded,

topaz> login
topazm: in login, found topaz session 1 stale
[13/10/2015 10:29:26.808 CEST]
  gci login: currSession 1 rpc gem processId 5322 OOB keep-alive interval 0
successful login
topaz 1> printit
SystemRepository restoreStatus
%
Restoring from transaction log files, restored to 09/10/15 21:04:48 CEST, file 183 record 1414, nextFileId 184, oldest fileId 183

topaz 1> printit
SystemRepository commitRestore
%
Restore from transaction log(s) succeeded, commitRestore succeeded.

topaz> login
topazm: in login, found topaz session 1 stale
[13/10/2015 10:32:31.598 CEST]
  gci login: currSession 1 rpc gem processId 5351 OOB keep-alive interval 0
successful login
topaz 1> printit
SystemRepository restoreStatus
%
Restore is not active.

    And a this point all works fine and the stone is right update.

    Now i don't understand because the system report the error relative to the tranlog183.dbf  

    when the first      SystemRepository restoreFromCurrentLogs  

    report the tranlog183.dbf as open and ( elaborated ????? )

    I wrong anything ?

    Thanks for any considerations,
       
        Dario

   

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass