Hi Liu,
>From the patch, is the snapshot disabled by disabling the COW in the mounting
>path?
It seems the create_snapshot() in ioctl.c does not get changed.
I experienced some similar system but am a bit new to the brtfs code.
Thanks,
Xin
Subject: [PATCH 0/6] btrfs dax IOFrom: Liu Bo
At 12/08/2016 01:27 PM, Eryu Guan wrote:
On Thu, Dec 08, 2016 at 10:04:56AM +0800, Qu Wenruo wrote:
Introduce new _require_btrfs_qgroup_report function, which will check
the accessibility to "btrfs check --qgroup-report", then set a global
flag to info _check_scratch_fs() to do extra qgroup ch
At 12/08/2016 12:00 PM, Eryu Guan wrote:
On Thu, Dec 08, 2016 at 10:04:55AM +0800, Qu Wenruo wrote:
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
Simple test script for the following patch.
btrfs-progs: qgroup: add sync option to 'qgroup show'
Signed-off-by: Tsutomu Itoh
---
tests/cli-tests/005-qgroup-show-sync/test.sh | 30
1 file changed, 30 insertions(+)
create mode 100755 tests/cli-tests/005-qgroup-sh
On Thu, Dec 08, 2016 at 10:04:56AM +0800, Qu Wenruo wrote:
> Introduce new _require_btrfs_qgroup_report function, which will check
> the accessibility to "btrfs check --qgroup-report", then set a global
> flag to info _check_scratch_fs() to do extra qgroup check.
>
> Signed-off-by: Qu Wenruo
> --
On Thu, Dec 08, 2016 at 10:04:55AM +0800, Qu Wenruo wrote:
> 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().
>
> Also enhance _require_btrfs_sub
Hi Liu,
[auto build test WARNING on tip/perf/core]
[also build test WARNING on v4.9-rc8 next-20161207]
[cannot apply to btrfs/next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Liu-Bo/btrfs
Hi Liu,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.9-rc8]
[cannot apply to btrfs/next next-20161207]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Liu-Bo/btrfs-dax
I realize this is related very loosely (if at all) to this topic but
what about these two possible features:
- a mount option, or
- an attribute (which could be set on directories and/or sub-volumes
and applied to any new files created below these)
which effectively forces every read/write operatio
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().
Also enhance _require_btrfs_subcommand() to accept 2nd level commands or
options.
Options will be de
Introduce new _require_btrfs_qgroup_report function, which will check
the accessibility to "btrfs check --qgroup-report", then set a global
flag to info _check_scratch_fs() to do extra qgroup check.
Signed-off-by: Qu Wenruo
---
common/rc | 22 ++
tests/btrfs/022 | 5 ++
Hi Liu,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.9-rc8]
[cannot apply to btrfs/next next-20161207]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Liu-Bo/btrfs-dax
Hi Liu,
[auto build test WARNING on tip/perf/core]
[also build test WARNING on v4.9-rc8 next-20161207]
[cannot apply to btrfs/next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Liu-Bo/btrfs
At 12/07/2016 11:06 PM, Goldwyn Rodrigues wrote:
On 12/06/2016 07:29 PM, Qu Wenruo wrote:
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 logic
On Wed, Dec 07, 2016 at 05:15:42PM -0500, Chris Mason wrote:
>
>
> On 12/07/2016 04:45 PM, Liu Bo wrote:
> > This has implemented DAX support for btrfs with nocow and single-device.
> >
> > DAX is developed for block devices that are memory-like in order to avoid
> > double buffer in both page c
# taskset -c 0 btrfs send /mnt/first/subvol.ro/ | btrfs receive /mnt/int/
Attaching top and perf top while this send receive happens. The use of
taskset -c 0 doesn't seem to affect the results.
Chris Murphy
Samples: 51K of event 'cycles:pp', Event count (approx.): 13435020269
Overhead Shared Ob
On 12/07/2016 04:45 PM, Liu Bo wrote:
This has implemented DAX support for btrfs with nocow and single-device.
DAX is developed for block devices that are memory-like in order to avoid
double buffer in both page cache and the storage, so DAX can performs reads and
writes directly to the storag
Hi,
On Wed, Dec 07, 2016 at 11:11:41AM -0500, Yclept Nemo wrote:
> kernel version: drm-next x86_64
> abrt (fedora) bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1402453
I believe the patch [1] can address this warning.
[1]: https://patchwork.kernel.org/patch/9457035/
Thanks,
-liubo
These TPs can help us monitor iomap content for dax reads and writes.
Signed-off-by: Liu Bo
---
fs/btrfs/inode.c | 9
include/trace/events/btrfs.h | 106 +++
2 files changed, 115 insertions(+)
diff --git a/fs/btrfs/inode.c b/fs/btrfs/in
Dax on btrfs is not ready for multiple device.
Signed-off-by: Liu Bo
---
fs/btrfs/ioctl.c | 6 ++
fs/btrfs/super.c | 7 +++
2 files changed, 13 insertions(+)
diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index 7acbd2c..ab30d88 100644
--- a/fs/btrfs/ioctl.c
+++ b/fs/btrfs/ioctl.c
@@ -
This adds a helper function btrfs_file_write_check for file checks, permission
check and necessary time and size extention.
With this, we simplify btrfs_file_write_iter by putting details into seperated
buffered_write and direct_write callback.
Signed-off-by: Liu Bo
---
fs/btrfs/file.c | 128 ++
Signed-off-by: Liu Bo
---
fs/btrfs/ctree.h | 1 +
fs/btrfs/super.c | 40 +++-
2 files changed, 40 insertions(+), 1 deletion(-)
diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index 0b8ce2b..e54c6e6 100644
--- a/fs/btrfs/ctree.h
+++ b/fs/btrfs/ctree.h
@@ -131
This has implemented DAX support for btrfs with nocow and single-device.
DAX is developed for block devices that are memory-like in order to avoid
double buffer in both page cache and the storage, so DAX can performs reads and
writes directly to the storage device, and for those who prefer to usin
This is a prelimanary patch set to add dax support for btrfs, with
this we can do normal read/write to dax files and can mmap dax files
to userspace so that applications have the ability to access
persistent memory directly.
Please note that currently this is limited to nocow, i.e. all dax
inodes
How to serialise page_faults against truncate/hole punch?
For truncate, we firstly update isize and then truncate pagecache in
order to avoid race against page fault.
For punch_hole, we use lock_extent and truncate pagecache.
Although we have these rules to avoid the race, it's not easy to unders
Good Day to you,
I am Mr.JAMES KABORE, Chief Operating Officer with my Bank, This
letter must come to you as a big surprise, but only a day people meet
and become friends and business partners.
An Iraqi Foreign Oil consultant/contractor Mr.Thomas Stone made a
fixed deposit with our bank in 2003,
On Sat, Dec 03, 2016 at 11:48:33AM -0500, Dave Jones wrote:
> The interesting process here seems to be kworker/u8:17, and the trace
> captures some of what that was doing before that bad page was hit.
I'm travelling next week, so I'm trying to braindump the stuff I've
found so far and summarise
kernel version: drm-next x86_64
abrt (fedora) bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1402453
dmesg snippet (the full dmesg is 15Mb):
kernel: =
kernel: [ INFO: possible recursive locking detected ]
kernel: 4.9.0-0.rc8.git0.1.fc25.x86_64 #
On 12/06/2016 07:29 PM, Qu Wenruo wrote:
> 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 c
On Thu, 2016-12-01 at 09:11 -0500, Jeff Layton wrote:
> 1) Proposals for agenda topics should be sent before January 15th,
> 2016 to:
>
> lsf...@lists.linux-foundation.org
>
> and cc the Linux list or lists that are relevant for the topic in
> question:
>
> ATA: linux-...@vger.kernel.
Luescher Claude posted on Tue, 06 Dec 2016 14:00:28 +0100 as excerpted:
> The server was running 3.13 kernel and btrfs progs 4.0 until it
> crashed. After that mounting the file system hang forever so I decided
> to switch to Linux Kernel 4.8.11 and btrfs-progs v4.8.5.
>
> There are of course no
31 matches
Mail list logo
