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:55:43 +0900 [thread overview]
Message-ID: <6a5c8e813a91f4edbf7353e55e87bd4a@admin.virtall.com> (raw)
In-Reply-To: <e03fc4983421a31251c6f6274dd2c597@admin.virtall.com>
On 2016-08-06 00:45, Tomasz Chmielewski wrote:
> 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
> (...)
A few mins after the previous "echo 3 > /proc/sys/vm/drop_caches" (this
file is around 1.5 MB and wasn't touched since 2016-06-21):
# file ./2016-06-21/serverY/nginx-dashboard-error.log
./2016-06-21/serverY/nginx-dashboard-error.log: ERROR: cannot read
`./2016-06-21/serverY/nginx-dashboard-error.log' (Input/output error)
# echo 3 > /proc/sys/vm/drop_caches
# file ./2016-06-21/serverY/nginx-dashboard-error.log
./2016-06-21/serverY/nginx-dashboard-error.log: ASCII text, with very
long lines
# cat ./2016-06-21/serverY/nginx-dashboard-error.log
(...works OK, no corruption...)
Tomasz Chmielewski
https://lxadm.com
next prev parent reply other threads:[~2016-08-05 15:55 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
2016-08-05 15:51 ` Chris Mason
2016-08-05 15:55 ` Tomasz Chmielewski [this message]
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=6a5c8e813a91f4edbf7353e55e87bd4a@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).