Subject Re: [firebird-support] wcdata.fdb file opened many times, hogging space !
Author marcus
Hej all

jbossert@... wrote:
> No i'm not deleting any file.
Sure? If not you, may it be a script or an application?
Because dropping a database per fb service or isql statement (which may
be the same) would not left over any hanging fb_inet processes.


>
>
> -we use the gfix script to stop the db every night, and make a backup.
> this is not releasing the hogged space (fb_inet process still running) !
> we use "gfix -user sysdba -password XXXX -shut full -force 0
> wcdata.fdb", then the DB is dow, we we try to connect to it.

>
>
> -Then we decided to go with a service firebird2-5.... stop, this this is
> not releasing the hogged space (fb_inet process still running) !
?? But why?? One step earlier you've told the database to shutdown, so
there cannot be any running fb_inet process, as they are invoked per
(x)inetd. The database is shut down, any connection will be prohibited.

>
>
> -the only option is to do a "pkill fb_inet", thus processes a killed,
> space is released.
>
>
> @MArk : by service api , do you mean using gfix to shut down the DB ?
>
>
> I am amazed i'm the on ly one having this issue, i did an standard
> install, no fancy config !
Playing around a little bit - even a forced shutdown on a database with
open transactions - as soon as the gfix -shut is executed - there is NO
single that has any connection to the database i've issued the shutdown
to. Try to finish open transactions, may it be commiting or rolling back
- errors. No new attachments to the database are allowed. So from this
point on i can take the database out for a walk - and no single fb_inet
process will miss it....

Being honest - smells like faulty firebird and/or connection and/or
system handling.


>
>
> Thanks for your help
>
>
>
> ---In firebird-support@yahoogroups.com, <mark@...> wrote:
>
> On 21-11-2013 17:59, jbossert@... <mailto:jbossert@...> wrote:
>
> >
> >
> > Hi Mark,
> >
> >
> > Right now i'm looking in a way to reclaim the space right away without
> > killing the process.
>
> Use the monitoring tables to kill connections.
>
> But how did you remove the file, did you delete it? Instead of deleting
> it through the file system, you might want to try dropping it using the
> service API. That will check if the database is still in use or not.
>
> > Is it helping if i change the FB flavor to "superclassic",
> assuming this
> > fires only 1 instance of the db, so the file will be opened only 1
> time ?!
>
> I don't know.
>
> Mark
> --
> Mark Rotteveel
>