Re: send/receive locking

Hugo Mills
2014-03-08T22:16:55Z

[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

On Sat, Mar 08, 2014 at 10:02:39PM +0000, Josef Bacik wrote:
> 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,

Aah, that's good to know. It's not an FS I care about massively
much, but it'd be a pain to recreate all the setup. I think I'll go
cherry picking tomorrow morning. :)

Hugo.

> Josef
>
> Hugo Mills <hugo@carfax.org.uk> 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@carfax.org.uk> 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 http://www.carfax.org.uk
--- Comic Sans goes into a bar, and the barman says, "We don't ---
serve your type here."

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]