On 2014-12-07 06:26, Chris Murphy wrote:
On Sat, Dec 6, 2014 at 2:17 AM, Tomasz Chmielewski <t...@virtall.com>
wrote:
After we run again btrfs device delete missing /home, the newly
created
directory eventually (/home/backup/ma-int/weekly.tmp) is being
detected as
"csum failed ino ...".
If that comes up clean then chances are this is file corruption and
you can mount and do:
btrfs scrub start -r <MP>
Actually, this seemed to be enough.
I didn't realize that scrub would print the names of corrupted files.
After removing them, "btrfs device delete missing" is finally making
some progress (previously, it would break at 300+GB; still running now):
# btrfs fi show /home
Label: none uuid: 92e93437-cc9f-475d-a739-085f3270896b
Total devices 3 FS bytes used 1.40TiB
devid 2 size 1.70TiB used 1.42TiB path /dev/sdb4
devid 3 size 1.70TiB used 807.00GiB path /dev/sda4
*** Some devices missing
Btrfs v3.14.2
Thanks for your hints!
--
Tomasz Chmielewski
http://www.sslrack.com
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
