Bug 761837 (GLUSTER-105)

Summary: [2.0.3rc1] Log structure has changed from 2.0.2
Product: [Community] GlusterFS Reporter: Sachidananda Urs <sac>
Component: coreAssignee: Vikas Gorur <vikas>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: 2.0.2CC: gluster-bugs, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Sachidananda Urs 2009-07-02 07:31:01 UTC 
2.0.2 GlusterFS log files had the version and other headers listed first, followed by the volume file and other information...

i.e

================================================================================
Version      : glusterfs 2.0.3rc1 built on Jul  1 2009 22:03:56
TLA Revision : e0db4ff890b591a58332994e37ce6db2bf430213
Starting Time: 2009-07-01 23:45:20
Command line : /opt/glusterfs/2.0.3rc1/sbin/glusterfsd -f /share/sac/volfiles/2.0.3/nufa/nufa.vol -l /share/sac/log/2.0.3rc1/nufa/brick1/nufa.log --run-id nu
fa_2.0.3rc1 /mnt/sac 
PID          : 16239
System name  : Linux
Nodename     : brick1
Kernel Release : 2.6.18-128.1.10.el5xen
Hardware Identifier: x86_64

================================================================================

Followed by the vol file...

But later releases have the volume file copy listed first and the headers come later... which makes reading the logs a bit clumsy.
Comment 1 Vikas Gorur 2009-07-02 09:39:14 UTC 
Patch submitted: http://patches.gluster.com/patch/669/