Bug 87692
| Summary: | While creating a database ext3 crashes the whole machine | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Jan Albrecht <jan.albrecht> |
| Component: | kernel | Assignee: | Larry Woodman <lwoodman> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.1 | CC: | shillman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-10-03 15:05:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This problem was addressed in the latest kernel errata(e.24). Larry Woodman As it's been about 3 months since this was said to have been fixed, with no reply saying otherwise, I'm closing this bug. |
Description of problem: Everytime when we tried to create a database on an ext3 filesystem we got the "kernel: ENOMEM in journal_alloc_journal_head,retrying." error and the machine rebooted itself. The error could be prevented if we mounted the filesystem as an ext2 before creating the database. We're using the with AS2.1 supplied cluster. Version-Release number of selected component (if applicable): Kernel 2.4.9-e.12summit Database: Sybase Adaptive Server Enterprise/12.5.0.1/EBF 10431 ESD#2/P/ Linux Intel/Linux 2.2.14-5.0smp i686/rel12501/1792/32-bit/OPT/ Mon Jul 29 22:24:47 2002 How reproducible: Create Database on ext3 filesystem Steps to Reproduce: 1. The following commands were executed: /* Generated on 20030326162320 by user XXXXXX*/ create database XXXXXXX on XXXXXXXX = 2000 log on XXXXXXXX = 512 go /* Generated on 20030325221626 by user XXXXXX */ disk init name = XXXXXXXX, vstart = 0, physname = '/XXX/XXXXXXXX/XXXX/XXXXXX.XXXXXXXX', size = 1048576, vdevno = 7 go (sensitive Information where replaced by a 'X') 2. The machines produces the following errors and reboots: Mar 26 14:26:31 XXXXXXXX kernel: ENOMEM in journal_alloc_journal_head, retrying. Mar 26 14:26:32 XXXXXXXX portmap[17883]: connect from 172.19.232.79 to callit(ypserv): request from unauthorized host Mar 26 14:26:37 XXXXXXXX kernel: ENOMEM in journal_alloc_journal_head, retrying. Actual results: To prevent this error: - Stop Database - remount filesystems with ext2 - create database - restart cluster service Expected results: Create database on ext3 without reboot Additional info: A Service Request is already opened for this: 'Service Request: 230822'