[
https://issues.apache.org/jira/browse/KUDU-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483424#comment-16483424
]
Jean-Daniel Cryans commented on KUDU-1867:
------------------------------------------
[~fwang29] did you mean to resolve this as Fix Version 1.8.0?
> Improve the "Could not lock .../block_manager_instance" error message
> ---------------------------------------------------------------------
>
> Key: KUDU-1867
> URL: https://issues.apache.org/jira/browse/KUDU-1867
> Project: Kudu
> Issue Type: Bug
> Components: fs
> Affects Versions: 1.2.0
> Reporter: Jean-Daniel Cryans
> Assignee: Fengling Wang
> Priority: Major
> Labels: newbie
> Fix For: 1.2.0
>
>
> It's possible for users to encounter a rather cryptic error when trying to
> run Kudu while it's already running or with a different user than what was
> previously used:
> {code}
> Check failed: _s.ok() Bad status: IO error: Failed to load FS layout: Could
> not lock /path/to/data/block_manager_instance: Could not lock
> /path/to/data/block_manager_instance: lock
> /path/to/data/block_manager_instance: Resource temporarily unavailable (error
> 11)
> {code}
> This is the log line that we FATAL with, so unless you already know what it
> means you're left to your own guessing and log digging. Instead, the error
> message could be more prescriptive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
