What should be the steps or options to resolve this? Thanks! On 3/28/06, Orlando Andico <[EMAIL PROTECTED]> wrote: > journal error on ext3 is usually related to running out of (physical) > memory, even if there's lots of swap available. the symptom is that there > are a bunch of journal errors, then the filesystem gets mounted read-only to > forestall further damage. so the system is effectively "wedged" since it's > read-only. > > after reboot, one SHOULD run fsck.ext3 to fix the filesystem > (time-consuming). i don't know what would happen if you don't. > > > > On 3/28/06, Tito Mari Francis Escaño <[EMAIL PROTECTED]> wrote: > > I read /var/log/messages and it's full of SQL statements, as per > > configuration of PostgreSQL. There's no indication of any hardware > > failure. When the server was rebooted, there were no problems with the > > hardware. According to the technician who attended it, there were > > journal error, but it wasn't clear. We had to restart the server to > > get it back on track or our site would spend another hour unavailable. > > What could have been the problem? There could be a software issue but > > I'm unsure. Thanks! > > > > > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > [email protected] (#PLUG @ irc.free.net.ph) > Read the Guidelines: http://linux.org.ph/lists > Searchable Archives: http://archives.free.net.ph > >
-- Tito Mari Francis H. Escaño Computer Engineer and Free Software Proponent _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
