linux-toradex.git/include/uapi/linux/btrfs.h, branch v4.6-rc3

btrfs: extend balance filter usage to take minimum and maximum

2015-10-27T02:38:30+00:00

Similar to the 'limit' filter, we can enhance the 'usage' filter to
accept a range. The change is backward compatible, the range is applied
only in connection with the BTRFS_BALANCE_ARGS_USAGE_RANGE flag.

We don't have a usecase yet, the current syntax has been sufficient. The
enhancement should provide parity with other range-like filters.

Signed-off-by: David Sterba 
Signed-off-by: Chris Mason

btrfs: add balance filter for stripes

2015-10-27T02:38:29+00:00

Balance block groups which have the given number of stripes, defined by
a range min..max. This is useful to selectively rebalance only chunks
that do not span enough devices, applies to RAID0/10/5/6.

Signed-off-by: Gabríel Arthúr Pétursson 
[ renamed bargs members, added to the UAPI, wrote the changelog ]
Signed-off-by: David Sterba 

Signed-off-by: Chris Mason

btrfs: extend balance filter limit to take minimum and maximum

2015-10-27T02:38:28+00:00

The 'limit' filter is underdesigned, it should have been a range for
[min,max], with some relaxed semantics when one of the bounds is
missing. Besides that, using a full u64 for a single value is a waste of
bytes.

Let's fix both by extending the use of the u64 bytes for the [min,max]
range. This can be done in a backward compatible way, the range will be
interpreted only if the appropriate flag is set
(BTRFS_BALANCE_ARGS_LIMIT_RANGE).

Signed-off-by: David Sterba 
Signed-off-by: Chris Mason

Btrfs: Remove unnecessary placeholder in btrfs_err_code

2015-02-03T03:25:51+00:00

"notused" is not necessary. Set 1 to the first entry is enough.

Signed-off-by: Takeuchi Satoru 
Reviewed-by: David Sterba 
Signed-off-by: Chris Mason

Btrfs: return failure if btrfs_dev_replace_finishing() failed

2014-11-21T01:14:28+00:00

device replace could fail due to another running scrub process or any
other errors btrfs_scrub_dev() may hit, but this failure doesn't get
returned to userspace.

The following steps could reproduce this issue

	mkfs -t btrfs -f /dev/sdb1 /dev/sdb2
	mount /dev/sdb1 /mnt/btrfs
	while true; do btrfs scrub start -B /mnt/btrfs >/dev/null 2>&1; done &
	btrfs replace start -Bf /dev/sdb2 /dev/sdb3 /mnt/btrfs
	# if this replace succeeded, do the following and repeat until
	# you see this log in dmesg
	# BTRFS: btrfs_scrub_dev(/dev/sdb2, 2, /dev/sdb3) failed -115
	#btrfs replace start -Bf /dev/sdb3 /dev/sdb2 /mnt/btrfs

	# once you see the error log in dmesg, check return value of
	# replace
	echo $?

Introduce a new dev replace result

BTRFS_IOCTL_DEV_REPLACE_RESULT_SCRUB_INPROGRESS

to catch -EINPROGRESS explicitly and return other errors directly to
userspace.

Signed-off-by: Eryu Guan 
Signed-off-by: Chris Mason

btrfs: create sprout should rename fsid on the sysfs as well

2014-06-28T20:48:44+00:00

Creating sprout will change the fsid of the mounted root.
do the same on the sysfs as well.

reproducer:
 mount /dev/sdb /btrfs (seed disk)
 btrfs dev add /dev/sdc /btrfs
 mount -o rw,remount /btrfs
 btrfs dev del /dev/sdb /btrfs
 mount /dev/sdb /btrfs

Error:
kobject_add_internal failed for fe350492-dc28-4051-a601-e017b17e6145 with -EEXIST, don't try to register things with the same name in the same directory.

Signed-off-by: Anand Jain 
Reviewed-by: David Sterba 
Signed-off-by: Chris Mason

btrfs: new ioctl TREE_SEARCH_V2

2014-06-13T16:52:19+00:00

This new ioctl call allows the user to supply a buffer of varying size in which
a tree search can store its results. This is much more flexible if you want to
receive items which are larger than the current fixed buffer of 3992 bytes or
if you want to fetch more items at once. Items larger than this buffer are for
example some of the type EXTENT_CSUM.

Signed-off-by: Gerhard Heift 
Signed-off-by: Chris Mason 
Acked-by: David Sterba

btrfs: retrieve more info from FS_INFO ioctl

2014-06-10T00:20:27+00:00

Provide the basic information about filesystem through the ioctl:
* b-tree node size (same as leaf size)
* sector size
* expected alignment of CLONE_RANGE and EXTENT_SAME ioctl arguments

Backward compatibility: if the values are 0, kernel does not provide
this information, the applications should ignore them.

Signed-off-by: David Sterba 
Signed-off-by: Chris Mason

btrfs: balance filter: add limit of processed chunks

2014-06-10T00:20:26+00:00

This started as debugging helper, to watch the effects of converting
between raid levels on multiple devices, but could be useful standalone.

In my case the usage filter was not finegrained enough and led to
converting too many chunks at once. Another example use is in connection
with drange+devid or vrange filters that allow to work with a specific
chunk or even with a chunk on a given device.

The limit filter applies last, the value of 0 means no limiting.

CC: Ilya Dryomov 
CC: Hugo Mills 
Signed-off-by: David Sterba 
Signed-off-by: Chris Mason

Revert "btrfs: add ioctl to export size of global metadata reservation"

2014-02-14T21:42:13+00:00

This reverts commit 01e219e8069516cdb98594d417b8bb8d906ed30d.

David Sterba found a different way to provide these features without adding a new
ioctl.  We haven't released any progs with this ioctl yet, so I'm taking this out
for now until we finalize things.

Signed-off-by: Chris Mason 
Signed-off-by: David Sterba 
CC: Jeff Mahoney