On Fri, Oct 17, 2014 at 04:29:36PM +0800, Liu Bo wrote: > On Fri, Oct 17, 2014 at 10:10:09AM +0200, Tomasz Torcz wrote: > > On Fri, Oct 17, 2014 at 04:02:03PM +0800, Liu Bo wrote: > > > > Recently I've observed some corruptions to systemd's journal > > > > files which are somewhat puzzling. This is especially worrying > > > > as this is btrfs raid1 setup and I expected auto-healing. > > > > read(4, 0x1001000, 65536) = -1 EIO (Input/output error) > > Well..I don't know exactly what's the cause, but as the file is NOCOW, it writes > data in place, have you experienced a hard reboot or something recently? Nothing like that. Server is on an UPS, there were couple normal shutdowns this year (few kernel upgrades). > And any message in dmesg log while getting EIO by reading the file? Nothing in dmesg, no btrfs messages, no SCSI/SATA errors, nothing. That's why I find those corruptions mysterious. Maybe there is some way to inspect internal btrfs state and find out what causing the problems? Or maybe this is related to patch mentioned in this thread? -- Tomasz Torcz "Never underestimate the bandwidth of a station xmpp: zdzichubg@xxxxxxxxx wagon filled with backup tapes." -- Jim Gray -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
