Re: ctree.c:197: update_ref_for_cow: BUG_ON `ret` triggered, value -5

On Fri, Jul 07, 2017 at 05:33:20PM +0800, Lu Fengqi wrote: > I apologise for my late reply. As a colleague left, I have to take over his > work recently. no worries. > >Mmmh, never mind, it seems that the software raid suffered yet another > >double disk failure due to some undermined flakiness

Re: btrfs device ready purpose

On Fri, Jul 7, 2017 at 10:59 AM, Andrei Borzenkov wrote: > 07.07.2017 19:42, Chris Murphy пишет: >> I'm digging through piles of list emails and not really finding an >> answer to this. Maybe it's Friday and I'm just confused... >> >> >> [root@f26s ~]# btrfs device ready

btrfs device ready purpose

I'm digging through piles of list emails and not really finding an answer to this. Maybe it's Friday and I'm just confused... [root@f26s ~]# btrfs device ready /dev/sda1 [root@f26s ~]# echo $? 0 [root@f26s ~]# btrfs device ready /dev/mapper/vg-1 [root@f26s ~]# echo $? 0 /dev/sda1 is a single

Re: Leveldb in google-chrome incompatible with btrfs?

(removing pwnall at chromium.org to cut spam) On Thu, Jul 06, 2017 at 10:46:08PM -0700, Omar Sandoval wrote: > ┌[osandov@vader ~/.config] > └$ ls -al google-chrome-busted/** > ls: cannot access 'google-chrome-busted/Local State': No such file or > directory > google-chrome-busted/Default: > ls:

Re: btrfs device ready purpose

07.07.2017 19:42, Chris Murphy пишет: > I'm digging through piles of list emails and not really finding an > answer to this. Maybe it's Friday and I'm just confused... > > > [root@f26s ~]# btrfs device ready /dev/sda1 > [root@f26s ~]# echo $? > 0 > [root@f26s ~]# btrfs device ready

Re: [PATCH v2] btrfs: Correct assignment of pos

On Tue, Jul 04, 2017 at 10:33:07PM -0500, Goldwyn Rodrigues wrote: > From: Goldwyn Rodrigues > > Assigning pos for usage early messes up in append mode, where > the pos is re-assigned in generic_write_checks(). Assign > pos later to get the correct position to write from

Re: [PATCH v2 3/4] btrfs: Add zstd support

On 7/6/17, 9:32 AM, "Adam Borowski" wrote: > On Thu, Jun 29, 2017 at 12:41:07PM -0700, Nick Terrell wrote: >> Add zstd compression and decompression support to BtrFS. zstd at its >> fastest level compresses almost as well as zlib, while offering much >> faster compression and

Re: [PATCH v2 3/4] btrfs: Add zstd support

On Fri, Jul 07, 2017 at 11:17:49PM +, Nick Terrell wrote: > On 7/6/17, 9:32 AM, "Adam Borowski" wrote: > > Got a reproducible crash on amd64: > > > > [98235.266511] BUG: unable to handle kernel paging request at > > c90001251000 > > [98235.314008] ?

Re: raid10 array lost with single disk failure?

Some additional information. I am running Rockstor just like Daniel Brady noted in his post just before mine titled "Chunk root problem". Sorry I am somewhat unfamiliar with newsgroups so I am not sure how to reply to his thread before I was subscribed. But I am noticing something in my logs very

Re: Commit edf064e7c (btrfs: nowait aio support) breaks shells

On 07/04/2017 05:16 PM, Jens Axboe wrote: > > Please expedite getting this upstream, asap. > Jens, I have posted an updated patch [1] and it is acked by David. Would you pick it up or should it go through the btrfs tree (or some other tree)? [1] https://patchwork.kernel.org/patch/9825813/

Re: Commit edf064e7c (btrfs: nowait aio support) breaks shells

On 07/07/2017 07:51 PM, Goldwyn Rodrigues wrote: > > > On 07/04/2017 05:16 PM, Jens Axboe wrote: >> >> Please expedite getting this upstream, asap. >> > > Jens, > > I have posted an updated patch [1] and it is acked by David. Would you > pick it up or should it go through the btrfs tree (or

Re: [PATCH v2 3/4] btrfs: Add zstd support

On Sat, Jul 08, 2017 at 01:40:18AM +0200, Adam Borowski wrote: > On Fri, Jul 07, 2017 at 11:17:49PM +, Nick Terrell wrote: > > On 7/6/17, 9:32 AM, "Adam Borowski" wrote: > > > Got a reproducible crash on amd64: > > > Thanks for the bug report Adam! I'm looking into the

raid10 array lost with single disk failure?

Hello all, I have a 18 device raid10 array that has recently stopped working. Seems like whenever my array tries to mount, it sits there with all disks doing I/O but never fully mounts. Eventually after a few minutes of attempting to mount the entire system locks up. This is as best I could get

[PATCH] Btrfs: incremental send, fix invalid memory access

From: Filipe Manana When doing an incremental send, while processing an extent that changed between the parent and send snapshots and that extent was an inline extent in the parent snapshot, it's possible to access a memory region beyond the end of leaf if the inline extent is

Re: ctree.c:197: update_ref_for_cow: BUG_ON `ret` triggered, value -5

On Thu, Jul 06, 2017 at 10:39:53PM -0700, Marc MERLIN wrote: >On Thu, Jul 06, 2017 at 10:37:18PM -0700, Marc MERLIN wrote: >> I'm still trying to fix my filesystem. >> It seems to work well enough since the damage is apparently localized, but >> I'd really want check --repair to actually bring it

Re: Leveldb in google-chrome incompatible with btrfs?

I was also struggling with this issue for quite some time. Today my 2 months old disk is crashed (which really surprises me). It doesn't even being shown by `fdisk -l`. After buying this this disk, I installed a Debian on a BTRFS partition on an LVM partition on a LUKS partition. From that day

Re: Chunk root problem

On 7/6/2017 11:48 PM, Roman Mamedov wrote: > On Wed, 5 Jul 2017 22:10:35 -0600 > Daniel Brady wrote: > >> parent transid verify failed > > Typically in Btrfs terms this means "you're screwed", fsck will not fix it, > and > nobody will know how to fix or what is the cause

[PATCH] Btrfs: fix early ENOSPC due to delalloc

From: Omar Sandoval If a lot of metadata is reserved for outstanding delayed allocations, we rely on shrink_delalloc() to reclaim metadata space in order to fulfill reservation tickets. However, shrink_delalloc() has a shortcut where if it determines that space can be

Re: Chunk root problem

On 7/6/2017 2:26 AM, Duncan wrote: > Daniel Brady posted on Wed, 05 Jul 2017 22:10:35 -0600 as excerpted: > >> My system suddenly decided it did not want to mount my BTRFS setup. I >> recently rebooted the computer. When it came back, the file system was >> in read only mode. I gave it another