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:
> >> > On Wed, 29 Jun 2016 13:08:30 -0600,
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:
>> > On Wed, 29 Jun 2016 13:08:30 -0600, Chris Murphy
>> > wrote :
>> >
>> > > >> > Ok I will follow your advice an
On Wed, Jun 29, 2016 at 1:16 PM, 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 fresh BTRFS
>> >> > volume. As explained on another email, rsync doesn't support
>> >> > reflink, so do you think it is w
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 fresh
> > > >> > BTRFS volume. As explained
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 fresh BTRFS
> > >> > volume. As explained on another email, rsync doesn't support
> > >> > reflink, so do you t
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
On Wed, Jun 29, 2016 at 1:02 PM, Saint Germain wrote:
>
> 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 t
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
On 2016-06-29 14:12, Saint Germain wrote:
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 corrupte
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
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 is
> always the
On Wed, Jun 29, 2016 at 3:50 AM, Saint Germain 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 of
the problem
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
On Tue, Jun 28, 2016 at 4:52 PM, Saint Germain 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?
> I don't
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 these options on and attempt a ddrescue on
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 these options on and attempt a ddrescue on /dev/sda
> to /dev/sdd.
> Then I will disconnect /dev/sda and reboot and
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
> >> wrote:
> >>
> >> >> BTRFS info (device sdb1): dev_repl
On Mon, Jun 27, 2016 at 6:00 PM, Chris Murphy wrote:
> There are two options since your drives support SCT ERC.
>
> 1.
> smartctl -l scterc,70,70 /dev/sdX ## done for both drives
>
> That will make sure the drive reports a read error in 7 seconds, well
> under the kernel's command timer of 7 sec
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
>> wrote:
>>
>> >> BTRFS info (device sdb1): dev_replace from /dev/sda1 (devid 1)
>> >> to /dev/sdd1 started scrub_handle_errored_
On Mon, Jun 27, 2016 at 5:03 PM, Saint Germain wrote:
>>
>
> Ok thanks I will begin to make an image with dd.
> Do you recommend to use sda or sdb ?
Well at the moment you're kinda stuck. I'd leave them together and
just get the data off the drive normally with cp -a (or just -r if you
don't car
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)
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
> > (btrfs replace start -f /dev/sda1 /dev/sdd1 /home):
> >
> > BTRFS
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): checksum error at logical 93445255168 on dev
>> /dev/sda1, secto
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
> (btrfs replace start -f /dev/sda1 /dev/sdd1 /home):
>
> BTRFS info (device sdb1): disk space caching is enabled
> BTRFS info (device sdb1): bd
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.1~bpo8+1
> >
> > When trying to replace a
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.1~bpo8+1
>
> When trying to replace a RAID1 drive (with btrfs replace start
> -f /dev/sda1 /dev/sdd1), the operation
26 matches
Mail list logo
