[PATCH 2/2] btrfs-progs: fi: enable fi usage for filesystem top of seed device

Currently "fi usage" (and "dev usage") cannot run for the filesystem using seed device. This is because FS_INFO ioctl returns the number of devices excluding seeds, but load_device_info() tries to access valid device from devid 0 to max_id, and results in accessing seeds too (thus causing

[PATCH 1/2] btrfs-progs: fi: move dev_to_fsid() to cmds-fi-usage for later use

Move dev_to_fsid() from cmds-filesystem.c to cmds-fi-usage.c in order to call it from both "fi show" and "fi usage". Signed-off-by: Tomohiro Misono --- cmds-fi-usage.c | 29 + cmds-fi-usage.h | 1 + cmds-filesystem.c | 27

[PATCH 0/2] btrfs-progs: fi: enable fi usage for filesystem top of seed device

Currently "fi usage" (and "dev usage") cannot run for the filesystem using seed device. This is because FS_INFO ioctl returns the number of devices excluding seeds, but load_device_info() tries to access valid device from devid 0 to max_id, and results in accessing seeds too (thus causing

btrfs send yields "ERROR: send ioctl failed with -5: Input/output error"

Was attempting my first btrfs send receive over ssh and continually received ioctl error at different points but always in the first 3 minutes. The volume consists of three devices with only metadata duplication. I narrowed down the error to the send command by recreating the error while

Re: 4.13: "error in btrfs_run_delayed_refs:3009: errno=-28 No space left" with 1.3TB unallocated / 737G free?

On 2017-10-19 12:14, Martin Raiber wrote: You could also mount with "enospc_debug" to give the devs more infos about this issue. I am having more ENOSPC issues with 4.9.x than with the latest 4.14. Here is the dmesg output with -o enospc_debug, hopefully it will be useful for someone:

Re: [PATCH v8 0/6] Btrfs: populate heuristic with code

2017-10-20 16:45 GMT+03:00 David Sterba : > On Fri, Oct 20, 2017 at 01:48:01AM +0300, Timofey Titovets wrote: >> 2017-10-19 18:39 GMT+03:00 David Sterba : >> > On Fri, Sep 29, 2017 at 06:22:00PM +0200, David Sterba wrote: >> >> On Thu, Sep 28, 2017 at 05:33:35PM

Re: [PATCH 1/1] btrfs-progs: docs: annual typo, clarity, & grammar review & fixups

Hi Nicholas, Thanks for the documentation update. Since I'm not a native English speaker, I may not help much to organize the sentence, but I can help to explain the question noted in the modification. On 2017年10月22日 08:00, Nicholas D Steeves wrote: > In one big patch, as requested > >

Re: SLES 11 SP4: can't mount btrfs

- Am 21. Okt 2017 um 20:07 schrieb Adam Borowski kilob...@angband.pl: >> > Yes it's possible to restore a btrfs partition from tape backup, /if/ you >> > backed up the partition itself, not just the files on top of it. > > Which is usually a quite bad idea: unless you shut down (or remount

Re: Cannot remove device, no space left on device

I have upgraded to kernel 4.13.8-1 and still cannot delete this disk. I find it weird that I cannot remove a from my array. Especially on one of the newest kernels available sourced straight from kernel.org On Sun, Oct 1, 2017 at 4:57 AM, Duncan <1i5t5.dun...@cox.net> wrote: > Adam Bahe posted