>It's hosted on an EBS volume; we don't use ephemeral storage at all. The EBS
>volumes are all SSD
I have recently done some SSD corruption experiments on small set of
workloads, so I thought I would share my experience.
While creating btrfs using mkfs.btrfs command for SSDs, by default the
Austin S. Hemmelgarn posted on Fri, 16 Feb 2018 14:44:07 -0500 as
excerpted:
> This will probably sound like an odd question, but does BTRFS think your
> storage devices are SSD's or not? Based on what you're saying, it
> sounds like you're running into issues resulting from the
>
On 2018年02月16日 22:12, Ellis H. Wilson III wrote:
> On 02/15/2018 08:55 PM, Qu Wenruo wrote:
>> On 2018年02月16日 00:30, Ellis H. Wilson III wrote:
>>> Very helpful information. Thank you Qu and Hans!
>>>
>>> I have about 1.7TB of homedir data newly rsync'd data on a single
>>> enterprise 7200rpm
On Fri, Feb 16, 2018 at 07:51:38PM +, Dmitriy Gorokh wrote:
> On detaching of a disk which is a part of a RAID6 filesystem, the following
> kernel OOPS may happen:
>
> [63122.680461] BTRFS error (device sdo): bdev /dev/sdo errs: wr 0, rd 0,
> flush 1, corrupt 0, gen 0
> [63122.719584]
On detaching of a disk which is a part of a RAID6 filesystem, the following
kernel OOPS may happen:
[63122.680461] BTRFS error (device sdo): bdev /dev/sdo errs: wr 0, rd 0, flush
1, corrupt 0, gen 0
[63122.719584] BTRFS warning (device sdo): lost page write due to IO error on
/dev/sdo
On 2018-02-15 11:18, Alex Adriaanse wrote:
We've been using Btrfs in production on AWS EC2 with EBS devices for over 2
years. There is so much I love about Btrfs: CoW snapshots, compression,
subvolumes, flexibility, the tools, etc. However, lack of stability has been a
serious ongoing issue
Hi,
btrfs-progs version 4.15.1 have been released. This is a minor update with
build fixes, cleanups and test enhancements.
Changes:
* build
* fix build on musl
* support asciidoctor for doc generation
* cleanups
* sync some code with kernel
* check: move code to own directory, split to
Hi,
we have a few assorted fixes, some of them show up during fstests so
I gave them more testing. Please pull, thanks.
The following changes since commit 3acbcbfc8f06d4ade2aab2ebba0a2542a05ce90c:
btrfs: drop devid as
On 02/16/2018 09:42 AM, Ellis H. Wilson III wrote:
On 02/16/2018 09:20 AM, Hans van Kranenburg wrote:
Well, imagine you have a big tree (an actual real life tree outside) and
you need to pick things (e.g. apples) which are hanging everywhere.
So, what you need to to is climb the tree, climb on
On 02/16/2018 09:20 AM, Hans van Kranenburg wrote:
Well, imagine you have a big tree (an actual real life tree outside) and
you need to pick things (e.g. apples) which are hanging everywhere.
So, what you need to to is climb the tree, climb on a branch all the way
to the end where the first
On 02/16/2018 03:12 PM, Ellis H. Wilson III wrote:
> On 02/15/2018 08:55 PM, Qu Wenruo wrote:
>> On 2018年02月16日 00:30, Ellis H. Wilson III wrote:
>>> Very helpful information. Thank you Qu and Hans!
>>>
>>> I have about 1.7TB of homedir data newly rsync'd data on a single
>>> enterprise 7200rpm
On 02/15/2018 08:55 PM, Qu Wenruo wrote:
On 2018年02月16日 00:30, Ellis H. Wilson III wrote:
Very helpful information. Thank you Qu and Hans!
I have about 1.7TB of homedir data newly rsync'd data on a single
enterprise 7200rpm HDD and the following output for btrfs-debug:
extent tree key
On Fri, Feb 16, 2018 at 10:43:54AM +0800, Sampson Fung wrote:
> I have snapshot A on Drive_A.
> I send snapshot A to an empty Drive_B. Then keep Drive_A as backup.
> I use Drive_B as active.
> I create new snapshot B on Drive_B.
>
> Can I use btrfs send/receive to send incremental differences
13 matches
Mail list logo
