On May 14, 2013, Liu Bo <bo.li.liu@xxxxxxxxxx> wrote: >> In one of the failures that caused machine load spikes, I tried to >> collect info on active processes with perf top and SysRq-T, but nothing >> there seemed to explain the spike. Thoughts on how to figure out what's >> causing this? > Although I've seen your solution patch in this thread, I'm still curious > about this senario, could you please share the reproducer script or > something? I'm afraid I don't have one. I just use the filesystem on various disks, with ceph osds and other non-ceph subvolumes and files, and occasionally I run into one of these bad blocks and the filesystem gets into these odd states. > I guess that you're using '-l 64k -n 64k' for mkfs.btrfs That is correct, but IIUC this should only affect metadata, and metadata recovery from the DUP block works. It's data (single copy) that fails as described. -- Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/ You must be the change you wish to see in the world. -- Gandhi Be Free! -- http://FSFLA.org/ FSF Latin America board member Free Software Evangelist Red Hat Brazil Compiler Engineer -- 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
