Red Hat Bugzilla – Bug 964048
longevity: Incorrect log level messages in posix_istat and posix_lookup
Last modified: 2015-03-23 03:39:37 EDT
Description of problem:
[2013-05-13 16:14:36.287918] W [posix-helpers.c:355:posix_istat] 0-long1-posix: lstat failed on /brick
s/long1_brick0/.glusterfs/84/82/8482e74b-e261-4367-8c09-baf3f098d34e (Input/output error)
[2013-05-13 16:14:36.287942] E [posix.c:154:posix_lookup] 0-long1-posix: lstat on /bricks/long1_brick0
/.glusterfs/84/82/8482e74b-e261-4367-8c09-baf3f098d34e failed: Input/output error
[2013-05-13 16:14:36.287954] W [server-resolve.c:130:resolve_gfid_cbk] 0-long1-server: 8482e74b-e261-4
367-8c09-baf3f098d34e: failed to resolve (Input/output error)
In both posix_istat and posix_lookup , lstat failed on /bricks/long1_brick0 , but one logs it as " W " and one logs it as " E ". There should be consistency.
Either both should be " W " or both should be " E "
Version-Release number of selected component (if applicable): glusterfs-220.127.116.11rhs-1.el6rhs.x86_64
How reproducible: It was happened in longevity test-run
Steps to Reproduce:
It was observed while debugging for the Bug 964038
Actual results: There is inconsistency in log-level of log messages
Expected results: There should be consistency in log-levels of log messages,
The product version of Red Hat Storage on which this issue was reported has reached End Of Life (EOL) , hence this bug report is being closed. If the issue is still observed on a current version of Red Hat Storage, please file a new bug report on the current version.