Bug 764661 (GLUSTER-2929) - Pathetic message upon a umount request
Summary: Pathetic message upon a umount request
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-2929
Product: GlusterFS
Classification: Community
Component: core
Version: 3.2.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-23 21:17 UTC by Harshavardhana
Modified: 2015-09-01 23:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Harshavardhana 2011-05-23 21:17:57 UTC 
[2011-05-22 18:58:01.878156] I [fuse-bridge.c:3316:fuse_graph_setup] 0-fuse: switched to graph 2
[2011-05-22 18:58:13.84989] I [fuse-bridge.c:3218:fuse_thread_proc] 0-fuse: unmounting /tmp/test
[2011-05-22 18:58:13.85127] W [glusterfsd.c:700:cleanup_and_exit] (-->/lib/libc.so.6(clone+0x6d) [0x7fabf706aaed] (-->/lib/libpthread.so.0(+0x7d40) [0x7fabf72fed40] (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xc5) [0x405ff5]))) 0-: received signum (15), shutting down

Is there a need for glibc Jibber-Jabber in our log message? . Isn't the first message "Umounting /tmp/test" sufficient enough?
Comment 1 Vijay Bellur 2011-05-24 07:28:41 UTC 
This doesn't affect usability. The backtrace will only aide in determining the reason for cleanup_and_exit.
Note You need to log in before you can comment on or make changes to this bug.