Re: Input/output error, nothing appended in dmesg

2016-08-05 Thread Diego Calleja
El sábado, 6 de agosto de 2016 0:45:13 (CEST) Tomasz Chmielewski escribió: > 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

Re: Input/output error, nothing appended in dmesg

2016-08-05 Thread Tomasz Chmielewski
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:

Re: Input/output error, nothing appended in dmesg

2016-08-05 Thread Chris Mason
On 08/05/2016 11:45 AM, Tomasz Chmielewski wrote: > 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 >

Re: Input/output error, nothing appended in dmesg

2016-08-05 Thread Tomasz Chmielewski
On 2016-08-06 00:40, Chris Mason 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

Re: Input/output error, nothing appended in dmesg

2016-08-05 Thread Tomasz Chmielewski
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

Re: Input/output error, nothing appended in dmesg

2016-08-05 Thread Chris Mason
On 08/05/2016 11:38 AM, Tomasz Chmielewski wrote: On 2016-08-06 00:15, Chris Mason wrote: # cat 2016-08-02/serverX/syslog.log cat: 2016-08-02/serverX/syslog.log: Input/output error How big is the file? We had one bug with inline files that might have caused this. This one's tiny, 158137

Re: Input/output error, nothing appended in dmesg

2016-08-05 Thread Tomasz Chmielewski
On 2016-08-06 00:15, Chris Mason wrote: # cat 2016-08-02/serverX/syslog.log cat: 2016-08-02/serverX/syslog.log: Input/output error How big is the file? We had one bug with inline files that might have caused this. This one's tiny, 158137 bytes. Too big for the known problem though.

Re: Input/output error, nothing appended in dmesg

2016-08-05 Thread Chris Mason
On 08/05/2016 10:44 AM, Tomasz Chmielewski wrote: On 2016-08-05 23:26, Chris Mason wrote: On 08/05/2016 07:42 AM, Tomasz Chmielewski wrote: I'm getting occasional (every few weeks) input/output errors on a btrfs filesystem with compress-force=zlib, running on Amazon EC2, with 4.5.2 kernel:

Re: Input/output error, nothing appended in dmesg

2016-08-05 Thread Tomasz Chmielewski
On 2016-08-05 23:26, Chris Mason wrote: On 08/05/2016 07:42 AM, Tomasz Chmielewski wrote: I'm getting occasional (every few weeks) input/output errors on a btrfs filesystem with compress-force=zlib, running on Amazon EC2, with 4.5.2 kernel: # cat 2016-08-02/serverX/syslog.log cat:

Re: Input/output error, nothing appended in dmesg

2016-08-05 Thread Chris Mason
On 08/05/2016 07:42 AM, Tomasz Chmielewski wrote: I'm getting occasional (every few weeks) input/output errors on a btrfs filesystem with compress-force=zlib, running on Amazon EC2, with 4.5.2 kernel: # cat 2016-08-02/serverX/syslog.log cat: 2016-08-02/serverX/syslog.log: Input/output error

Input/output error, nothing appended in dmesg

2016-08-05 Thread Tomasz Chmielewski
I'm getting occasional (every few weeks) input/output errors on a btrfs filesystem with compress-force=zlib, running on Amazon EC2, with 4.5.2 kernel: # cat 2016-08-02/serverX/syslog.log cat: 2016-08-02/serverX/syslog.log: Input/output error Strangely, nothing gets appended in dmesg: #