[PATCH] btrfs-convert: document -O|--features flag

Copy-pasted description found at mkfs.btrfs. I did not bother with feature list as it seemed to be incomplete. --- Documentation/btrfs-convert.asciidoc | 7 +++ 1 file changed, 7 insertions(+) diff --git a/Documentation/btrfs-convert.asciidoc b/Documentation/btrfs-convert.asciidoc index

Re: BTRFS Raid 6 corruption - please help with restore

On Wed, Mar 2, 2016 at 3:47 AM, Stuart Gittings wrote: > Hi - I have some corruption on a 12 drive Raid 6 volume. Here's the > basics - if someone could help with restore it would save me a ton of > time (and some data loss - I have critical data backed up, but not > all).

[PATCH] Btrfs: fix loading of orphan roots leading to BUG_ON

From: Filipe Manana When looking for orphan roots during mount we can end up hitting a BUG_ON() (at root-item.c:btrfs_find_orphan_roots()) if a log tree is replayed and qgroups are enabled. This is because after a log tree is replayed, a transaction commit is made, which

[PATCH] fstests: btrfs, test log replay with qgroups enabled and orphan roots

From: Filipe Manana Test that replaying a log tree when qgroups are enabled and orphan roots (deleted snapshots) exist, the replay process does not crash. This is motivated by a bug found in btrfs, introduced in the linux kernel 4.4 release, and is fixed by the following

Re: BTRFS Raid 6 corruption - please help with restore

On Wed, Mar 2, 2016 at 11:42 AM, Stuart Gittings wrote: > All devices are present. Btrfs if show is listed below and shows they are > all there. I'm afraid btrfs dev scan does not help What do you get for 'btrfs check' (do not use --repair yet) -- Chris Murphy --

duplicate automounts with btrfs RAID1

Hello, Not entirely sure this is a btrfs issue, but here is my problem. I've had this issue with recent Fedora and CentOS distros. I created a btrfs RAID 1 pair with two identical USB external drives, following the instructions found online: mkfs.btrfs -m raid1 -d raid1 /dev/sdc1 /dev/sdd1

Re: [RFC] Experimental btrfs encryption

Thanks! for commenting Qu. As you are working near these codes appreciate any code review comments. +1 here, but in fact, it's easy to deal with. As long as not implement encryption as a compression method. Just like inband dedup, we use the following method to support dedup and

Re: [RFC] Experimental btrfs encryption

Hi Qu, Not only move, but also reflink/inband dedup. oh yes thanks. I shall add those. Yes, but in fact, you can use another method, just like in-band de-dup, by adding new hook into async_cow_start() and async_cow_end(), allowing compression and encryption can be done at the same time.

Re: Again, no space left on device while rebalancing and recipe doesnt work

2016-02-27 23:14 GMT+02:00 Marc Haber : > Hi, > > I have again the issue of no space left on device while rebalancing > (with btrfs-tools 4.4.1 on kernel 4.4.2 on Debian unstable): > I've same issue, 4.4.3 kernel on Arch Linux $ sudo btrfs fi show /mnt/fs/ Label:

Re: duplicate automounts with btrfs RAID1

and disk/ata/usb resets? On Wed, Mar 2, 2016 at 10:56 PM, Leigh Orf wrote: > On Wed, Mar 2, 2016 at 3:34 PM, Pavol Cupka wrote: >> is anything in dmesg that would point to diskscontrollers being reset? >> >> or something like that? >> >> pavol > >

Re: duplicate automounts with btrfs RAID1

On Wed, Mar 2, 2016 at 3:34 PM, Pavol Cupka wrote: > is anything in dmesg that would point to diskscontrollers being reset? > > or something like that? > > pavol Pavol, Hmm, yes, there are some weird things going on. I am attaching what I see as the relevant bits from

Re: "WARNING: device 0 not present" during scrub?

On 01.02.2016 11:23, Patrik Lundquist wrote: > apt-get install -t jessie-backports linux-image-4.3.0-0.bpo.1-amd64 > > Or something like that for the image name. Unfortunately there's no > stable backport of btrfs-tools (as they call btrfs-progs). There is now: 4.4-1~bpo8+1 Upgrading from

Re: duplicate automounts with btrfs RAID1

is anything in dmesg that would point to diskscontrollers being reset? or something like that? pavol On Wed, Mar 2, 2016 at 9:34 PM, Leigh Orf wrote: > Hello, > > Not entirely sure this is a btrfs issue, but here is my problem. I've > had this issue with recent Fedora and

Re: [RFC] Experimental btrfs encryption

Anand Jain wrote on 2016/03/02 16:50 +0800: Thanks! for commenting Qu. As you are working near these codes appreciate any code review comments. +1 here, but in fact, it's easy to deal with. As long as not implement encryption as a compression method. Just like inband dedup, we use the

Re: duplicate automounts with btrfs RAID1

First, If /dev/sdc1 is getting disappeared and reappearing you may have this problem, securing the connection for /dev/sdc1 will help. But, Should automount be more intelligent to identify FSID thats already mounted ? In btrfs RAIDs, Both /dev/sdc1 /dev/sdd1 contains same FSID. With btrfs its

incomplete conversion to RAID1?

Hi, I recently moved my main system to btrfs and had to shuffle everything around in tricky ways while migrating from LVM while maintaining at least two copies + backup of everything. I'm using linux-4.4.3 with btrfs-progs-4.4.1. The end result, after adding sdc and then converting both

Re: [RFC] Experimental btrfs encryption

Anand Jain wrote on 2016/03/02 17:09 +0800: Hi Qu, Not only move, but also reflink/inband dedup. oh yes thanks. I shall add those. Yes, but in fact, you can use another method, just like in-band de-dup, by adding new hook into async_cow_start() and async_cow_end(), allowing

Re: [RFC] Experimental btrfs encryption

. (I received couple of private emails on this, so looks like I confused you and I'm writing again to clear the air on this). - Uses btrfs compression framework, so compression and then encryption is not possible. However yet evaluate if there are encryption algorithm which can

Re: Again, no space left on device while rebalancing and recipe doesnt work

Thanks for the output. At least for mprofile enospc error, the problem itself is very straightforward, just unable to alloc tree block. I'll check the codes to see if we can improve it, by finding out why we can't alloc a new chunk to resolve the problem. But I'm still a little concerned

Re: [PATCH] Btrfs: fix loading of orphan roots leading to BUG_ON

fdmanana posted on Wed, 02 Mar 2016 15:49:38 + as excerpted: > When looking for orphan roots during mount we can end up hitting a > BUG_ON() (at root-item.c:btrfs_find_orphan_roots()) if a log tree is > replayed and qgroups are enabled. This should hit 4.6, right? Will it hit 4.5 before

Re: Again, no space left on device while rebalancing and recipe doesnt work

Dāvis Mosāns wrote on 2016/03/03 02:28 +0200: 2016-02-27 23:14 GMT+02:00 Marc Haber : Hi, I have again the issue of no space left on device while rebalancing (with btrfs-tools 4.4.1 on kernel 4.4.2 on Debian unstable): I've same issue, 4.4.3 kernel on Arch

Re: raid5

Austin S. Hemmelgarn posted on Wed, 02 Mar 2016 08:43:17 -0500 as excerpted: > On 2016-03-01 16:44, Duncan wrote: >> John Smith posted on Tue, 01 Mar 2016 15:24:04 +0100 as excerpted: >> >>> what is the status of btrfs raid5 in kernel 4.4? Thank you >> >> That is a very good question. =:^) >> >>

Re: Again, no space left on device while rebalancing and recipe doesnt work

Dāvis Mosāns posted on Thu, 03 Mar 2016 02:28:36 +0200 as excerpted: > 2016-02-27 23:14 GMT+02:00 Marc Haber : >> Hi, >> >> I have again the issue of no space left on device while rebalancing >> (with btrfs-tools 4.4.1 on kernel 4.4.2 on Debian unstable): >> >> > I've

Re: incomplete conversion to RAID1?

Nicholas D Steeves posted on Wed, 02 Mar 2016 20:25:46 -0500 as excerpted: > btrfs fi show > Label: none uuid: 2757c0b7-daf1-41a5-860b-9e4bc36417d3 > Total devices 2 FS bytes used 882.28GiB > devid1 size 926.66GiB used 886.03GiB path /dev/sdb1 > devid2 size

Re: [PATCH] Btrfs: fix loading of orphan roots leading to BUG_ON

Duncan wrote on 2016/03/03 04:31 +: fdmanana posted on Wed, 02 Mar 2016 15:49:38 + as excerpted: When looking for orphan roots during mount we can end up hitting a BUG_ON() (at root-item.c:btrfs_find_orphan_roots()) if a log tree is replayed and qgroups are enabled. This should hit

Re: [PATCH] Btrfs: fix loading of orphan roots leading to BUG_ON

wrote on 2016/03/02 15:49 +: From: Filipe Manana When looking for orphan roots during mount we can end up hitting a BUG_ON() (at root-item.c:btrfs_find_orphan_roots()) if a log tree is replayed and qgroups are enabled. This is because after a log tree is replayed, a

Re: [PATCH] Btrfs: fix loading of orphan roots leading to BUG_ON

Qu Wenruo posted on Thu, 03 Mar 2016 14:26:45 +0800 as excerpted: > Never heard the 2 release cycles principle, but seems to be not flex > enough. > From this point of view, every time Filipe(just an example, as he finds > the most of bugs and corner case), some part or even the whole btrfs is >

Re: btrfs-progs: initial scan-build results

On Tue, Mar 01, 2016 at 05:39:29PM +0100, Holger Hoffstätte wrote: > On 03/01/16 16:45, Holger Hoffstätte wrote: > > On 03/01/16 14:41, Alexander Fougner wrote: > >> All zero-sized allocations are false positives, except the > > Right, I've now also reviewed them all and they are all guarded > by

Re: duplicate automounts with btrfs RAID1

Leigh Orf posted on Wed, 02 Mar 2016 14:34:41 -0600 as excerpted: > Here is info about my setup (up to date CentOS 7.2): > > % cat /etc/system-release > CentOS Linux release 7.2.1511 (Core) > % uname -a > Linux xxx.xxx.xxx.edu 3.10.0-123.20.1.el7.x86_64 #1 SMP > Thu Jan 29 18:05:33 UTC 2015

BTRFS Raid 6 corruption - please help with restore

Hi - I have some corruption on a 12 drive Raid 6 volume. Here's the basics - if someone could help with restore it would save me a ton of time (and some data loss - I have critical data backed up, but not all). stuart@debian:~$ uname -a Linux debian 4.3.0-0.bpo.1-amd64 #1 SMP Debian

Re: raid5

On 2016-03-01 16:44, Duncan wrote: John Smith posted on Tue, 01 Mar 2016 15:24:04 +0100 as excerpted: what is the status of btrfs raid5 in kernel 4.4? Thank you That is a very good question. =:^) The answer, to the best I can give it, is, btrfs raid56 mode has no known outstanding bugs

Still in 4.4.0: livelock in recovery (free_reloc_roots)

On 11/20/2015 10:04 AM, Lukas Pirl wrote as excerpted: > I am (still) trying to recover a RAID1 that can only be mounted > recovery,degraded,ro. > > I experienced an issue that might be interesting for you: I tried to > mount the file system rw,recovery and the kernel ended up burning one > core