Re: Problems with btrfs

On 2018年04月29日 09:55, David C. Partridge wrote: > Not a problem > > See attached The final binary dump: # dd if= of=/tmp/copy1.img bs=1 count=16K skip=25942081536 # dd if= of=/tmp/copy2.img bs=1 count=16K skip=26478952448 Thanks, Qu > > > -Original Message- > From: Qu Wenruo

Re: fs/btrfs/ctree.h:1559 warnings

On 2018年04月29日 04:16, Paul Richards wrote: > On 28 April 2018 at 20:39, Patrik Lundquist > wrote: >> On 28 April 2018 at 20:54, Paul Richards wrote: >>> >>> Hi, >>> I recently upgraded from Linux 4.4.0 to 4.13.0 (Ubuntu 16.04 stock to >>>

Re: Problems with btrfs

On 2018年04月29日 00:02, David C. Partridge wrote: > Here are the dumps you requested. Sorry, I took wrong dump. The correct dump would be: # btrfs inspect dump-tree -t extent And you still need to do an extra dump for the final offending tree block. Considering the extra steps and delays,

Re: [PATCH] btrfs: trace: Remove unnecessary fs_info parameter for btrfs__reserve_extent event class

On 2018年04月29日 01:45, David Sterba wrote: > On Sat, Apr 28, 2018 at 06:42:06PM +0200, David Sterba wrote: >> On Thu, Apr 26, 2018 at 02:24:25PM +0800, Qu Wenruo wrote: >>> fs_info can be extracted from btrfs_block_group_cache, and all >>> btrfs_block_group_cache is created by

Re: fs/btrfs/ctree.h:1559 warnings

On 28 April 2018 at 20:39, Patrik Lundquist wrote: > On 28 April 2018 at 20:54, Paul Richards wrote: >> >> Hi, >> I recently upgraded from Linux 4.4.0 to 4.13.0 (Ubuntu 16.04 stock to >> hwe kernel). >> >> Since then, I've noticed lots of

fs/btrfs/ctree.h:1559 warnings

Hi, I recently upgraded from Linux 4.4.0 to 4.13.0 (Ubuntu 16.04 stock to hwe kernel). Since then, I've noticed lots of btrfs warnings in dmesg (example at the end). I believe these warnings to be benign, and they relate to my partition not being a multiple of 4KiB in size (I confirmed that

Re: [PATCH v2] btrfs: Unexport and rename btrfs_invalidate_inodes

/0day-ci/linux/commits/Nikolay-Borisov/btrfs-Unexport-and-rename-btrfs_invalidate_inodes/20180428-234332 reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones prefixed by >>) fs/btrfs/disk-io.c:4

Re: [PATCH] btrfs: trace: Remove unnecessary fs_info parameter for btrfs__reserve_extent event class

On Sat, Apr 28, 2018 at 06:42:06PM +0200, David Sterba wrote: > On Thu, Apr 26, 2018 at 02:24:25PM +0800, Qu Wenruo wrote: > > fs_info can be extracted from btrfs_block_group_cache, and all > > btrfs_block_group_cache is created by btrfs_create_block_group_cache() > > with fs_info initialized, no

Re: [PATCH] btrfs: Take trans lock before access running trans in check_delayed_ref

/commits/ethanwu/btrfs-Take-trans-lock-before-access-running-trans-in-check_delayed_ref/20180428-223414 reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones prefixed by >>) fs/btrfs/extent-tree.c:

Re: [PATCH 1/3] btrfs: qgroups, fix rescan worker running races

On Fri, Apr 27, 2018 at 03:28:44PM -0400, Noah Massey wrote: > On Fri, Apr 27, 2018 at 11:56 AM, David Sterba wrote: > > On Thu, Apr 26, 2018 at 03:23:49PM -0400, je...@suse.com wrote: > >> From: Jeff Mahoney > >> > >> Commit d2c609b834d6 (Btrfs: fix qgroup

Re: [PATCH 1/3] btrfs: qgroups, fix rescan worker running races

On Fri, Apr 27, 2018 at 03:32:14PM -0400, Jeff Mahoney wrote: > On 4/27/18 12:40 PM, David Sterba wrote: > > On Fri, Apr 27, 2018 at 12:02:13PM -0400, Jeff Mahoney wrote: > +static void queue_rescan_worker(struct btrfs_fs_info *fs_info) > +{ > >>> > >>> And this had to be moved upwards

Re: [PATCH v2] btrfs: Unexport and rename btrfs_invalidate_inodes

/linux/commits/Nikolay-Borisov/btrfs-Unexport-and-rename-btrfs_invalidate_inodes/20180428-234332 config: i386-randconfig-a0-201816 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new

Re: [PATCH] btrfs: trace: Remove unnecessary fs_info parameter for btrfs__reserve_extent event class

On Thu, Apr 26, 2018 at 02:24:25PM +0800, Qu Wenruo wrote: > fs_info can be extracted from btrfs_block_group_cache, and all > btrfs_block_group_cache is created by btrfs_create_block_group_cache() > with fs_info initialized, no need to worry about NULL pointer > dereference. Famous last words. [

Re: [PATCH v2] btrfs: Unexport and rename btrfs_invalidate_inodes

/linux/commits/Nikolay-Borisov/btrfs-Unexport-and-rename-btrfs_invalidate_inodes/20180428-234332 config: x86_64-randconfig-x013-201816 (attached as .config) compiler: gcc-7 (Debian 7.3.0-16) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors

RE: Problems with btrfs

Here are the dumps you requested. -Original Message- From: Qu Wenruo [mailto:quwenruo.bt...@gmx.com] Sent: 28 April 2018 15:23 To: David C. Partridge; linux-btrfs@vger.kernel.org Subject: Re: Problems with btrfs On 2018年04月28日 22:06, David C. Partridge wrote: > Here's the log you

Re: [PATCH] btrfs: Take trans lock before access running trans in check_delayed_ref

/commits/ethanwu/btrfs-Take-trans-lock-before-access-running-trans-in-check_delayed_ref/20180428-223414 config: i386-randconfig-a0-201816 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: # save the attached .config to linux build tree make ARCH=i386 All warnings

Re: [PATCH] btrfs: Take trans lock before access running trans in check_delayed_ref

/ethanwu/btrfs-Take-trans-lock-before-access-running-trans-in-check_delayed_ref/20180428-223414 config: i386-randconfig-x014-201816 (attached as .config) compiler: gcc-7 (Debian 7.3.0-16) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new

Re: Problems with btrfs

On 2018年04月28日 22:06, David C. Partridge wrote: > Here's the log you asked for ... > > David To dump the offending tree block, you could use the following command: # dd if=/dev/mapper/Charon--vg-root of=copy1.dump bs=1 count=16k skip=22919544832 # dd if=/dev/mapper/Charon--vg-root

RE: Problems with btrfs

Here's the log you asked for ... David -Original Message- From: Qu Wenruo [mailto:quwenruo.bt...@gmx.com] Sent: 28 April 2018 14:54 To: David C. Partridge Subject: Re: Problems with btrfs On 2018年04月28日 21:38, David C. Partridge wrote: > Oh! doing a private build from source a bit

What is recommended level of btrfs-progs and kernel please

To what level of btrfs-progs do you recommend I should upgrade once my corrupt FS is fixed? What is the kernel pre-req for that? Would prefer not to build from source ... currently running Ubuntu 16.04LTS Thanks David -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in

Re: BTRFS RAID filesystem unmountable

On 2018年04月28日 17:37, Michael Wade wrote: > Hi Qu, > > Thanks for your reply. I will investigate upgrading the kernel, > however I worry that future ReadyNAS firmware upgrades would fail on a > newer kernel version (I don't have much linux experience so maybe my > concerns are unfounded!?). >

Re: [PATCH 4/4] [RESEND] Btrfs: reduce size of struct btrfs_inode

чт, 26 апр. 2018 г. в 16:44, David Sterba : > On Wed, Apr 25, 2018 at 02:37:17AM +0300, Timofey Titovets wrote: > > Currently btrfs_inode have size equal 1136 bytes. (On x86_64). > > > > struct btrfs_inode store several vars releated to compression code, > > all states use 1 or 2

Re: BTRFS RAID filesystem unmountable

Hi Qu, Thanks for your reply. I will investigate upgrading the kernel, however I worry that future ReadyNAS firmware upgrades would fail on a newer kernel version (I don't have much linux experience so maybe my concerns are unfounded!?). I have attached the output of the dump super command. I

Re: [PATCH 1/4] [RESEND] Btrfs: btrfs_dedupe_file_range() ioctl, remove 16MiB restriction

чт, 26 апр. 2018 г. в 17:05, David Sterba : > On Wed, Apr 25, 2018 at 02:37:14AM +0300, Timofey Titovets wrote: > > At now btrfs_dedupe_file_range() restricted to 16MiB range for > > limit locking time and memory requirement for dedup ioctl() > > > > For too big input range code

Re: BTRFS RAID filesystem unmountable

On 2018年04月28日 16:30, Michael Wade wrote: > Hi all, > > I was hoping that someone would be able to help me resolve the issues > I am having with my ReadyNAS BTRFS volume. Basically my trouble > started after a power cut, subsequently the volume would not mount. > Here are the details of my

BTRFS RAID filesystem unmountable

Hi all, I was hoping that someone would be able to help me resolve the issues I am having with my ReadyNAS BTRFS volume. Basically my trouble started after a power cut, subsequently the volume would not mount. Here are the details of my setup as it is at the moment: uname -a Linux QAI

Re: NVMe SSD + compression - benchmarking

On 04/28/2018 04:05 AM, Qu Wenruo wrote: On 2018年04月28日 01:41, Brendan Hide wrote: Hey, all I'm following up on the queries I had last week since I have installed the NVMe SSD into the PCI-e adapter. I'm having difficulty knowing whether or not I'm doing these benchmarks correctly. As a