On 05/06/15 20:28, Lionel Bouton wrote:
Hi,
On 05/06/15 20:07, Timofey Titovets wrote:
2015-05-06 20:51 GMT+03:00 Lionel Bouton lionel+c...@bouton.name:
Is there something that would explain why initially Btrfs creates the
4MB files with 128k extents (32 extents / file) ? Is it a bad thing
On 05/06/15 19:51, Lionel Bouton wrote:
During normal operation Btrfs OSD volumes continue to behave in the same
way XFS ones do on the same system (sometimes faster/sometimes slower).
What is really slow though it the OSD process startup. I've yet to make
serious tests (umounting the
Hi,
On 05/07/2015 12:04 PM, Lionel Bouton wrote:
On 05/06/15 19:51, Lionel Bouton wrote:
*snipsnap*
We've seen progress on this front. Unfortunately for us we had 2 power
outages and they seem to have damaged the disk controller of the system
we are testing Btrfs on: we just had a system
Hi,
On 05/07/15 12:30, Burkhard Linke wrote:
[...]
Part of the OSD boot up process is also the handling of existing
snapshots and journal replay. I've also had several btrfs based OSDs
that took up to 20-30 minutes to start, especially after a crash.
During journal replay the OSD daemon
Hi,
On 05/06/15 20:07, Timofey Titovets wrote:
2015-05-06 20:51 GMT+03:00 Lionel Bouton lionel+c...@bouton.name:
Is there something that would explain why initially Btrfs creates the
4MB files with 128k extents (32 extents / file) ? Is it a bad thing for
performance ?
This kind of behaviour
On 05/05/15 02:24, Lionel Bouton wrote:
On 05/04/15 01:34, Sage Weil wrote:
On Mon, 4 May 2015, Lionel Bouton wrote:
Hi,
we began testing one Btrfs OSD volume last week and for this first test
we disabled autodefrag and began to launch manual btrfs fi defrag.
[...]
Cool.. let us know how
On 05/06/2015 12:51 PM, Lionel Bouton wrote:
On 05/05/15 02:24, Lionel Bouton wrote:
On 05/04/15 01:34, Sage Weil wrote:
On Mon, 4 May 2015, Lionel Bouton wrote:
Hi,
we began testing one Btrfs OSD volume last week and for this first test
we disabled autodefrag and began to launch manual
On 05/05/15 06:30, Timofey Titovets wrote:
Hi list,
Excuse me, what I'm saying is off topic
@Lionel, if you use btrfs, did you already try to use btrfs compression for
OSD?
If yes, сan you share the your experience?
Btrfs compresses by default using zlib. We force lzo compression instead
Hi list,
Excuse me, what I'm saying is off topic
@Lionel, if you use btrfs, did you already try to use btrfs compression for OSD?
If yes, сan you share the your experience?
2015-05-05 3:24 GMT+03:00 Lionel Bouton lionel+c...@bouton.name:
On 05/04/15 01:34, Sage Weil wrote:
On Mon, 4 May 2015,
On 05/04/15 01:34, Sage Weil wrote:
On Mon, 4 May 2015, Lionel Bouton wrote:
Hi,
we began testing one Btrfs OSD volume last week and for this first test
we disabled autodefrag and began to launch manual btrfs fi defrag.
[...]
Cool.. let us know how things look after it ages!
We had the
On Mon, 4 May 2015, Lionel Bouton wrote:
Hi,
we began testing one Btrfs OSD volume last week and for this first test
we disabled autodefrag and began to launch manual btrfs fi defrag.
During the tests, I monitored the number of extents of the journal
(10GB) and it went through the roof
Hi,
we began testing one Btrfs OSD volume last week and for this first test
we disabled autodefrag and began to launch manual btrfs fi defrag.
During the tests, I monitored the number of extents of the journal
(10GB) and it went through the roof (it currently sits at 8000+ extents
for example).
On 05/04/15 01:34, Sage Weil wrote:
On Mon, 4 May 2015, Lionel Bouton wrote:
Hi, we began testing one Btrfs OSD volume last week and for this
first test we disabled autodefrag and began to launch manual btrfs fi
defrag. During the tests, I monitored the number of extents of the
journal (10GB)
13 matches
Mail list logo
