Re: Infinite loop/hang in in btrfs_find_space_cluster()

On Tue, Apr 19, 2016 at 02:51:33PM -0700, Eric Wheeler wrote: > On Wed, 13 Apr 2016, Eric Wheeler wrote: > > > Hello all, > > > > We just got this backtrace in 4.4.6 on an ARM AM335x (beaglebone > > compatible). The trace looks similar to this one: > >

Re: Question: raid1 behaviour on failure

Matthias Bodenbinder wrote on 2016/04/21 07:22 +0200: Am 20.04.2016 um 09:25 schrieb Qu Wenruo: Unfortunately, this is the designed behavior. The fs is rw just because it doesn't hit any critical problem. If you try to touch a file and then sync the fs, btrfs will become RO immediately.

Re: KERNEL PANIC + CORRUPTED BTRFS?

On Wed, Apr 20, 2016 at 10:09:07PM +0200, lenovomi wrote: > Hi Chris, > > please find below attached the complete log while executing all the > brtrfs commands, all of them failed. > > ;-( > > > https://bpaste.net/show/4d8877a49b80 > https://bpaste.net/show/7e2e5aa30741 >

Re: Question: raid1 behaviour on failure

Am 20.04.2016 um 09:25 schrieb Qu Wenruo: > > Unfortunately, this is the designed behavior. > > The fs is rw just because it doesn't hit any critical problem. > > If you try to touch a file and then sync the fs, btrfs will become RO > immediately. > > Btrfs fails to read space cache,

Re: Question: raid1 behaviour on failure

Am 20.04.2016 um 15:32 schrieb Anand Jain: >> 1. mount the raid1 (2 disc with different size) > >> 2. unplug the biggest drive (hotplug) > > Btrfs won't know that you have plugged-out a disk. > Though it experiences IO failures, it won't close the bdev. Well, as far as I can tell mdadm can

Re: Kernel crash if both devices in raid1 are failing

On Mon, Apr 18, 2016 at 01:18:31AM +0200, Dmitry Katsubo wrote: > On 2016-04-14 22:30, Dmitry Katsubo wrote: > > Dear btrfs community, > > > > I have the following setup: > > > > # btrfs fi show /home > > Label: none uuid: 865f8cf9-27be-41a0-85a4-6cb4d1658ce3 > > Total devices 3 FS bytes

BTRFS: assertion failed: num_extents, file: fs/btrfs/extent-tree.c, line: 5584

Don't think I've reported this one before. It's on the same box I've been seeing the btrfs_destroy_inode WARN_ON's on though. Dave BTRFS: assertion failed: num_extents, file: fs/btrfs/extent-tree.c, line: 5584 [ cut here ] kernel BUG at fs/btrfs/ctree.h:4320!

Re: Kernel crash if both devices in raid1 are failing

On 2016-04-19 09:58, Duncan wrote: > Dmitry Katsubo posted on Tue, 19 Apr 2016 07:45:40 +0200 as excerpted: > >> Actually btrfs restore has recovered many files, however I was not able >> to run in fully unattended mode as it complains about "looping a lot". >> Does it mean that files are

Re: KERNEL PANIC + CORRUPTED BTRFS?

On Wed, Apr 20, 2016 at 2:09 PM, lenovomi wrote: > Hi Chris, > > please find below attached the complete log while executing all the > brtrfs commands, all of them failed. > > https://bpaste.net/show/482e91b25fc5 >warning, device 1 is missing >warning, device 2 is missing

Re: KERNEL PANIC + CORRUPTED BTRFS?

Hi Chris, please find below attached the complete log while executing all the brtrfs commands, all of them failed. ;-( https://bpaste.net/show/4d8877a49b80 https://bpaste.net/show/7e2e5aa30741 https://bpaste.net/show/482e91b25fc5 https://bpaste.net/show/5093cc3daa5a

btrfs-progs confusing message

Pretty much all commands print out the usage message when no device is specified: [root@host ~]# btrfs scrub start btrfs scrub start: too few arguments usage: btrfs scrub start [-BdqrRf] [-c ioprio_class -n ioprio_classdata] | ... However, balance doesn't [root@host ~]# btrfs balance start

Re: [PATCH v8 00/27][For 4.7] Btrfs: Add inband (write time) de-duplication framework

On Wed, Apr 20, 2016 at 10:02:27AM +0800, Qu Wenruo wrote: > Hi David, > > Any new comment about the ondisk format and ioctl interface? Hi Qu, I'm at LSF this week but will dig through again on the way home. Thanks! -chris -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH v4] btrfs: qgroup: Fix qgroup accounting when creating snapshot

On Tue, 19 Apr 2016 15:19:46 -0700, Mark Fasheh wrote: > On Fri, Apr 15, 2016 at 05:08:22PM +0800, Qu Wenruo wrote: >> Current btrfs qgroup design implies a requirement that after calling >> btrfs_qgroup_account_extents() there must be a commit root switch. >> >> Normally this is OK, as

Re: Question: raid1 behaviour on failure

1. mount the raid1 (2 disc with different size) 2. unplug the biggest drive (hotplug) Btrfs won't know that you have plugged-out a disk. Though it experiences IO failures, it won't close the bdev. 3. try to copy something to the degraded raid1 This will work as long as you do

Re: btrfs-image and btrfs send related queries

Sorry. Its typo I used original disk /dev/sdb where filesystem is created and seeing these errors. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Question: raid1 behaviour on failure

Matthias Bodenbinder wrote on 2016/04/20 07:17 +0200: Am 18.04.2016 um 09:22 schrieb Qu Wenruo: BTW, it would be better to post the dmesg for better debug. So here we. I did the same test again. Here is a full log of what i did. It seems to be mean like a bug in btrfs. Sequenz of events:

[PATCH] btrfs-progs: prop: remove an unnecessary condition on parse_args

>From commit c742debab11f ('btrfs-progs: fix a regression that "property" with -t option doesn't work'), the number of arguments is checked strictly. So the following condition never be satisfied. Signed-off-by: Satoru Takeuchi --- cmds-property.c | 5 - 1