Re: help : "bad tree block start" -> btrfs forced readonly

2017-03-17 Thread Lionel Bouton
Hi, some news from the coal mine... Le 17/03/2017 à 11:03, Lionel Bouton a écrit : > [...] > I'm considering trying to use a 4 week old snapshot of the device to > find out if it was corrupted or not instead. It will still be a pain if > it works but rsync for less than a month of data is at

Re: help : "bad tree block start" -> btrfs forced readonly

2017-03-17 Thread Lionel Bouton
Le 17/03/2017 à 10:51, Roman Mamedov a écrit : > On Fri, 17 Mar 2017 10:27:11 +0100 > Lionel Bouton wrote: > >> Hi, >> >> Le 17/03/2017 à 09:43, Hans van Kranenburg a écrit : >>> btrfs-debug-tree -b 3415463870464 >> Here is what it gives me back : >> >>

Re: help : "bad tree block start" -> btrfs forced readonly

2017-03-17 Thread Roman Mamedov
On Fri, 17 Mar 2017 10:27:11 +0100 Lionel Bouton wrote: > Hi, > > Le 17/03/2017 à 09:43, Hans van Kranenburg a écrit : > > btrfs-debug-tree -b 3415463870464 > > Here is what it gives me back : > > btrfs-debug-tree -b 3415463870464 /dev/sdb > btrfs-progs v4.6.1

Re: help : "bad tree block start" -> btrfs forced readonly

2017-03-17 Thread Hans van Kranenburg
On 03/17/2017 10:27 AM, Lionel Bouton wrote: > Hi, > > Le 17/03/2017 à 09:43, Hans van Kranenburg a écrit : >> btrfs-debug-tree -b 3415463870464 > > Here is what it gives me back : > > btrfs-debug-tree -b 3415463870464 /dev/sdb > btrfs-progs v4.6.1 > checksum verify failed on 3415463870464

Re: help : "bad tree block start" -> btrfs forced readonly

2017-03-17 Thread Lionel Bouton
Hi, Le 17/03/2017 à 09:43, Hans van Kranenburg a écrit : > btrfs-debug-tree -b 3415463870464 Here is what it gives me back : btrfs-debug-tree -b 3415463870464 /dev/sdb btrfs-progs v4.6.1 checksum verify failed on 3415463870464 found A85405B7 wanted 01010101 checksum verify failed on

Re: help : "bad tree block start" -> btrfs forced readonly

2017-03-17 Thread Hans van Kranenburg
On 03/17/2017 09:11 AM, Lionel Bouton wrote: > Le 17/03/2017 à 05:32, Lionel Bouton a écrit : >> Hi, >> >> [...] >> I'll catch some sleep right now (it's 5:28 AM here) but I'll be able to >> work on this in 3 or 4 hours. > > I woke up to this : > > Mar 17 06:56:30 fileserver kernel:

Re: help : "bad tree block start" -> btrfs forced readonly

2017-03-17 Thread Lionel Bouton
Le 17/03/2017 à 05:32, Lionel Bouton a écrit : > Hi, > > [...] > I'll catch some sleep right now (it's 5:28 AM here) but I'll be able to > work on this in 3 or 4 hours. I woke up to this : Mar 17 06:56:30 fileserver kernel: btree_readpage_end_io_hook: 104476 callbacks suppressed Mar 17 06:56:30

help : "bad tree block start" -> btrfs forced readonly

2017-03-16 Thread Lionel Bouton
Hi, our largest BTRFS filesystem is damaged but I'm unclear if it is recoverable or not. This is a 20TB filesystem with ~13TB used in a virtual machine using virtio-scsi backed by Ceph (Firefly 0.8.10). The following messages have become more frequent : fileserver kernel: sd 0:0:1:0: [sdb] tag#