- Original Message -
> From: "Qu Wenruo"
> To: "STEVE LEUNG" , linux-btrfs@vger.kernel.org
> Sent: Sunday, February 10, 2019 6:52:23 AM
> Subject: Re: corruption with multi-device btrfs + single bcache, won't mount
> - Original Message -
- Original Message -
> From: "Qu Wenruo"
> On 2019/2/10 下午2:56, STEVE LEUNG wrote:
>> Hi all,
>>
>> I decided to try something a bit crazy, and try multi-device raid1 btrfs on
>> top of dm-crypt and bcache. That is:
>>
>> btrfs -
- Original Message -
> From: "Thiago Ramon"
> On Sun, Feb 10, 2019 at 5:07 AM STEVE LEUNG wrote:
>>
>> Hi all,
>>
>> I decided to try something a bit crazy, and try multi-device raid1 btrfs on
>> top of dm-crypt and bcache. That is:
&
Hi all,
I decided to try something a bit crazy, and try multi-device raid1 btrfs on
top of dm-crypt and bcache. That is:
btrfs -> dm-crypt -> bcache -> physical disks
I have a single cache device in front of 4 disks. Maybe this wasn't
that good of an idea, because the filesystem went read-on
kard
Date: Wed Apr 25 16:34:54 2018 +0200
btrfs-progs: mkfs: traverse_directory: Reset error code on continue
Reported-by Steve Leung , his old btrfs (at least
offending inodes are from 2014) has inline uncompressed extent, while
its ram_bytes mismatch with item size.
Took a while t
On 06/04/2018 11:30 PM, Qu Wenruo wrote:
On 2018年05月29日 22:58, Steve Leung wrote:
Qu Wenruo writes:
On 2018年05月28日 11:47, Steve Leung wrote:
On 05/26/2018 06:57 PM, Qu Wenruo wrote:
[snip]
Still nope.
What about encrypt it and upload it to some public storage provider like
google
Qu Wenruo writes:
> On 2018年05月28日 11:47, Steve Leung wrote:
>> On 05/26/2018 06:57 PM, Qu Wenruo wrote:
>>>
>>>
>>> On 2018年05月26日 22:06, Steve Leung wrote:
>>>> On 05/20/2018 07:07 PM, Qu Wenruo wrote:
>>>>>
>>>>>
&g
On 05/26/2018 06:57 PM, Qu Wenruo wrote:
On 2018年05月26日 22:06, Steve Leung wrote:
On 05/20/2018 07:07 PM, Qu Wenruo wrote:
On 2018年05月21日 04:43, Steve Leung wrote:
On 05/19/2018 07:02 PM, Qu Wenruo wrote:
On 2018年05月20日 07:40, Steve Leung wrote:
On 05/17/2018 11:49 PM, Qu Wenruo wrote
On 05/20/2018 07:07 PM, Qu Wenruo wrote:
On 2018年05月21日 04:43, Steve Leung wrote:
On 05/19/2018 07:02 PM, Qu Wenruo wrote:
On 2018年05月20日 07:40, Steve Leung wrote:
On 05/17/2018 11:49 PM, Qu Wenruo wrote:
On 2018年05月18日 13:23, Steve Leung wrote:
Hi list,
I've got 3-device raid1
On 05/19/2018 07:02 PM, Qu Wenruo wrote:
On 2018年05月20日 07:40, Steve Leung wrote:
On 05/17/2018 11:49 PM, Qu Wenruo wrote:
On 2018年05月18日 13:23, Steve Leung wrote:
Hi list,
I've got 3-device raid1 btrfs filesystem that's throwing up some
"corrupt leaf" errors
On 05/17/2018 11:49 PM, Qu Wenruo wrote:
On 2018年05月18日 13:23, Steve Leung wrote:
Hi list,
I've got 3-device raid1 btrfs filesystem that's throwing up some
"corrupt leaf" errors in dmesg. This is a uniquified list I've
observed lately:
Evidently I forgot that I adde
Hi list,
I've got 3-device raid1 btrfs filesystem that's throwing up some
"corrupt leaf" errors in dmesg. This is a uniquified list I've
observed lately:
BTRFS critical (device sda1): corrupt leaf: root=1
block=4970196795392 slot=307 ino=206231 file_offset=0, invalid ram_bytes
for uncompres
On 10/12/2017 11:44 AM, Steve Leung wrote:
Hi list,
TL;DR: ran into some btrfs errors and weird behaviour, but things generally
seem
to work. Just posting some details in case it helps devs or other users.
I've run into a btrfs error trying to do a -j8 build of android on a
Hi list,
TL;DR: ran into some btrfs errors and weird behaviour, but things generally
seem
to work. Just posting some details in case it helps devs or other users.
I've run into a btrfs error trying to do a -j8 build of android on a btrfs
filesystem exported over NFSv3. That in itself mi
On Fri, 25 Apr 2014, Chris Murphy wrote:
On Apr 25, 2014, at 12:43 PM, Steve Leung wrote:
Once everything gets rebalanced though, I don't think I'd be missing out on any
features, would I?
The default nodesize/leafsize is 16KB since btrfs-progs v3.12. This
isn't changed
On 04/25/2014 11:24 AM, Chris Murphy wrote:
On Apr 25, 2014, at 8:57 AM, Steve Leung wrote:
I've got a 3-device RAID1 btrfs filesystem that started out life as
single-device.
btrfs fi df:
Data, RAID1: total=1.31TiB, used=1.07TiB
System, RAID1: total=32.00MiB, used=224.00KiB
System
On 04/25/2014 12:12 PM, Austin S Hemmelgarn wrote:
On 2014-04-25 13:24, Chris Murphy wrote:
On Apr 25, 2014, at 8:57 AM, Steve Leung wrote:
I've got a 3-device RAID1 btrfs filesystem that started out life as
single-device.
btrfs fi df:
Data, RAID1: total=1.31TiB, used=1.07TiB
S
Hi list,
I've got a 3-device RAID1 btrfs filesystem that started out life as
single-device.
btrfs fi df:
Data, RAID1: total=1.31TiB, used=1.07TiB
System, RAID1: total=32.00MiB, used=224.00KiB
System, DUP: total=32.00MiB, used=32.00KiB
System, single: total=4.00MiB, used=0.00
Metadata, R
I'm getting some kernel warnings from a btrfs raid1 filesystem that's
serving up nfs4 to a couple of other computers on a small home network.
I ran 3.6.x for several weeks before upgrading and didn't see any warnings
like this.
[ 1712.223791] WARNING: at fs/btrfs/tree-log.c:3716
btrfs_log_i
19 matches
Mail list logo
