Re: Writing a large file causes odd freeze

2018-10-02 Thread Qu Wenruo
On 2018/10/2 下午9:31, Gerard Saraber wrote: > I have a 25TB mirrored filesystem that I'm able to consistently freeze > by ungzipping a large file. > The filesystem scrubs complete without errors and smartd reports no > errors at the moment. > > The command is: > gzip -dc /btrfsarray/largefile.gz

Re: [PATCH 03/10] btrfs-progs: Replace homegrown bitops related functions with kernel counterparts

2018-10-02 Thread Omar Sandoval
On Mon, Oct 01, 2018 at 05:46:14PM +0300, Nikolay Borisov wrote: > Replace existing find_*_bit functions with kernel equivalent. This > reduces duplication, simplifies the code (we really have one worker > function _find_next_bit) and is quite likely faster. No functional > changes. Reviewed-by:

Re: Writing a large file causes odd freeze

2018-10-02 Thread Gerard Saraber
That was going to be my next move, downgrade kernels, but I wasn't sure how far back to go.. I'll give 4.18.6 a shot and see how it does the next time I need to reboot it :) -G On Tue, Oct 2, 2018 at 1:23 PM Eli V wrote: > > I've seen similar symptoms running >

Re: btrfs send receive ERROR: chown failed: No such file or directory

2018-10-02 Thread Filipe Manana
On Tue, Oct 2, 2018 at 7:02 AM Leonard Lausen wrote: > > Hello, > > does anyone have an idea about below issue? It is a severe issue as it > renders btrfs send / receive dysfunctional and it is not clear if there > may be a data corruption issue hiding in the current send / receive > code. > >

Re: [PATCH 02/10] btrfs-progs: Add extent buffer bitmap manipulation infrastructure

2018-10-02 Thread Omar Sandoval
On Mon, Oct 01, 2018 at 05:46:13PM +0300, Nikolay Borisov wrote: > Those functions are in preparation for adding the freespace tree > repair code since it needs to be able to deal with bitmap based fsts. > This patch adds extent_buffer_bitmap_set and extent_buffer_bitmap_clear > functions. Since

Re: [PATCH 01/10] btrfs-progs: Add support for freespace tree in btrfs_read_fs_root

2018-10-02 Thread Omar Sandoval
On Mon, Oct 01, 2018 at 05:46:12PM +0300, Nikolay Borisov wrote: > For completeness sake add code to btrfs_read_fs_root so that it can > handle the freespace tree. Reviewed-by: Omar Sandoval > Signed-off-by: Nikolay Borisov > --- > disk-io.c | 3 +++ > 1 file changed, 3 insertions(+) > >

Re: cross-fs copy support

2018-10-02 Thread J. Bruce Fields
On Mon, Oct 01, 2018 at 01:51:09PM -0600, Andreas Dilger wrote: > On Oct 1, 2018, at 9:49 AM, Eric Sandeen wrote: > > Yes, I would expect there to be problems with his modified kernel > > for a filesystem that supports clone_file_range, because > > vfs_copy_file_range() will clone if

Re: Writing a large file causes odd freeze

2018-10-02 Thread Eli V
I've seen similar symptoms running rsync(https://bugzilla.kernel.org/show_bug.cgi?id=199753), and the hangs always seem to have the wait_woken() in the stack trace. Doesn't happen repeatably for me, though I ran 4.18.6 for a month without issues, and had freezes the first(and only) two times I ran

Re: Writing a large file causes odd freeze

2018-10-02 Thread Gerard Saraber
Correction, I am using that option: mount UUID="${FS}" -o space_cache=v2,noatime,degraded /btrfsarray On Tue, Oct 2, 2018 at 10:50 AM Gerard Saraber wrote: > > I'll give that a shot! thank you! > > -Gerard > On Tue, Oct 2, 2018 at 10:24 AM wrote: > > > > > I have a 25TB mirrored filesystem that

Re: Writing a large file causes odd freeze

2018-10-02 Thread Gerard Saraber
I'll give that a shot! thank you! -Gerard On Tue, Oct 2, 2018 at 10:24 AM wrote: > > > I have a 25TB mirrored filesystem that I'm able to consistently freeze > > by ungzipping a large file. > > The filesystem scrubs complete without errors and smartd reports no > > errors at the moment. > > > >

Re: Writing a large file causes odd freeze

2018-10-02 Thread joshua
> I have a 25TB mirrored filesystem that I'm able to consistently freeze > by ungzipping a large file. > The filesystem scrubs complete without errors and smartd reports no > errors at the moment. > > The command is: > gzip -dc /btrfsarray/largefile.gz > /btrfs/db/output.sql > At around 31GB it

Re: cross-fs copy support

2018-10-02 Thread Darrick J. Wong
On Tue, Oct 02, 2018 at 10:15:44AM +0200, David Sterba wrote: > On Mon, Oct 01, 2018 at 01:51:09PM -0600, Andreas Dilger wrote: > > > Yes, I would expect there to be problems with his modified kernel > > > for a filesystem that supports clone_file_range, because > > > vfs_copy_file_range() will

Re: [PATCH 16/42] btrfs: loop in inode_rsv_refill

2018-10-02 Thread David Sterba
On Fri, Sep 28, 2018 at 07:17:55AM -0400, Josef Bacik wrote: > With severe fragmentation we can end up with our inode rsv size being > huge during writeout, which would cause us to need to make very large > metadata reservations. However we may not actually need that much once > writeout is

Writing a large file causes odd freeze

2018-10-02 Thread Gerard Saraber
I have a 25TB mirrored filesystem that I'm able to consistently freeze by ungzipping a large file. The filesystem scrubs complete without errors and smartd reports no errors at the moment. The command is: gzip -dc /btrfsarray/largefile.gz > /btrfs/db/output.sql At around 31GB it quits writing to

Re: [PATCH] btrfs: tree-checker: Check level for leaves and nodes

2018-10-02 Thread David Sterba
On Fri, Sep 28, 2018 at 07:59:34AM +0800, Qu Wenruo wrote: > Although we have tree level check at tree read runtime, it's completely > based on its parent level. > We still need to do accurate level check to avoid invalid tree blocks > sneak into kernel space. > > The check itself is simple, for

Re: cross-fs copy support

2018-10-02 Thread David Sterba
On Mon, Oct 01, 2018 at 01:51:09PM -0600, Andreas Dilger wrote: > > Yes, I would expect there to be problems with his modified kernel > > for a filesystem that supports clone_file_range, because > > vfs_copy_file_range() will clone if possible, and this should fail across > > filesystems. > > > >

Re: btrfs send receive ERROR: chown failed: No such file or directory

2018-10-02 Thread Leonard Lausen
Hello, does anyone have an idea about below issue? It is a severe issue as it renders btrfs send / receive dysfunctional and it is not clear if there may be a data corruption issue hiding in the current send / receive code. Thank you. Best regards Leonard Leonard Lausen writes: > Hello! > > I