Subject | Re: [ib-support] Redhat8, EXT3 file system, FBSQL 1.5RC3 |
---|---|
Author | Kip Iles |
Post date | 2003-06-06T17:30:14Z |
Thanks Dimitrios,
I found an Errata for ext3 on Redhat8 that addressed file system corruption.
I was using Redhat Network to update that particular server and the package
list was out of sync. After re-syncing - I was 48 erratas behind.
Ill just wait and see ...
Kip Iles
""Dimitrios Chr. Ioannidis"" <dchri@...> wrote in message
news:3EDF55F3.8000800@......
I found an Errata for ext3 on Redhat8 that addressed file system corruption.
I was using Redhat Network to update that particular server and the package
list was out of sync. After re-syncing - I was 48 erratas behind.
Ill just wait and see ...
Kip Iles
""Dimitrios Chr. Ioannidis"" <dchri@...> wrote in message
news:3EDF55F3.8000800@......
> >gds_drop
> >
> >System: Redhat Linux 8 kernel version 2.4.18-14.
> >
> >I ran across an issue when deleting a firebird gdb file on a EXT3
> >filesystem. The space was not freed until I rebooted the system. The
> >administrator deleting the database and recreating it did not use
> >to drop all resources before-hand.....
> >
> >
> >
> I think i use to have such problems on a client ...
>
> From the Update Comments for the RedHat Kernel 2.4 updated 2003-06-03
>
> <<A potential data corruption scenario has been identified. This
> scenario can occur under heavy, complex I/O loads. The scenario
> only occurs while performing memory mapped file I/O, where the
> file is simultaneously unlinked and the corresponding file blocks
> reallocated. Furthermore, the memory mapped writes must be to a
> partial page at the end of a file on an ext3 file system. As such,
> Red Hat considers this an unlikely scenario. >>
>
> Maybe an update it will solve the problem ?
> I update my client yesterday so i can't really tell, it's too soon ...
>
> Dimitris
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>