Clean up kernel messages at boot

What steps will reproduce the problem?
1. Turn off system
2. Turn on system
3. Observe console spam

What is the expected output? What do you see instead?
Expect quiet meaningful output, instead there is lots of seemingly 
useless output.

Common output snippets below:
incoming: Client thread started, pid=6209 for snapshot 775                      

worker: Worker thread started, pid=6210 for snapshot 775                        

worker: worker recovering for snapshot 775                                      

control: Control thread started, pid=6211 for snapshot 775                      

requeue_queries:                                                                

worker: worker resuming for snapshot 775                                        

incoming: identify succeeded. chunksize 14                                      

ddsnap_create: Created snapshot device 
snapstore=/var/lib/zumastor/volumes/zuma/device/snapstore 
origin=/var/lib/zumastor/volumes/zuma/device/origin 
socket=/var/run/zumastor/agents/zuma snapshot=879                               

incoming: Client thread started, pid=6221 for snapshot 879                      

worker: Worker thread started, pid=6222 for snapshot 879                        

worker: worker recovering for snapshot 879                                      

control: Control thread started, pid=6223 for snapshot 879                      

requeue_queries:                                                                

worker: worker resuming for snapshot 879                                        

incoming: identify succeeded. chunksize 14       

and
control: ddcon/1324 exiting for snapshot 4900                                   

ddsnap_destroy: thread 1 exited                                                 

ddsnap_destroy: thread 2 exited                                                 

ddsnap_destroy: thread 3 exited                                                 

ddsnap_destroy: Unblocking helper threads                                       

ddsnap_destroy: closing socket connections                                      

worker: ddwrk/1325 exiting for snapshot 4901                                    

incoming: socket error -32                                                      

incoming: ddcli/1325 exiting for snapshot 4901                                  

control: socket error -32                                                       

control: ddcon/1325 exiting for snapshot 4901                                   

ddsnap_destroy: thread 1 exited                                                 

ddsnap_destroy: thread 2 exited                                                 

ddsnap_destroy: thread 3 exited                                                 

EXT3-fs: INFO: recovery required on readonly filesystem.                        

EXT3-fs: write access will be enabled during recovery.                          

kjournald starting.  Commit interval 5 seconds    

and snapshot creation
ddsnap_create: Created snapshot device 
snapstore=/var/lib/zumastor/volumes/software/device/snapstore 
origin=/var/lib/zumastor/volumes/software/device/origin 
socket=/var/run/zumastor/agents/software snapshot=376
incoming: Client thread started, pid=8320 for snapshot 376
worker: Worker thread started, pid=8321 for snapshot 376
worker: worker recovering for snapshot 376
control: Control thread started, pid=8322 for snapshot 376
requeue_queries: 
worker: worker resuming for snapshot 376
incoming: identify succeeded. chunksize 14
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Original issue reported on code.google.com by williama...@gmail.com on 10 Jun 2008 at 9:17
junneyang / zumastor

Clean up kernel messages at boot #152
