[PATCH v2] btrfs-progs: qgroup: add sync option to 'qgroup show'

The 'qgroup show' command does not synchronize filesystem. Therefore, 'qgroup show' may not display the correct value unless synchronized with 'filesystem sync' command etc. So add the '--sync' and '--no-sync' options so that we can choose whether or not to synchronize when executing the command.

Re: [PATCH] btrfs-progs: qgroup: add sync option to 'qgroup show'

On 2016/12/07 13:59, Qu Wenruo wrote: > > > At 12/07/2016 12:31 PM, Tsutomu Itoh wrote: >> Hi Qu, >> >> Thanks for the review. >> >> On 2016/12/07 12:24, Qu Wenruo wrote: >>> >>> >>> At 12/07/2016 11:07 AM, Tsutomu Itoh wrote: The 'qgroup show' command does not synchronize filesystem.

Couldn't delete a directory after power failure

Hello, I had this problem today after power failure of the pc. Bitcoin wallet couldn't use his database, it said that the database is corrupted, so I decided to delete blockchain database from the wallet. But I couldn't delete directory "chainstate". The problem is solved at the moment I

Re: [PATCH] btrfs-progs: qgroup: add sync option to 'qgroup show'

At 12/07/2016 12:31 PM, Tsutomu Itoh wrote: Hi Qu, Thanks for the review. On 2016/12/07 12:24, Qu Wenruo wrote: At 12/07/2016 11:07 AM, Tsutomu Itoh wrote: The 'qgroup show' command does not synchronize filesystem. Therefore, 'qgroup show' may not display the correct value unless

Re: [PATCH] btrfs-progs: qgroup: add sync option to 'qgroup show'

Hi Qu, Thanks for the review. On 2016/12/07 12:24, Qu Wenruo wrote: > > > At 12/07/2016 11:07 AM, Tsutomu Itoh wrote: >> The 'qgroup show' command does not synchronize filesystem. >> Therefore, 'qgroup show' may not display the correct value unless >> synchronized with 'filesystem sync'

Re: [PATCH] btrfs-progs: qgroup: add sync option to 'qgroup show'

At 12/07/2016 11:07 AM, Tsutomu Itoh wrote: The 'qgroup show' command does not synchronize filesystem. Therefore, 'qgroup show' may not display the correct value unless synchronized with 'filesystem sync' command etc. So add the '--sync' and '--no-sync' options so that we can choose whether

[PATCH] btrfs-progs: qgroup: add sync option to 'qgroup show'

The 'qgroup show' command does not synchronize filesystem. Therefore, 'qgroup show' may not display the correct value unless synchronized with 'filesystem sync' command etc. So add the '--sync' and '--no-sync' options so that we can choose whether or not to synchronize when executing the command.

[PATCH] btrfs-progs: Fix disable backtrace assert error

Due to commit 00e769d04c2c83029d6c71(btrfs-progs: Correct value printed by assertions/BUG_ON/WARN_ON), which changed the assert_trace() parameter, the condition passed to assert/WARN_ON/BUG_ON are logical notted for backtrace enabled and disabled case. Such behavior makes us easier to pass value

Re: [PATCH 1/2] btrfs-progs: Correct value printed by assertions/BUG_ON/WARN_ON

At 12/06/2016 08:44 PM, Goldwyn Rodrigues wrote: On 12/05/2016 09:08 PM, Qu Wenruo wrote: At 12/06/2016 10:51 AM, Goldwyn Rodrigues wrote: On 12/05/2016 08:03 PM, Qu Wenruo wrote: BTW, the DISABLE_BACKTRACE branch seems quite different from backtrace one. #define BUG_ON(c)

Re: bio linked list corruption.

On Tue, Dec 6, 2016 at 12:16 AM, Peter Zijlstra wrote: >> >> Of course, I'm really hoping that this shmem.c use is the _only_ such >> case. But I doubt it. > > $ git grep DECLARE_WAIT_QUEUE_HEAD_ONSTACK | wc -l > 28 Hmm. Most of them seem to be ok, because they use

Re: crc32c_le performance hit

On 12/05/2016 08:34 PM, Chris Murphy wrote: On Mon, Dec 5, 2016 at 8:46 AM, Chris Mason wrote: On 12/04/2016 04:28 PM, Chris Murphy wrote: 4.8.11-300.fc25.x86_64 I'm currently doing a btrfs send/receive and I'm seeing a rather large hit for crc32c, bigger than aes-ni (the

Re: [SOLVED] Re: system hangs due to qgroups

On Tuesday 06 December 2016 11:12:12 Marc Joliet wrote: > I have disabled quotas already (first thing I did after > mounting). However, there were definitely 20-30, maybe more (enough for > 2, maybe 3, console pages -- I don't know how many lines the initramfs > rescue shell has, but based on

Re: [PATCH 10/18] btrfs: root->fs_info cleanup, btrfs_calc_{trans,trunc}_metadata_size

On Mon, Dec 05, 2016 at 10:50:34AM -0500, Jeff Mahoney wrote: > On 12/5/16 10:29 AM, David Sterba wrote: > > On Fri, Dec 02, 2016 at 12:07:30AM -0500, je...@suse.com wrote: > >> -static inline u64 btrfs_calc_trans_metadata_size(struct btrfs_root *root, > >> +static inline u64

[PATCH v2] btrfs: opencode chunk locking, remove helpers

The helpers are trivial and we don't use them consistently. Signed-off-by: David Sterba --- Refreshed on top of Jeff's cleanup regarding passing fs_info and root to various functions. fs/btrfs/disk-io.c | 4 +-- fs/btrfs/extent-tree.c | 8 +++---

Re: Convert from RAID 5 to 10

Thanks a lot to all who replied! I learned a lot from this thread. However, what I learned has made me even more doubtful that a btrfs RAID is the right choice for me at this moment. There seems to be much uncertainty about the real state (experimental, stable, production-ready, mature, ...) of

Re: Free space missing

On 6 December 2016 at 12:40, Кравцов Роман Владимирович wrote: > Hello. > > Why 'BTRFS used size' and 'du -s' are different? > > > [root@OraCI2 ~]# btrfs --version > btrfs-progs v4.8.3 > [root@OraCI2 ~]# btrfs fi show /dev/nvme0n1 > Label: 'OLD_PES' uuid:

*** Some devices missing ***

Hi, I have the following array: Label: 'backup_fs' uuid: x Total devices 10 FS bytes used 13.46TiB devid1 size 3.64TiB used 3.32TiB path /dev/sdf devid2 size 3.64TiB used 3.32TiB path /dev/sde devid3 size 3.64TiB used 3.32TiB path /dev/sdd

Free space missing

Hello. Why 'BTRFS used size' and 'du -s' are different? [root@OraCI2 ~]# btrfs --version btrfs-progs v4.8.3 [root@OraCI2 ~]# btrfs fi show /dev/nvme0n1 Label: 'OLD_PES' uuid: bd542f37-6baa-4af8-b87a-20d4e335e4b3 Total devices 1 FS bytes used 2.53TiB devid1 size 2.91TiB used

Re: [PATCH 1/2] btrfs-progs: Correct value printed by assertions/BUG_ON/WARN_ON

On 12/05/2016 09:08 PM, Qu Wenruo wrote: > > > At 12/06/2016 10:51 AM, Goldwyn Rodrigues wrote: >> >> >> On 12/05/2016 08:03 PM, Qu Wenruo wrote: >>> BTW, the DISABLE_BACKTRACE branch seems quite different from >>> backtrace one. >>> >>> #define BUG_ON(c) assert_trace(#c, __FILE__, __func__,

Re: [SOLVED] Re: system hangs due to qgroups

On Tuesday 06 December 2016 08:29:48 Qu Wenruo wrote: > At 12/05/2016 10:43 PM, Marc Joliet wrote: > > On Monday 05 December 2016 12:01:28 Marc Joliet wrote: > >>> This seems to be a NULL pointer bug in qgroup relocation fix. > >>> > >>> > >>> > >>> The latest fix (not merged yet) should

Re: bio linked list corruption.

On 5 December 2016 at 22:33, Vegard Nossum wrote: > On 5 December 2016 at 21:35, Linus Torvalds > wrote: >> Note for Ingo and Peter: this patch has not been tested at all. But >> Vegard did test an earlier patch of mine that just verified

Re: bio linked list corruption.

* Peter Zijlstra wrote: > $ git grep DECLARE_WAIT_QUEUE_HEAD_ONSTACK | wc -l > 28 This debug facility looks sensible. A couple of minor suggestions: > --- a/include/linux/wait.h > +++ b/include/linux/wait.h > @@ -39,6 +39,9 @@ struct wait_bit_queue { > struct

Re: [PATCH] generic/35[67]: disable swapfile tests on Btrfs

On Mon, Dec 05, 2016 at 05:01:28PM -0800, Omar Sandoval wrote: > From: Omar Sandoval > > Btrfs doesn't support swapfiles (yet?), so generic/356 fails > erroneously, and generic/357 only passes by accident. Let's add a > _require_scratch_swapfile helper and add it to these tests.

Re: bio linked list corruption.

On Mon, Dec 05, 2016 at 12:35:52PM -0800, Linus Torvalds wrote: > Adding the scheduler people to the participants list, and re-attaching > the patch, because while this patch is internal to the VM code, the > issue itself is not. > > There might well be other cases where somebody goes