[jira] [Commented] (KUDU-1367) Crash at startup after full disk due to corrupt tablet metadata

["Todd Lipcon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187918#comment-15187918 ] 

Todd Lipcon commented on KUDU-1367:
-----------------------------------

Dupe of KUDU-668. This can be worked around by truncating the file to the correct length in the meantime.

> Crash at startup after full disk due to corrupt tablet metadata
> ---------------------------------------------------------------
>
>                 Key: KUDU-1367
>                 URL: https://issues.apache.org/jira/browse/KUDU-1367
>             Project: Kudu
>          Issue Type: Bug
>          Components: tablet
>    Affects Versions: 0.5.0
>            Reporter: Mike Percy
>
> As reported by Nick Wolf.
> The disk filled up on their tablet server, resulting in a bad metadata file being written. This was the error message on tablet server startup:
> {code}
> F0309 06:57:50.281460 32105 tablet_server_main.cc:49] Check failed: _s.ok() Bad status:Corruption: Failed to load FS layout: Could not read records from container
> /var/lib/kudu/tserver/data/b1940ca83ce44da3bc6bf4a36f3d5e90:
> Could not read body from proto container file
> /var/lib/kudu/tserver/data/b1940ca83ce44da3bc6bf4a36f3d5e90.metadata:
> File size not large enough to be valid: Proto container file
> /var/lib/kudu/tserver/data/b1940ca83ce44da3bc6bf4a36f3d5e90.metadata:
> tried to read /var/lib/kudu/tserver/data/b1940ca83ce44da3bc6bf4a36f3d5e90.metadata
> bytes at offset 30 but file size is only 114688
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)