[PATCH] btrfs-progs: docs: correct grammar

Signed-off-by: Benjamin Peterson --- Documentation/mkfs.btrfs.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/mkfs.btrfs.asciidoc b/Documentation/mkfs.btrfs.asciidoc index d53d9e26..62f5a5be 100644 ---

Re: kernel BUG at fs/btrfs/ctree.h:3457

> Please skip that patch, as the check timing has its problem. > Okay, I'll skip the patch and run the tests hereafter. thanks. Cheers, Lakshmipathi.G http://www.giis.co.in http://www.webminal.org -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a

[PATCH] btrfs: tree-checker: Fix false panic for sanity test

[BUG] If we run btrfs with CONFIG_BTRFS_FS_RUN_SANITY_TESTS=y, it will instantly cause kernel panic like: -- ... assertion failed: 0, file: fs/btrfs/disk-io.c, line: 3853 ... Call Trace: btrfs_mark_buffer_dirty+0x187/0x1f0 [btrfs] setup_items_for_insert+0x385/0x650 [btrfs]

Re: kernel BUG at fs/btrfs/ctree.h:3457

Seems like output is messed by my email client: Here is formatted one: https://bugzilla.kernel.org/show_bug.cgi?id=197587#c6 Cheers, Lakshmipathi.G http://www.giis.co.in http://www.webminal.org On Mon, Nov 6, 2017 at 10:47 AM, Lakshmipathi.G wrote: > Hi. > >

Re: kernel BUG at fs/btrfs/ctree.h:3457

On 2017年11月06日 13:17, Lakshmipathi.G wrote: > Hi. > > While running xfstests/065 with 4.14.0-rc7 and latest btrfs-progs > from devel branch, it crashes the system after dumping below log: > (Note: For btrfs-devel, I'm still using SANITY_TESTS=y and > FS_INTEGRITY=y and applied patch >

kernel BUG at fs/btrfs/ctree.h:3457

Hi. While running xfstests/065 with 4.14.0-rc7 and latest btrfs-progs from devel branch, it crashes the system after dumping below log: (Note: For btrfs-devel, I'm still using SANITY_TESTS=y and FS_INTEGRITY=y and applied patch https://patchwork.kernel.org/patch/10038011/) Nov 06 05:08:09

[PATCH 2/2] btrfs: compression: Return correct default zlib compression level

0 means no compression at all for zlib. Z_DEFAULT_COMPRESSION is the correct value, which is -1 and will be converted to 6 at runtime. Signed-off-by: Qu Wenruo --- fs/btrfs/compression.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git

[PATCH 1/2] btrfs: Fix wild memory access in compression level parser

[BUG] Kernel panic when mounting with "-o compress" mount option. KASAN will report like: -- == BUG: KASAN: wild-memory-access in strncmp+0x31/0xc0 Read of size 1 at addr d86735fce994f800 by task mount/662 ... Call Trace:

Re: [PATCH 06/11] btrfs: document device locking

On 11/03/2017 07:13 PM, Anand Jain wrote: Thanks for writing this. + * - fs_devices::device_list_mutex (per-fs, with RCU) + * + * protects updates to fs_devices::devices, ie. adding and deleting + * + * simple list traversal with read-only actions can be done with RCU + * protection

[PATCH] btrfs: move volume_mutex into the btrfs_rm_device()

A cleanup patch no functional change, we hold volume_mutex before calling btrfs_rm_device, so move it into the function itself. Signed-off-by: Anand Jain --- David, This patch is based on your workspace/for-next plus your recent patchset '[PATCH 00/11] Device fixes and

Re: [PATCH 05/11] btrfs: simplify exit paths in btrfs_init_new_device

looks good. Reviewed-by: Anand Jain Thanks, Anand On 11/01/2017 01:44 AM, David Sterba wrote: Signed-off-by: David Sterba --- fs/btrfs/volumes.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/fs/btrfs/volumes.c

Re: Fixed subject: updatedb does not index separately mounted btrfs subvolumes

>> The issue is that updatedb by default will not index bind >> mounts, but by default on Fedora and probably other distros, >> put /home on a subvolume and then mount that subvolume which >> is in effect a bind mount. > > So the issue isn't /home being btrfs (as you said in the > subject), but

Re: Fixed subject: updatedb does not index separately mounted btrfs subvolumes

On Sun, Nov 5, 2017 at 1:47 AM, Duncan <1i5t5.dun...@cox.net> wrote: > Chris Murphy posted on Fri, 03 Nov 2017 18:15:53 -0600 as excerpted: > >> Ancient bug, still seems to be a bug. >> https://bugzilla.redhat.com/show_bug.cgi?id=906591 >> >> The issue is that updatedb by default will not index

btrfs-progs:fuzz-tests/003-multi-check-unmounted broken?

Hi. Seems like fuzz-test/003 is broken for quite sometime now (it works on v4.7.3 but not after that). Can anyone else able to run this test successfully? If this test is not required anymore, shall we remove it from fuzz-tests? TEST=003\* tests/fuzz-tests.sh [TEST/fuzz]

Re: updatedb does not index /home when /home is Btrfs

04.11.2017 21:55, Chris Murphy пишет: > On Sat, Nov 4, 2017 at 12:27 PM, Andrei Borzenkov wrote: >> 04.11.2017 10:05, Adam Borowski пишет: >>> On Sat, Nov 04, 2017 at 09:26:36AM +0300, Andrei Borzenkov wrote: 04.11.2017 07:49, Adam Borowski пишет: > On Fri, Nov 03,

Fixed subject: updatedb does not index separately mounted btrfs subvolumes

Chris Murphy posted on Fri, 03 Nov 2017 18:15:53 -0600 as excerpted: > Ancient bug, still seems to be a bug. > https://bugzilla.redhat.com/show_bug.cgi?id=906591 > > The issue is that updatedb by default will not index bind mounts, but by > default on Fedora and probably other distros, put /home

Re: Parity-based redundancy (RAID5/6/triple parity and beyond) on BTRFS and MDADM (Dec 2014) – Ronny Egners Blog

waxhead posted on Thu, 02 Nov 2017 23:06:41 +0100 as excerpted: > Dave wrote: >> >> TL;DR: There are patches to extend the linux kernel to support up to 6 >> parity disks but BTRFS does not want them because it does not fit their >> “business case” and MDADM would want them but somebody needs to