Re: strange i/o errors with btrfs on raid/lvm

2015-10-01 Thread Russell Coker
On Sat, 26 Sep 2015 06:47:26 AM Chris Murphy wrote: > And then > > Aug 28 17:06:49 host mdadm[2751]: RebuildFinished event detected on md > device /dev/md/0, component device mismatches found: 2048 (on raid > level 10) > Aug 28 17:06:49 host mdadm[2751]: SpareActive event detected on md > device

Re: strange i/o errors with btrfs on raid/lvm

2015-09-28 Thread Jogi Hofmüller
Hi Chris, all, Am 2015-09-25 um 22:47 schrieb Chris Murphy: > On Fri, Sep 25, 2015 at 2:26 PM, Jogi Hofmüller wrote: > >> That was right while the RAID was in degraded state and rebuilding. > > On the guest: > > Aug 28 05:17:01 vm kernel: [140683.741688] BTRFS info (device vdc):

Re: strange i/o errors with btrfs on raid/lvm

2015-09-25 Thread Chris Murphy
On Fri, Sep 25, 2015 at 2:26 PM, Jogi Hofmüller wrote: > That was right while the RAID was in degraded state and rebuilding. On the guest: Aug 28 05:17:01 vm kernel: [140683.741688] BTRFS info (device vdc): disk space caching is enabled Aug 28 05:17:13 vm kernel: [140695.575896]

Re: strange i/o errors with btrfs on raid/lvm

2015-09-25 Thread Chris Murphy
>From offlist host logs (the Btrfs errors happen in a VM guest), I think this is a hardware problem. Aug 28 07:04:22 host kernel: [41367948.153031] sas: sas_scsi_find_task: task 0x880e85c09c00 is done Aug 28 07:04:22 host kernel: [41367948.153033] sas: sas_eh_handle_sas_errors: task

strange i/o errors with btrfs on raid/lvm

2015-09-24 Thread Jogi Hofmüller
Hi all, We experience strange Input/output errors on our mail server (dovecot pop/imap) that is using btrfs for its mailspool. The server uses software RAID10. The RAID is split into LVMs. The mailspool logical volume uses btrfs. For several days now we see Input/output errors on different

Re: strange i/o errors with btrfs on raid/lvm

2015-09-24 Thread Chris Murphy
On Thu, Sep 24, 2015 at 8:34 AM, Jogi Hofmüller wrote: > All this runs on a virtual machine that uses kernel 4.1.3 (Debian build) > and btrfs-progs v4.0. Unrelated to the problem but I'd upgrade progs, in case it's ever needed. 4.1 and 4.2 have tons of bug fixes over 4.0 already.