Re: Announcing btrfs-dedupe

2016-11-09 Thread Saint Germain
On Wed, 09 Nov 2016 12:24:51 +0100, Niccolò Belli wrote : > > On martedì 8 novembre 2016 23:36:25 CET, Saint Germain wrote: > > Please be aware of these other similar softwares: > > - jdupes: https://github.com/jbruchon/jdupes > > - rmlint: https://github.com/sahib/

Re: Announcing btrfs-dedupe

2016-11-08 Thread Saint Germain
On Sun, 6 Nov 2016 14:30:52 +0100, James Pharaoh wrote : > Hi all, > > I'm pleased to announce my btrfs deduplication utility, written in > Rust. This operates on whole files, is fast, and I believe > complements the existing utilities (duperemove, bedup), which exist > currently. > > Please vi

Re: Identifying reflink / CoW files

2016-11-04 Thread Saint Germain
On Thu, 3 Nov 2016 01:17:07 -0400, Zygo Blaxell wrote : > On Thu, Oct 27, 2016 at 01:30:11PM +0200, Saint Germain wrote: > > Hello, > > > > Following the previous discussion: > > https://www.spinics.net/lists/linux-btrfs/msg19075.html > > > > I would be

Identifying reflink / CoW files

2016-10-27 Thread Saint Germain
Hello, Following the previous discussion: https://www.spinics.net/lists/linux-btrfs/msg19075.html I would be interested in finding a way to reliably identify reflink / CoW files in order to use deduplication programs (like fdupes, jdupes, rmlint) efficiently. Using FIEMAP doesn't seem to be reli

Re: Kernel bug during RAID1 replace

2016-06-30 Thread Saint Germain
On Wed, 29 Jun 2016 18:24:07 -0600, Chris Murphy wrote : > On Wed, Jun 29, 2016 at 5:51 PM, Saint Germain > wrote: > > On Wed, 29 Jun 2016 19:23:57 +, Hugo Mills > > wrote : > > > >> On Wed, Jun 29, 2016 at 09:16:13PM +0200, Saint Germain wrote: > >

Re: Kernel bug during RAID1 replace

2016-06-29 Thread Saint Germain
On Wed, 29 Jun 2016 19:23:57 +, Hugo Mills wrote : > On Wed, Jun 29, 2016 at 09:16:13PM +0200, Saint Germain wrote: > > On Wed, 29 Jun 2016 13:08:30 -0600, Chris Murphy > > wrote : > > > > > >> > Ok I will follow your advice and start over with a fres

Re: Kernel bug during RAID1 replace

2016-06-29 Thread Saint Germain
On Wed, 29 Jun 2016 13:08:30 -0600, Chris Murphy wrote : > >> > Ok I will follow your advice and start over with a fresh BTRFS > >> > volume. As explained on another email, rsync doesn't support > >> > reflink, so do you think it is worth trying with BTRFS send > >> > instead ? Is it safe to copy

Re: Kernel bug during RAID1 replace

2016-06-29 Thread Saint Germain
On Wed, 29 Jun 2016 14:19:23 -0400, "Austin S. Hemmelgarn" wrote : > >>> Already got a backup. I just really want to try to repair it (in > >>> order to test BTRFS). > >> > >> I don't know that this is a good test because I think the file > >> system has already been sufficient corrupted that it

Re: Kernel bug during RAID1 replace

2016-06-29 Thread Saint Germain
On Wed, 29 Jun 2016 11:28:24 -0600, Chris Murphy wrote : > > Already got a backup. I just really want to try to repair it (in > > order to test BTRFS). > > I don't know that this is a good test because I think the file system > has already been sufficient corrupted that it can't be fixed. Part o

Re: Kernel bug during RAID1 replace

2016-06-29 Thread Saint Germain
On Wed, 29 Jun 2016 11:50:55 +0200, Saint Germain wrote : > So if I understand correctly, you advise to use check --repair > --init-csum-tree and delete the files which were reported as having > checksum error ? > After that I can compare the important files to a backup, but there

Re: Kernel bug during RAID1 replace

2016-06-29 Thread Saint Germain
On Tue, 28 Jun 2016 22:25:32 -0600, Chris Murphy wrote : > > Well I made a ddrescue image of both drives (only one error on sdb > > during ddrescue copy) and started the computer again (after > > disconnecting the old drives). > > What was the error? Any kernel message at the time of this error

Re: Kernel bug during RAID1 replace

2016-06-28 Thread Saint Germain
On Mon, 27 Jun 2016 20:14:58 -0600, Chris Murphy wrote : > On Mon, Jun 27, 2016 at 6:49 PM, Saint Germain > wrote: > > > > > I've tried both option and launched a replace, but I got the same > > error (replace is cancelled, jernel bug). > > I will let thes

Re: Kernel bug during RAID1 replace

2016-06-27 Thread Saint Germain
On Mon, 27 Jun 2016 18:00:34 -0600, Chris Murphy wrote : > On Mon, Jun 27, 2016 at 5:06 PM, Saint Germain > wrote: > > On Mon, 27 Jun 2016 16:58:37 -0600, Chris Murphy > > wrote : > > > >> On Mon, Jun 27, 2016 at 4:55 PM, Chris Murphy > >> w

Re: Kernel bug during RAID1 replace

2016-06-27 Thread Saint Germain
On Mon, 27 Jun 2016 16:58:37 -0600, Chris Murphy wrote : > On Mon, Jun 27, 2016 at 4:55 PM, Chris Murphy > wrote: > > >> BTRFS info (device sdb1): dev_replace from /dev/sda1 (devid 1) > >> to /dev/sdd1 started scrub_handle_errored_block: 166 callbacks > >> suppressed BTRFS warning (device sdb1)

Re: Kernel bug during RAID1 replace

2016-06-27 Thread Saint Germain
On Mon, 27 Jun 2016 16:55:07 -0600, Chris Murphy wrote : > On Mon, Jun 27, 2016 at 4:26 PM, Saint Germain > wrote: > > >> > > > > Thanks for your help. > > > > Ok here is the log from the mounting, and including btrfs replace > > (

Re: Kernel bug during RAID1 replace

2016-06-27 Thread Saint Germain
On Mon, 27 Jun 2016 15:42:42 -0600, Chris Murphy wrote : > On Mon, Jun 27, 2016 at 3:36 PM, Saint Germain > wrote: > > Hello, > > > > I am on Debian Jessie with a kernel from backports: > > 4.6.0-0.bpo.1-amd64 > > > > I am also using btrfs-tools 4.4.1-1

Kernel bug during RAID1 replace

2016-06-27 Thread Saint Germain
Hello, I am on Debian Jessie with a kernel from backports: 4.6.0-0.bpo.1-amd64 I am also using btrfs-tools 4.4.1-1.1~bpo8+1 When trying to replace a RAID1 drive (with btrfs replace start -f /dev/sda1 /dev/sdd1), the operation is cancelled after completing only 5%. I got this error in the /var/l

Re: BTRFS with RAID1 cannot boot when removing drive

2014-02-16 Thread Saint Germain
On Fri, 14 Feb 2014 15:33:10 +0100, Saint Germain wrote : > On 11 February 2014 03:30, Saint Germain wrote: > >> > I am experimenting with BTRFS and RAID1 on my Debian Wheezy (with > >> > backported kernel 3.12-0.bpo.1-amd64) using a a motherboard with > >>

Re: BTRFS with RAID1 cannot boot when removing drive

2014-02-14 Thread Saint Germain
On 11 February 2014 03:30, Saint Germain wrote: >> > I am experimenting with BTRFS and RAID1 on my Debian Wheezy (with >> > backported kernel 3.12-0.bpo.1-amd64) using a a motherboard with >> > UEFI. >> >> > I have installed Debian with the following

Re: BTRFS partitioning scheme (was BTRFS with RAID1 cannot boot when removing drive)

2014-02-13 Thread Saint Germain
On Thu, 13 Feb 2014 10:43:08 -0700, Chris Murphy wrote : > >>> sda3 = 1 TiB root partition (BTRFS), mounted on / > >>> sda4 = 6 GiB swap partition > >>> (that way I should be able to be compatible with both CSM or UEFI) > >>> > >>> B) normal Debian installation on sdas, activate the CSM on the >

Re: BTRFS partitioning scheme (was BTRFS with RAID1 cannot boot when removing drive)

2014-02-13 Thread Saint Germain
On 13 February 2014 09:50, Frank Kingswood wrote: > On 12/02/14 17:13, Saint Germain wrote: >> >> Ok based on your advices, here is what I have done so far to use UEFI >> (remeber that the objective is to have a clean and simple BTRFS RAID1 >> install). >> >&g

Re: BTRFS with RAID1 cannot boot when removing drive

2014-02-12 Thread Saint Germain
On 11 February 2014 21:35, Duncan <1i5t5.dun...@cox.net> wrote: > Saint Germain posted on Tue, 11 Feb 2014 11:04:57 +0100 as excerpted: > >> The big problem I currently have is that based on your input, I hesitate >> a lot on my partitioning scheme: should I use a dedicat

Re: BTRFS partitioning scheme (was BTRFS with RAID1 cannot boot when removing drive)

2014-02-12 Thread Saint Germain
On 11 February 2014 19:15, Chris Murphy wrote: >> >> To summarize, I think I have 3 options for partitioning (I am not >> considering UEFI secure boot or swap): >> 1) grub, BTRFS partition (i.e. full disk in BTRFS), /boot inside BTRFS >> subvolume > > This doesn't seem like a good idea for a boot

Re: BTRFS with RAID1 cannot boot when removing drive

2014-02-11 Thread Saint Germain
On 11 February 2014 18:21, Chris Murphy wrote: > > On Feb 10, 2014, at 8:15 PM, Saint Germain wrote: >> >> Ok I need to really understand how my motherboard works (new Z87E-ITX). >> It is written "64Mb AMI UEFI Legal BIOS", so I thought it was really >>

BTRFS partitioning scheme (was BTRFS with RAID1 cannot boot when removing drive)

2014-02-11 Thread Saint Germain
Hello and thanks for your feedback ! Cc back to the mailing-list as it may be of interest here as well. On 11 February 2014 16:11, Kyle Gates wrote: >> The big problem I currently have is that based on your input, I >> hesitate a lot on my partitioning scheme: should I use a dedicated >> /boot p

Re: BTRFS with RAID1 cannot boot when removing drive

2014-02-11 Thread Saint Germain
On 11 February 2014 07:59, Duncan <1i5t5.dun...@cox.net> wrote: > Saint Germain posted on Tue, 11 Feb 2014 04:15:27 +0100 as excerpted: > >> Ok I need to really understand how my motherboard works (new Z87E-ITX). >> It is written "64Mb AMI UEFI Legal BIOS",

Re: BTRFS with RAID1 cannot boot when removing drive

2014-02-10 Thread Saint Germain
Hello ! On Mon, 10 Feb 2014 19:18:22 -0700, Chris Murphy wrote : > > On Feb 9, 2014, at 2:40 PM, Saint Germain wrote: > > > > Then I added another drive for a RAID1 configuration (with btrfs > > balance) and I installed grub on the second hard drive with &g

Re: BTRFS with RAID1 cannot boot when removing drive

2014-02-10 Thread Saint Germain
Hello Duncan, What an amazing extensive answer you gave me ! Thank you so much for it. See my comments below. On Mon, 10 Feb 2014 03:34:49 + (UTC), Duncan <1i5t5.dun...@cox.net> wrote : > > I am experimenting with BTRFS and RAID1 on my Debian Wheezy (with > > backported kernel 3.12-0.bpo.1-

BTRFS with RAID1 cannot boot when removing drive

2014-02-09 Thread Saint Germain
Hello, I am experimenting with BTRFS and RAID1 on my Debian Wheezy (with backported kernel 3.12-0.bpo.1-amd64) using a a motherboard with UEFI. However I haven't managed to make the system boot when the removing the first hard drive. I have installed Debian with the following partition on the fi