Don't do it on a fs you care about, cow is broken with that branch so it will corrupt your fs. So actually just find Wang's patch that sets skip locking for send and do that. Thanks, Josef Hugo Mills <hugo@xxxxxxxxxxxxx> wrote: On Sat, Mar 08, 2014 at 09:55:50PM +0000, Josef Bacik wrote: > Hey Hugo will you try the danger branch on btrfs-next, Wang changed the locking a bit. Thanks, Sure. I'll build a kernel tonight and report tomorrow. I'm not sure how repeatable the problem is, though. I'll see if I can quantify that, too. Hugo. > Josef > > Hugo Mills <hugo@xxxxxxxxxxxxx> wrote: > > > Is there anything that can be done about the issues of btrfs send > blocking? I've been writing a backup script (slowly), and several > times I've managed to hit a situation where large chunks of the > machine grind to a complete halt in D state because the backup script > has jammed up. > > Now, I'm aware that you can't send and receive to the same > filesystem at the same time, and that's a restriction I can live with. > However, having things that aren't related to the backup process > suddenly stop working because the backup script is trying to log its > progress to the same FS it's backing up is... umm... somewhat vexing, > to say the least. > > Is this a truly fundamental property of send/receive, or is there > likely to be a simple(ish) solution? > > Hugo. > -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or https://urldefense.proofpoint.com/v1/url?u=http://www.carfax.org.uk/&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cKCbChRKsMpTX8ybrSkonQ%3D%3D%0A&m=mielorsIWCCiMGh9bKTw2yfu58jDUmYHzG5Bs4%2BQ668%3D%0A&s=e7731595293b5612cadc9ba07854b17052b8c74ac69ddefd02b0437e42086594 --- Well, you don't get to be a kernel hacker simply by looking --- good in Speedos. -- Rusty Russell -- 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
