Dāvis Mosāns | 1 Sep 02:08 2015
Picon

Re: [BUG] kernel BUG at fs/btrfs/extent_io.c:2062 (v4.2.0-rc8)

2015-08-31 18:14 GMT+00:00 Dāvis Mosāns <davispuh <at> gmail.com>:
> I'm getting kernel crash and complete system lockup when trying to access
> journal on two disk btrfs filesystem with data/metadata as RAID1.
>
> I can't get proper log because whole system hangs and even kdump fails,
> seems it doesn't start or I'm doing something wrong.
>
> Also because there are several call traces and they all get printed on
> screen within few seconds I can get photos only on few last ones.
> But I managed to get some low-quality blurry photos with 80 FPS
> recording.
>
> So from them I saw
>
> kernel BUG at fs/btrfs/extent_io.c:2062
> extent_io.c <at> 2062.png => http://i.imgur.com/uuxOGIR.png
>
> kernel BUG at fs/btrfs/extent_io.c:2140
> extent_io.c <at> 2140.png => http://i.imgur.com/j5xrt7w.png
>
> kernel BUG at fs/btrfs/extent_io.c:2338
> extent_io.c <at> 2338_0.png => http://i.imgur.com/EosplAu.png
> extent_io.c <at> 2338_1.png => http://i.imgur.com/rsE9qNT.png
>
> kernel BUG at fs/btrfs/volumes.c:5399
> volumes.c <at> 5399_0.png => http://i.imgur.com/iV9zqAv.png
> volumes.c <at> 5399_1.png => http://i.imgur.com/VCyr07R.png
>
>
> And better photos
(Continue reading)

sam tygier | 31 Aug 20:48 2015
Picon

[PATCH] Btrfs: Check metadata redundancy on balance

Resending, as I received no comments on previous submission.

Currently BTRFS allows you to make bad choices of data and 
metadata levels. For example -d raid1 -m raid0 means you can
only use half your total disk space, but will loose everything
if 1 disk fails. It should give a warning in these cases.

This patch is a follow up to
[PATCH v2] btrfs-progs: check metadata redundancy
in order to cover the case of using balance to convert to such
a set of raid levels.

A simple example to hit this is to create a single device fs, 
which will default to single:dup, then to add a second device and
attempt to convert to raid1 with the command
btrfs balance start -dconvert=raid1  /mnt
this will result in a filesystem with raid1:dup, which will not
survive the loss of one drive. I personally don't see why the tools
should allow this, but in the previous thread a warning was
considered sufficient.

Signed-off-by: Sam Tygier <samtygier <at> yahoo.co.uk>

From: Sam Tygier <samtygier <at> yahoo.co.uk>
Date: Sat, 13 Jun 2015 18:13:06 +0100
Subject: [PATCH] Btrfs: Check metadata redundancy on balance

When converting a filesystem via balance check that metadata mode
is at least as redundant as the data mode. For example give warning
when:
(Continue reading)

Vincent Olivier | 31 Aug 20:34 2015

errors while "btrfs receive"

hi,

i'm doing a ~900TiB receive on a 6x4TB RAID0

"fi show", "device scan" all fail and report "unable to connect to /dev/sdX"

is it normal ?

thanks,

Vincent

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Dāvis Mosāns | 31 Aug 20:14 2015
Picon

[BUG] kernel BUG at fs/btrfs/extent_io.c:2062 (v4.2.0-rc8)

I'm getting kernel crash and complete system lockup when trying to access
journal on two disk btrfs filesystem with data/metadata as RAID1.

I can't get proper log because whole system hangs and even kdump fails,
seems it doesn't start or I'm doing something wrong.

Also because there are several call traces and they all get printed on
screen within few seconds I can get photos only on few last ones.
But I managed to get some low-quality blurry photos with 80 FPS
recording.

So from them I saw

kernel BUG at fs/btrfs/extent_io.c:2062
extent_io.c <at> 2062.png => http://i.imgur.com/uuxOGIR.png

kernel BUG at fs/btrfs/extent_io.c:2140
extent_io.c <at> 2140.png => http://i.imgur.com/j5xrt7w.png

kernel BUG at fs/btrfs/extent_io.c:2338
extent_io.c <at> 2338_0.png => http://i.imgur.com/EosplAu.png
extent_io.c <at> 2338_1.png => http://i.imgur.com/rsE9qNT.png

kernel BUG at fs/btrfs/volumes.c:5399
volumes.c <at> 5399_0.png => http://i.imgur.com/iV9zqAv.png
volumes.c <at> 5399_1.png => http://i.imgur.com/VCyr07R.png

And better photos

BUG: scheduling while atomic: kworker/u16
(Continue reading)

Néstor Uribe-Patarroyo | 31 Aug 20:06 2015

Kernel bug after changing raid levels

I've filed bug https://bugzilla.kernel.org/show_bug.cgi?id=103811 on a 
recent kernel bug I've encountered using btrfs after changing raid level 
online.

Let me know if there's any more info I can provide, I haven't formatted 
that file system yet.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Zhao Lei | 31 Aug 13:03 2015

[PATCH v2 0/4] btrfs-progs: Use common function to parse unit arguments

We are using separate code for parse unit mode in current code,
better to use common function.

This patchset introduce common function to parse arguments for setting
unit: get_unit_mode_from_arg()
and common help message for unit argument, to make every tool in btrfs having
same interface for setting unit.

The merit are:
1: Unify current each tool's arguments for unit
2: Make tools in future easy to implement such argument
3: Changes(enhancement) in common function have effect on all
   relative tools

Changelog v1->v2:
 Keep short options for 'fi df' command, to keeps option compatibility
 with the standalone 'df' commmand, suggested-by:
 David Sterba <dsterba <at> suse.cz>

Zhao Lei (4):
  btrfs-progs: Introduce get_unit_mode_from_arg for common use
  btrfs-progs: Use common unit parser for btrfs filesystem command
  btrfs-progs: Use common unit parser for btrfs device command
  btrfs-progs: Use common unit parser for btrfs qgroup command

 cmds-device.c     |  74 ++++-----------------------------
 cmds-fi-usage.c   |  79 ++++-------------------------------
 cmds-filesystem.c | 121 ++++++------------------------------------------------
 cmds-qgroup.c     |  47 ++-------------------
 utils.c           | 102 +++++++++++++++++++++++++++++++++++++++++++++
(Continue reading)

Zhao Lei | 31 Aug 07:04 2015

[PATCH v2 0/4] btrfs-progs: tests: umount TEST_MNT in clean-tests.sh

If a testcase failed, we can't run it(or other tests needs mount) again,
  # ./misc-tests.sh 007
   [TEST]   007-subvolume-sync
   failed: fail
   test failed for case 007-subvolume-sync
  # ./misc-tests.sh 007
   [TEST]   007-subvolume-sync
   failed: mount /root/btrfs-progs/tests/test.img /root/btrfs-progs/tests/mnt
   test failed for case 007-subvolume-sync
  #

To solve this problem, I put umount command into test sctipt in v1,
but it will change stat of failed-test in next test, and make it
hard to debug, noticed by David Sterba <dsterba <at> suse.cz>:
 My expectation is that the testsuite will not fail and if it does,
 I wan't to keep the last stat so I can have a look.
 Would it be acceptable for you to enhance the clean-tests.sh
 script to unmount the TEST_DEV?

Putting umount command into clean-tests.sh need a global $TEST_MNT,
which already done in my previous patch.

This patchset rebase my previous patch of "setting global $TEST_MNT"
to git head in [PATCH 1..2/4], and add v2 of "umount TEST_MNT"
in [PATCH 3/4].

Thanks
Zhaolei

Zhao Lei (4):
(Continue reading)

Alexandru Moise | 30 Aug 23:45 2015
Picon

[PATCH] btrfs: cleanup btrfs_balance profile validity checks

Improve readability by generalizing the profile validity checks,
I had to read through those if statements half a dozen times on my
first try just to get an idea of what's happening there.

Signed-off-by: Alexandru Moise <00moses.alexander00 <at> gmail.com>
---
 fs/btrfs/volumes.c | 21 ++++++++++++---------
 1 file changed, 12 insertions(+), 9 deletions(-)

diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index fbe7c10..d23bc26 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
 <at>  <at>  -3454,6 +3454,15  <at>  <at>  static void __cancel_balance(struct btrfs_fs_info *fs_info)
 	atomic_set(&fs_info->mutually_exclusive_operation_running, 0);
 }

+/* Non-zero return value signifies invalidity */
+static inline int balance_relocate_invalid(struct btrfs_balance_args *bctl_arg,
+		u64 allowed)
+{
+	return ((bctl_arg->flags & BTRFS_BALANCE_ARGS_CONVERT) &&
+		(!alloc_profile_is_valid(bctl_arg->target, 1) ||
+		 (bctl_arg->target & ~allowed)));
+}
+
 /*
  * Should be called with both balance and volume mutexes held
  */
 <at>  <at>  -3511,27 +3520,21  <at>  <at>  int btrfs_balance(struct btrfs_balance_control *bctl,
(Continue reading)

Chris Murphy | 30 Aug 19:17 2015

mount command now shows subvol and subvolid

Does anyone know when this changed? Maybe it's a 4.2 thing... anyway
it's very much welcome!

/dev/sda2 on /home type btrfs
(rw,relatime,seclabel,space_cache,subvolid=258,subvol=/home)

/dev/sdc1 on /brick0 type btrfs
(rw,relatime,seclabel,space_cache,subvolid=5,subvol=/)

/dev/sde on /brick1 type btrfs
(rw,relatime,seclabel,space_cache,subvolid=5,subvol=/)

--

-- 
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Chandan Rajendra | 30 Aug 16:46 2015
Picon

[PATCH] generic/224: Increase filesystem instance size to 1.5 GiB

For small filesystem instances (i.e. size <= 1 GiB), mkfs.btrfs fails when
"data block size" does not match with the "metadata block size" specified on
the mkfs.btrfs command line. This commit increases the size of filesystem
instance created so that the test can be executed on subpagesize-blocksize
Btrfs instances which have different values for data and metadata blocksizes.

Increasing the filesystem size had a negligible impact on the runtime of the
test as indicated by the following table:

|------------+--------------+----------------|
| Filesystem | 1GiB FS size | 1.5GiB FS size |
|------------+--------------+----------------|
| Btrfs      | 21secs       | 24secs         |
| Ext4       | 12secs       | 15secs         |
| Xfs        | 10secs       | 11secs         |
|------------+--------------+----------------|

Timing information reported in the above table were the worst-case times
observed when running the test on a spinning disk.

Signed-off-by: Chandan Rajendra <chandan <at> linux.vnet.ibm.com>
---
 tests/generic/224 | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/tests/generic/224 b/tests/generic/224
index 391d877..8fae187 100755
--- a/tests/generic/224
+++ b/tests/generic/224
 <at>  <at>  -53,8 +53,9  <at>  <at>  _supported_os Linux
(Continue reading)

jerryfunds4 | 30 Aug 04:10 2015

(unknown)

We Give Out Loans For 3% Interest Rate And We Offer Loans From $5,000 To $50,000,000.00, Are You Looking To
Buy A House Car Or Company Or Start Up A Truck Company or Buy A Truck Or Personal Loans, Email Us At
j.funds2000000 <at> inbox.lv  With Amount Needed And Phone Number.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Gmane