Hi, 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. System details: 3.17.0-301.fc21.x86_64 btrfs: raid1 over 2x dm-crypted 6TB HDDs. mount opts: rw,relatime,seclabel,compress=lzo,space_cache Broken files are in /var/log/journal directory. This directory is set NOCOW with chattr, all the files within too. Example of broken file: system@0005057fe87730cf-6d3d85ed59bd70ae.journal~ When read with dd_rescue, there are many I/O errors reported, the summary looks like that (x = error): >-..-..xxxxxxxxx---x.-..-..-...-..-..-...-< 100% Reads with cat, hexdump fails with: read(4, 0x1001000, 65536) = -1 EIO (Input/output error) But btrfs dev stat reports no errors! $ btrfs dev stat . [/dev/dm-0].write_io_errs 0 [/dev/dm-0].read_io_errs 0 [/dev/dm-0].flush_io_errs 0 [/dev/dm-0].corruption_errs 0 [/dev/dm-0].generation_errs 0 [/dev/dm-1].write_io_errs 0 [/dev/dm-1].read_io_errs 0 [/dev/dm-1].flush_io_errs 0 [/dev/dm-1].corruption_errs 0 [/dev/dm-1].generation_errs 0 There are no hardware errors in dmesg. This is perplexing. How to find out what is causing the brokeness and howto avoid it in the future? -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz .. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. -- 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
