From: Lionel Bouton <lionel-subscription@bouton.name>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs fi defrag interfering (maybe) with Ceph OSD operation
Date: Tue, 29 Sep 2015 16:49:15 +0200 [thread overview]
Message-ID: <560AA4EB.4050504@bouton.name> (raw)
In-Reply-To: <56080C9A.6030102@bouton.name>
Le 27/09/2015 17:34, Lionel Bouton a écrit :
> [...]
> It's not clear to me that "btrfs fi defrag <file>" can't interfere with
> another process trying to use the file. I assume basic reading and
> writing is OK but there might be restrictions on unlinking/locking/using
> other ioctls... Are there any I should be aware of and should look for
> in Ceph OSDs? This is on a 3.8.19 kernel (with Gentoo patches which
> don't touch BTRFS sources) with btrfs-progs 4.0.1. We have 5 servers on
> our storage network : 2 are running a 4.0.5 kernel and 3 are running
> 3.8.19. The 3.8.19 servers are waiting for an opportunity to reboot on
> 4.0.5 (or better if we have the time to test a more recent kernel before
> rebooting : 4.1.8 and 4.2.1 are our candidates for testing right now).
Apparently this isn't the problem : we just had another similar Ceph OSD
crash without any concurrent defragmentation going on.
Best regards,
Lionel Bouton
next prev parent reply other threads:[~2015-09-29 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 15:34 btrfs fi defrag interfering (maybe) with Ceph OSD operation Lionel Bouton
2015-09-28 0:18 ` Duncan
2015-09-28 9:55 ` Lionel Bouton
2015-09-28 20:52 ` Duncan
2015-09-28 21:55 ` Lionel Bouton
2015-09-29 14:49 ` Lionel Bouton [this message]
2015-09-29 17:14 ` Lionel Bouton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=560AA4EB.4050504@bouton.name \
--to=lionel-subscription@bouton.name \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).