linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <tch@virtall.com>
To: Chris Mason <clm@fb.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Input/output error, nothing appended in dmesg
Date: Sat, 06 Aug 2016 00:45:13 +0900	[thread overview]
Message-ID: <e03fc4983421a31251c6f6274dd2c597@admin.virtall.com> (raw)
In-Reply-To: <e8e15af203f0f559d46402ee6a296209@admin.virtall.com>

On 2016-08-06 00:38, Tomasz Chmielewski wrote:

>> Too big for the known problem though.  Still, can you btrfs-debug-tree
>> and just make sure it doesn't have inline items?
> 
> Hmmm....
> 
> # btrfs-debug-tree /dev/xvdb > /root/debug.tree
> parent transid verify failed on 355229302784 wanted 49943295 found 
> 49943301
> parent transid verify failed on 355229302784 wanted 49943295 found 
> 49943301
> Ignoring transid failure
> parent transid verify failed on 355233251328 wanted 49943299 found 
> 49943303
> parent transid verify failed on 355233251328 wanted 49943299 found 
> 49943303
> Ignoring transid failure
> print-tree.c:1105: btrfs_print_tree: Assertion failed.
> btrfs-debug-tree[0x418d99]
> btrfs-debug-tree(btrfs_print_tree+0x26a)[0x41acf6]
> btrfs-debug-tree(main+0x9a5)[0x432589]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f2369de0f45]
> btrfs-debug-tree[0x4070e9]

And, miracle cure O_o

# file ./2016-08-02/serverX/syslog.log
ERROR: cannot read `./2016-08-02/serverX/syslog.log' (Input/output 
error)

# echo 3 > /proc/sys/vm/drop_caches

# file 2016-08-02/serverX/syslog.log
2016-08-02/serverX/syslog.log: ASCII text, with very long lines

# cat 2016-08-02/serverX/syslog.log
(...)


Tomasz Chmielewski
https://lxadm.com

  parent reply	other threads:[~2016-08-05 15:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05 11:42 Input/output error, nothing appended in dmesg Tomasz Chmielewski
2016-08-05 14:26 ` Chris Mason
2016-08-05 14:44   ` Tomasz Chmielewski
2016-08-05 15:15     ` Chris Mason
2016-08-05 15:38       ` Tomasz Chmielewski
2016-08-05 15:40         ` Chris Mason
2016-08-05 15:50           ` Tomasz Chmielewski
2016-08-05 15:45         ` Tomasz Chmielewski [this message]
2016-08-05 15:51           ` Chris Mason
2016-08-05 15:55           ` Tomasz Chmielewski
2016-08-05 17:14           ` Diego Calleja

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e03fc4983421a31251c6f6274dd2c597@admin.virtall.com \
    --to=tch@virtall.com \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).