Re: [PATCH] btrfs: move btrfs_compression_type to compression.h

Hi Anand, [auto build test ERROR on v4.5-rc7] [cannot apply to btrfs/next next-20160309] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Anand-Jain/btrfs-move-btrfs_compression_type

Re: [PATCH] btrfs: move btrfs_compression_type to compression.h

Hi Anand, [auto build test ERROR on v4.5-rc7] [cannot apply to btrfs/next next-20160309] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Anand-Jain/btrfs-move-btrfs_compression_type

Re: [PATCH] btrfs-progs: Replace hardcoded PAGE_CACHE_SIZE with getpagesize().

On 2016/3/9 20:45, David Sterba wrote: On Wed, Mar 09, 2016 at 08:22:13PM +0800, Feifei Xu wrote: PAGE_CACHE_SIZE is hardcoded to 4K in cmds-restore.c. It makes lzo decompress fail on ppc64. Fix this through replacing hardcoded 4K with getpagesize(). You're right that the hardcoded value is

Re: dstat shows unexpected result for two disk RAID1

On Wed, Mar 9, 2016 at 9:06 PM, Duncan <1i5t5.dun...@cox.net> wrote: > Tho hopefully all the really tough problems they would have hit with N- > way-mirroring were hit and resolved with raid56, and N-way-mirroring will > thus be relatively simple, so hopefully it's less than the four years > it's

[PATCH] btrfs: move btrfs_compression_type to compression.h

So that its better organized. Signed-off-by: Anand Jain --- fs/btrfs/compression.h | 9 + fs/btrfs/ctree.h| 8 fs/btrfs/disk-io.c | 1 + fs/btrfs/extent_map.c | 1 + fs/btrfs/file-item.c| 1 + fs/btrfs/file.c | 1 +

[PATCH] btrfs: rename btrfs_print_info to btrfs_print_mod_info

So that it indicates what it does. Signed-off-by: Anand Jain --- fs/btrfs/super.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c index 29836ca..3b5b192 100644 --- a/fs/btrfs/super.c +++ b/fs/btrfs/super.c @@

[PATCH v2 RESEND] btrfs: maintain consistency in logging to help debugging

Optional Label may or may not be set, or it might be set at some time later. However while debugging to search through the kernel logs the scripts would need the logs to be consistent, so logs search key words shouldn't depend on the optional variables, instead fsid is better. Signed-off-by:

[PATCH RESEND] Btrfs: fix fs logging for multi device

In case of multi device btrfs fs, using one of device for the logging purpose is quite confusing, instead use the fsid. FSID is bit long, but the device path can be long as well in some cases. Signed-off-by: Anand Jain --- fs/btrfs/super.c | 4 ++-- 1 file changed, 2

[PATCH v2 RESEND] btrfs: device path change must be logged

>From the issue diagnosable point of view, log if the device path is changed. Signed-off-by: Anand Jain --- V2: Accepts David's review comment and adds a new ret value 2 for device_list_add() and based on that the caller function would indicate if the path is

[PATCH V2 RESEND] btrfs: pass the error code to the btrfs_std_error and log ret

This patch will log return value of add/del_qgroup_relation() and pass the err code of btrfs_run_qgroups to the btrfs_std_error(). Signed-off-by: Anand Jain --- v2: fix the forgotten git commit amend, to take in compile fail, sorry fs/btrfs/ioctl.c | 7 ++- 1 file

КЛИЕНТСКИЕ БАЗЫ! Тел\Viber\Whatsapp: +79133913837 Email: aburo...@gmail.com Skype: prodawez389

КЛИЕНТСКИЕ БАЗЫ! Соберем для Вас по интернет базу данных потенциальных клиентов для Вашего Бизнеса! Много! Быстро! Недорого! Узнайте об этом подробнее по Тел: +79133913837 Viber: +79133913837 Whatsapp: +79133913837 Skype: prodawez389 Email: aburo...@gmail.com -- To unsubscribe from this list:

Re: dstat shows unexpected result for two disk RAID1

Roman Mamedov posted on Thu, 10 Mar 2016 02:36:27 +0500 as excerpted: > It's a known limitation that the disks are in effect "pinned" to running > processes, based on their process ID. One process reads from the same > disk, from the point it started and until it terminates. Other processes > by

Re: [PATCH V4 2/2] btrfs-progs: Introduce device delete by devid

Please send any followup changes on top of the current devel patch. I kind of missed this point at the wiki. -- The git repositories on kernel.org are not used for development or integration branches. -- Thanks for the update on how things work at your end, which helps to keep

Re: btrfs and containers

Austin S. Hemmelgarn posted on Wed, 09 Mar 2016 07:15:36 -0500 as excerpted: > On 2016-03-08 16:28, Chris Murphy wrote: >> Yes, it's a bit peculiar I can create subvolumes and snapshot them, but >> can't 'btrfs sub list/show' >> >> It's an open question why the user needs a subvolume, but I'm

Re: [RFC PATCH 1/1] btrfs: Encryption: Add btrfs encryption support

On Wed, Mar 02, 2016 at 12:08:10AM +0800, Anand Jain wrote: > *** > *** Warning: Experimental code. > *** > > Adds encryption support. The branch is based on v4.5-rc6. > > Signed-off-by: Anand Jain > --- > fs/btrfs/Makefile | 2 +- > fs/btrfs/btrfs_inode.h | 2 +

Re: [PATCH] Documentation: btrfs: remove usage specific information

On 03/10/2016 01:11 AM, David Sterba wrote: On Wed, Mar 09, 2016 at 10:26:51AM +0900, Satoru Takeuchi wrote: +that maintains information about administration tasks, frequently asked +questions, use cases, mount options, comprehensible changelogs, features, +manual pages, source code

Re: [PATCH v7 01/20] btrfs: dedup: Introduce dedup framework and its header

NeilBrown wrote on 2016/03/10 08:27 +1100: On Thu, Feb 18 2016, Qu Wenruo wrote: + +/* + * Dedup storage backend + * On disk is persist storage but overhead is large + * In memory is fast but will lose all its hash on umount + */ +#define BTRFS_DEDUP_BACKEND_INMEMORY 0 +#define

Re: btrfs and containers

On Wed, Mar 9, 2016 at 4:45 PM, Marc MERLIN wrote: > On Wed, Mar 09, 2016 at 02:21:26PM -0700, Chris Murphy wrote: >> > I have a very stripped down docker image that actually mounts portion of >> > of my root filesystem read only. >> > While it's running out of a btrfs

[PATCH 2/2] btrfs-progs: Describe device scan -d is a deprecated option in manpage

It's already marked as deprecated in cmd_device_scan_usage(). commit 5444864e5605 ("btrfs-progs: remove BTRFS_SCAN_PROC scan method") Signed-off-by: Satoru Takeuchi --- Documentation/btrfs-device.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[PATCH 1/2] btrfs-progs: Remove unnecessary variable devstart from cmd_device_scan()

It's unnecessary since it's always 1. Signed-off-by: Satoru Takeuchi --- This patch can be applied to devel (commit b2bdd0da8969). --- cmds-device.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/cmds-device.c b/cmds-device.c index

Re: dstat shows unexpected result for two disk RAID1

On 9 March 2016 at 16:36, Roman Mamedov wrote: > On Wed, 9 Mar 2016 15:25:19 -0500 > Nicholas D Steeves wrote: > >> I understood that a btrfs RAID1 would at best grab one block from sdb >> and then one block from sdd in round-robin fashion, or at worse grab

Re: dstat shows unexpected result for two disk RAID1

On 9 March 2016 at 16:43, Chris Murphy wrote: > On Wed, Mar 9, 2016 at 2:36 PM, Roman Mamedov wrote: >> On Wed, 9 Mar 2016 15:25:19 -0500 > This is a better qualification than my answer. > >> >> Now if you want to do some more performance evaluation,

Re: How to move a btrfs volume to a smaller disk

Hello Hugo, thanks for your ultrafast reply. Unfortunately, it does not work for me: [root@homeserver mnt2]# btrfs filesystem resize 80G /mnt2/Data_Store/ && btrfs replace start /dev/sdb4 /dev/sda4 /mnt2/Data_Store/ -f && btrfs filesystem resize max /mnt2/Data_Store/ Resize

Re: How to move a btrfs volume to a smaller disk

On Wed, Mar 09, 2016 at 10:46:09PM +0100, Hendrik Friedel wrote: > Hello, > > I intend to move this subvolume to a new device. > btrfs fi show /mnt2/Data_Store/ > Label: 'Data_Store' uuid: 0ccc1e24-090d-42e2-9e61-d0a1b3101f93 > Total devices 1 FS bytes used 47.93GiB > devid1

How to move a btrfs volume to a smaller disk

Hello, I intend to move this subvolume to a new device. btrfs fi show /mnt2/Data_Store/ Label: 'Data_Store' uuid: 0ccc1e24-090d-42e2-9e61-d0a1b3101f93 Total devices 1 FS bytes used 47.93GiB devid1 size 102.94GiB used 76.03GiB path /dev/sdb4 (fi usage at the bottom of this

Re: btrfs and containers

On Wed, Mar 09, 2016 at 02:21:26PM -0700, Chris Murphy wrote: > > I have a very stripped down docker image that actually mounts portion of > > of my root filesystem read only. > > While it's running out of a btrfs filesystem, you can't run btrfs > > commands against it: > > 05233e5c91f0:/# btrfs

Re: dstat shows unexpected result for two disk RAID1

On Wed, Mar 9, 2016 at 2:36 PM, Roman Mamedov wrote: > On Wed, 9 Mar 2016 15:25:19 -0500 > Nicholas D Steeves wrote: > >> grr. Gmail is terrible :-/ >> >> I understood that a btrfs RAID1 would at best grab one block from sdb >> and then one block from sdd

Re: dstat shows unexpected result for two disk RAID1

On Wed, 9 Mar 2016 15:25:19 -0500 Nicholas D Steeves wrote: > grr. Gmail is terrible :-/ > > I understood that a btrfs RAID1 would at best grab one block from sdb > and then one block from sdd in round-robin fashion, or at worse grab > one chunk from sdb and then one chunk

Re: [PATCH v7 01/20] btrfs: dedup: Introduce dedup framework and its header

On Thu, Feb 18 2016, Qu Wenruo wrote: > + > +/* > + * Dedup storage backend > + * On disk is persist storage but overhead is large > + * In memory is fast but will lose all its hash on umount > + */ > +#define BTRFS_DEDUP_BACKEND_INMEMORY 0 > +#define BTRFS_DEDUP_BACKEND_ONDISK

Re: dstat shows unexpected result for two disk RAID1

On Wed, Mar 9, 2016 at 1:25 PM, Nicholas D Steeves wrote: > grr. Gmail is terrible :-/ > > I understood that a btrfs RAID1 would at best grab one block from sdb > and then one block from sdd in round-robin fashion, or at worse grab > one chunk from sdb and then one chunk from

Re: btrfs and containers

On Wed, Mar 9, 2016 at 2:10 PM, Marc MERLIN wrote: > On Mon, Mar 07, 2016 at 11:55:47PM +0100, Tobias Hunger wrote: >> Hi, >> >> I have been running systemd-nspawn containers on top of a btrfs >> filesystem for a while now. >> >> This works great: Snapshots are a huge help to

Re: btrfs and containers

On Mon, Mar 07, 2016 at 11:55:47PM +0100, Tobias Hunger wrote: > Hi, > > I have been running systemd-nspawn containers on top of a btrfs > filesystem for a while now. > > This works great: Snapshots are a huge help to manage containers! > > But today I ran btrfs subvol list . *inside* a

Re: dstat shows unexpected result for two disk RAID1

On 2016-03-09 21:25, Nicholas D Steeves wrote: > grr. Gmail is terrible :-/ > > I understood that a btrfs RAID1 would at best grab one block from sdb > and then one block from sdd in round-robin fashion, or at worse grab > one chunk from sdb and then one chunk from sdd. Alternatively I >

Re: dstat shows unexpected result for two disk RAID1

grr. Gmail is terrible :-/ I understood that a btrfs RAID1 would at best grab one block from sdb and then one block from sdd in round-robin fashion, or at worse grab one chunk from sdb and then one chunk from sdd. Alternatively I thought that it might read from both simultaneously, to make sure

dstat shows unexpected result for two disk RAID1

Hello everyone, I've run into an expected behaviour for a my two disk RAID1. I mount with UUIDs, because sometimes my USB disk gets /dev/sdc instead of /dev/sdd. The two elements of my RAID1 are currently sdb and sdd. dstat -tdD total,sdb,sdc,sdd It seems that per process, reads come from

Re: incomplete conversion to RAID1?

On 4 March 2016 at 07:55, Duncan <1i5t5.dun...@cox.net> wrote: > Nicholas D Steeves posted on Thu, 03 Mar 2016 16:21:53 -0500 as excerpted: > >>> Of course either way assumes you don't run into some bug that will >>> prevent removal of that chunk, perhaps exactly the same one that kept >>> it from

Re: [PATCH] Documentation: btrfs: remove usage specific information

On Wed, Mar 09, 2016 at 10:26:51AM +0900, Satoru Takeuchi wrote: > > +that maintains information about administration tasks, frequently asked > > +questions, use cases, mount options, comprehensible changelogs, features, > > +manual pages, source code repositories, contacts etc. > > About mount

Re: [PATCH V4 2/2] btrfs-progs: Introduce device delete by devid

On Wed, Mar 09, 2016 at 06:10:26PM +0800, Anand Jain wrote: > From: Anand Jain > > This patch introduces new option for the command > > btrfs device delete [..] > > In a user reported issue on a 3-disk-RAID1, one disk failed with its SB >

Re: [PATCH 13/13] btrfs: optimize check for stale device

On Wed, Mar 09, 2016 at 05:54:47PM +0800, Anand Jain wrote: > > the dereference happens at offset 0x68 which matches bdev in > > btrfs_device, so this patch is my best guess at the moment. I'm not able > > to reproduce it directly so I need to wait for a rebuild and repeat. > > > As of now, >

Re: [PATCH] btrfs-progs: Add new option for specify chunk root bytenr

On Mon, Mar 07, 2016 at 12:57:41PM +0800, Lu Fengqi wrote: > Add new btrfsck option, '--chunk-root', to specify chunk root bytenr.And > allow open_ctree_fs_info() function accept chunk_root_bytenr to override > the bytenr in superblock.This will be mainly used when chunk tree > corruption. Good

Re: [PATCH] Fix broken 'device scan' arguments parsing

On Tue, Mar 08, 2016 at 05:19:40PM -0800, Yauhen Kharuzhy wrote: > commit 52179e4fea41e55f31c92cd033a0b53a5107b4f4 'btrfs-progs: unify argc > min/max checking' brokes 'btrfs device scan' command when no argument > was given. Fix this. > > Signed-off-by: Yauhen Kharuzhy

Re: [PATCH] Fix broken 'device scan' arguments parsing

On Wed, Mar 09, 2016 at 05:24:16PM +0900, Satoru Takeuchi wrote: > > --- a/cmds-device.c > > +++ b/cmds-device.c > > @@ -273,7 +273,7 @@ static int cmd_device_scan(int argc, char **argv) > > if (all && check_argc_max(argc - optind, 1)) > > It's better to the above line as follows. > >

Re: [PATCH] btrfs-progs: util: Fix a wrong unit of pretty_size

On Wed, Mar 09, 2016 at 10:10:55AM +0800, Qu Wenruo wrote: > If parameter for pretty_size is smaller than default base(1024), > pretty_size() will output wrong unit. > For example, pretty_size(1008) will output '0.98B' not '1008B' or > '0.98KiB'. > > The cause is, for default base and auto-detect

Re: [PATCH] btrfs-progs: Replace hardcoded PAGE_CACHE_SIZE with getpagesize().

On Wed, Mar 09, 2016 at 08:22:13PM +0800, Feifei Xu wrote: > PAGE_CACHE_SIZE is hardcoded to 4K in cmds-restore.c. It makes lzo > decompress fail on ppc64. Fix this through replacing hardcoded 4K > with getpagesize(). You're right that the hardcoded value is a bug, but the correct value is the

[PATCH] btrfs-progs: Replace hardcoded PAGE_CACHE_SIZE with getpagesize().

PAGE_CACHE_SIZE is hardcoded to 4K in cmds-restore.c. It makes lzo decompress fail on ppc64. Fix this through replacing hardcoded 4K with getpagesize(). Signed-off-by: Feifei Xu --- cmds-restore.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff

Re: btrfs and containers

On 2016-03-08 16:28, Chris Murphy wrote: On Tue, Mar 8, 2016 at 12:58 PM, Liu Bo wrote: On Mon, Mar 07, 2016 at 04:45:09PM -0700, Chris Murphy wrote: On Mon, Mar 7, 2016 at 3:55 PM, Tobias Hunger wrote: Hi, I have been running systemd-nspawn

[PATCH V4 2/2] btrfs-progs: Introduce device delete by devid

From: Anand Jain This patch introduces new option for the command btrfs device delete [..] In a user reported issue on a 3-disk-RAID1, one disk failed with its SB unreadable. Now with this patch user will have a choice to delete the device using

Re: btrfs-progs and btrfs(8) inconsistencies

Don't hesitate to drop an email here (with your Github account name...) to get invited into the Github group. That's because you can't ask to join a group on GitHub. At the moment, kdave and myself are administrators of the said group (https://github.com/btrfs8-revamp). I'm sure we can nominate

Re: [PATCH 13/13] btrfs: optimize check for stale device

Dave, I see crashes with btrfs/011 on a non-debugging config [ 641.714363] BUG: unable to handle kernel NULL pointer dereference at 0068 [ 641.716057] IP: [] scrub_setup_ctx.isra.19+0x1f6/0x260 [btrfs] :: [ 641.744599] Call Trace: [ 641.745553] []

[PATCH v2 2/2] fstests: btrfs/011 add debug logs to seqres.full

Adds debug logs to $seqres.full and as the btrfs fi show command shows unwanted extra errors from the previous test defunct volumes, avoid this by adding wipefs -a of scratch_pool_device before the each sub test case. Signed-off-by: Anand Jain --- v2: Commit update and,

Re: [PATCH 1/2] fstests: btrfs/011 use replace_options

Sorry for the late reply. More below.. On 02/24/2016 08:42 PM, David Sterba wrote: On Fri, Feb 19, 2016 at 09:25:28PM +0800, Anand Jain wrote: This patch fixes test btrfs/011 which intended to use -r option but was never used since its associated args 'replace_options' didn't make it to the

[PATCH v4 4/6] fstests: btrfs: Add per inode dedup flag test

This test will check per inode dedup flag. Signed-off-by: Qu Wenruo --- tests/btrfs/202 | 108 tests/btrfs/202.out | 15 tests/btrfs/group | 1 + 3 files changed, 124 insertions(+) create mode

[PATCH v4 3/6] fstests: btrfs: Add testcase for btrfs dedup enable disable race test

Add test case to check btrfs dedup enable/disable race. Signed-off-by: Qu Wenruo --- tests/btrfs/201 | 98 + tests/btrfs/201.out | 2 ++ tests/btrfs/group | 1 + 3 files changed, 101 insertions(+) create mode

[PATCH v4 5/6] fstests: btrfs: Test inband dedup with balance.

Btrfs balance will reloate date extent, but its hash is removed too late at run_delayed_ref() time, which will cause extent ref increased increased during balance, cause either find_data_references() gives WARN_ON() or even run_delayed_refs() fails and cause transaction abort. Add such

[PATCH v4 2/6] fstests: btrfs: Add basic test for btrfs in-band de-duplication

Add basic test for btrfs in-band de-duplication, including: 1) Enable 2) Re-enable 3) Dedup 4) File correctness 5) Disable Signed-off-by: Qu Wenruo --- common/defrag | 13 +++ tests/btrfs/200 | 109

[PATCH v4 6/6] fstests: btrfs: Test for btrfs dedup tree balance bug

Btrfs in-band de-duplication has a bug when dedup tree metadata is balanced, it will corrupted btrfs delayed ref and cause the following kernel warning: BTRFS error (device sdb6): unable to find ref byte nr 29736960 parent 0 root 11 owner 0 offset 0 [ cut here ] WARNING:

[PATCH v4 0/6] Btrfs in-band de-duplication test cases

Since we are push btrfs in-band de-duplication for v4.6, it's better to add test cases for this new feature. Except the first basic function test, the rest are all regression test which we found during the development. We also found some bugs from the generic test, but we need some fstests option

[PATCH v4 1/6] fstests: rename _require_btrfs to _require_btrfs_subcommand

Rename _require_btrfs() to _require_btrfs_subcommand() to avoid confusion, as all other _require_btrfs_* has a quite clear suffix, like _require_btrfs_mkfs_feature() or _require_btrfs_fs_feature(). Signed-off-by: Qu Wenruo --- common/rc | 2 +- tests/btrfs/004 | 2

Re: [PATCH] Fix broken 'device scan' arguments parsing

On 2016/03/09 10:19, Yauhen Kharuzhy wrote: > commit 52179e4fea41e55f31c92cd033a0b53a5107b4f4 'btrfs-progs: unify argc > min/max checking' brokes 'btrfs device scan' command when no argument > was given. Fix this. > > Signed-off-by: Yauhen Kharuzhy > --- >