Bug 137382 - pool init.d scripts can hang on startup until console input is provided
pool init.d scripts can hang on startup until console input is provided
Status: CLOSED ERRATA
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: gfs (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adam "mantis" Manthei
GFS Bugs
:
Depends On: 137381
Blocks:
  Show dependency treegraph
 
Reported: 2004-10-27 17:49 EDT by Adam "mantis" Manthei
Modified: 2010-01-11 22:00 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-12-01 15:04:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam "mantis" Manthei 2004-10-27 17:49:57 EDT
Description of problem:
pool init.d scripts can hang on startup until console input is
provided.  This will happen if there is a file in the /dev/pool/
directory that has the same name as the pool that is being assembled.  

Version-Release number of selected component (if applicable):
GFS-6.0.0-15

How reproducible:


Steps to Reproduce:
1. make sure pool is not assembled
2. create a file in /dev/pool with the poolname you want to assemble
   (e.g. touch /dev/pool/yourpoolnamehere)
3. run the pool init.d script
4. script will hang until interactive input is provided

Actual results:
[root@trin-11 root]# /etc/init.d/pool start
Starting pool:/dev/pool/iscsi exists - remove? (y/n):  

Expected results:
root@trin-11 root]# /etc/init.d/pool start
Starting pool:                                             [  OK  ]
Comment 1 Adam "mantis" Manthei 2004-10-27 17:55:58 EDT
Added the following tempoary hack to workaround the issue until bug
#137381 is addressed:

diff -u -p -r1.1.2.3 pool
--- pool        29 Jun 2004 22:41:44 -0000      1.1.2.3
+++ pool        27 Oct 2004 21:55:32 -0000
@@ -33,7 +33,7 @@ start()
                for pool in $POOLS
                do
                        echo -n "Starting pool $pool:"
-                       if pool_assemble -q $pool 2>/dev/null
+                       if yes | pool_assemble -q $pool 2>/dev/null
                        then
                                success
                        else
@@ -44,7 +44,7 @@ start()
                done
        else
                echo -n "Starting pool:"
-               if pool_assemble -q 2>/dev/null 
+               if yes | pool_assemble -q 2>/dev/null 
                then
                        success
                else
Comment 2 Adam "mantis" Manthei 2004-10-29 11:06:56 EDT
resolved in GFS/init.d/pool 1.1.2.5

Now that bug #137381 has been resolved (override flag added to
pool_assemble) the hack of piping "yes" into pool_assemble can be
replaced by the correct fix:

diff -u -r1.1.2.4 pool
--- pool        27 Oct 2004 21:58:25 -0000      1.1.2.4
+++ pool        29 Oct 2004 15:07:02 -0000
@@ -33,7 +33,7 @@
                for pool in $POOLS
                do
                        echo -n "Starting pool $pool:"
-                       if yes | pool_assemble -q $pool 2>/dev/null
+                       if pool_assemble -O -q $pool 2>/dev/null
                        then
                                success
                        else
@@ -44,7 +44,7 @@
                done
        else
                echo -n "Starting pool:"
-               if yes | pool_assemble -q 2>/dev/null
+               if pool_assemble -O -q 2>/dev/null
                then
                        success
                else
Comment 3 Derek Anderson 2004-12-01 15:04:39 EST
Verified in GFS-6.0.2-12.
Comment 4 Tim Powers 2004-12-03 11:58:47 EST
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-659.html

Note You need to log in before you can comment on or make changes to this bug.