Re: [PATCH] btrfs: check options during subsequent mount

On 04/29/2017 01:26 PM, Andrei Borzenkov wrote: 28.04.2017 12:14, Anand Jain пишет: We allow recursive mounts with subvol options such as [1] [1] mount -o rw,compress=lzo /dev/sdc /btrfs1 mount -o ro,subvol=sv2 /dev/sdc /btrfs2 And except for the btrfs-specific subvol and subvolid options

Re: btrfs check bug

Am Dienstag, 18. April 2017, 21:34:33 CEST schrieben Sie: > Hi, > > i have to try to create a new extent-tree after checksum error not solveable > with srub or init-csum-tree. Now i got this failure output from btrfs > --repair: > > ERROR: errors found in extent allocation tree or chunk

Re: File system corruption, btrfsck abort

> On 28 Apr 2017, at 22:09, Chris Murphy wrote: > > On Fri, Apr 28, 2017 at 3:10 AM, Christophe de Dinechin > wrote: > >> >> QEMU qcow2. Host is BTRFS. Guests are BTRFS, LVM, Ext4, NTFS (winXP and >> win10) and HFS+ (macOS Sierra). I think I had

Re: btrfs check bug

Am Dienstag, 18. April 2017, 21:34:33 CEST schrieben Sie: > Hi, > > i have to try to create a new extent-tree after checksum error not solveable > with srub or init-csum-tree. Now i got this failure output from btrfs > --repair: > > ERROR: errors found in extent allocation tree or chunk

Re: btrfs, journald logs, fragmentation, and fallocate

> [ ... ] Instead, you can use raw files (preferably sparse unless > there's both nocow and no snapshots). Btrfs does natively everything > you'd gain from qcow2, and does it better: you can delete the master > of a cloned image, deduplicate them, deduplicate two unrelated images; > you can turn

Re: btrfs, journald logs, fragmentation, and fallocate

>> [ ... ] these extents are all over the place, they're not >> contiguous at all. 4K here, 4K there, 4K over there, back to >> 4K here next to this one, 4K over there...12K over there, 500K >> unwritten, 4K over there. This seems not so consequential on >> SSD, [ ... ] > Indeed there were recent

Re: File system corruption, btrfsck abort

On Sat, Apr 29, 2017 at 2:46 AM, Christophe de Dinechin wrote: > >> On 28 Apr 2017, at 22:09, Chris Murphy wrote: >> >> On Fri, Apr 28, 2017 at 3:10 AM, Christophe de Dinechin >> wrote: >> >>> >>> QEMU qcow2. Host is BTRFS.

Re: File system corruption, btrfsck abort

On Sat, Apr 29, 2017 at 2:46 AM, Christophe de Dinechin wrote: > Are there btrfs commands I could run on a read-only filesystem that would > give me this information? qemu-img info will give you the status of lazy refcounts. lsattr will show a capital C in the 3rd to last

[PATCH 1/1] btrfs-progs: send: fail on first -ENODATA only

Returning -ENODATA is only considered invalid on the first run of the loop. Signed-off-by: Christian Brauner --- cmds-receive.c | 20 ++-- 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/cmds-receive.c b/cmds-receive.c index

[PATCH 0/1] btrfs-progs: send: fail on first -ENODATA only

Christian Brauner (1): btrfs-progs: send: fail on first -ENODATA only cmds-receive.c | 20 ++-- 1 file changed, 14 insertions(+), 6 deletions(-) -- 2.11.0 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to

Can I see what device was used to mount btrfs?

I'm chasing issue with btrfs mounts under systemd (https://github.com/systemd/systemd/issues/5781) - to summarize, systemd waits for the final device that makes btrfs complete and mounts it using this device name. But in /proc/self/mountinfo we actually see another device name. Due to

ERROR: cannot find parent subvolume, can't see reason for it.

I am trying to do a "send -p src/snp1 src/snp2 dst/" and getting the following error: ERROR: cannot find parent subvolume The "src/snp1" is present in both "src/" and "dst/". The "src/snp2" is present in "src/" . The send works when "-p" is not used, but will not work when it is. I