Re: Need some help: "BTRFS critical (device sda): corrupt leaf, slot offset bad: block"

On 04.04.2017 18:55, Chris Murphy wrote: > On Tue, Apr 4, 2017 at 10:52 AM, Chris Murphy wrote: > > >> Mounting -o ro,degraded is probably permitted by the file system, but >> chunks of the file system and certainly your data, will be missing. So >> it's just a matter

Re: Need some help: "BTRFS critical (device sda): corrupt leaf, slot offset bad: block"

On 03.04.2017 16:25, Robert Krig wrote: > > I'm gonna run a extensive memory check once I get home, since you > mentioned corrupt memory might be an issue here. > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message

Re: Need some help: "BTRFS critical (device sda): corrupt leaf, slot offset bad: block"

On 03.04.2017 16:20, Robert Krig wrote: > > On 03.04.2017 16:08, Hans van Kranenburg wrote: >> On 04/03/2017 12:11 PM, Robert Krig wrote: >> The corruption is at item 157. Can you attach all of the output, or >> pastebin it? >> > > I've attache

Re: Need some help: "BTRFS critical (device sda): corrupt leaf, slot offset bad: block"

On 03.04.2017 16:08, Hans van Kranenburg wrote: > On 04/03/2017 12:11 PM, Robert Krig wrote: > The corruption is at item 157. Can you attach all of the output, or > pastebin it? > I've attached the entire log of btrfs-debug-tree. This was generated with btrfs-progs 4.7.3

Re: Need some help: "BTRFS critical (device sda): corrupt leaf, slot offset bad: block"

On 03.04.2017 12:11, Robert Krig wrote: > Hi guys, I seem to have run into a spot of trouble with my btrfs partition. > > I've got 4 x 8TB in a RAID1 BTRFS configuration. > > I'm running Debian Jessie 64 Bit, 4.9.0-0.bpo.2-amd64 kernel. Btrfs > progs version v4.7.3 > &g

Need some help: "BTRFS critical (device sda): corrupt leaf, slot offset bad: block"

Hi guys, I seem to have run into a spot of trouble with my btrfs partition. I've got 4 x 8TB in a RAID1 BTRFS configuration. I'm running Debian Jessie 64 Bit, 4.9.0-0.bpo.2-amd64 kernel. Btrfs progs version v4.7.3 Server has 8GB of Ram. I was running duperemove using a hashfile, which seemed

Re: Announcing btrfs-dedupe 1.1.0

> > git clone > https://gitlab.wellbehavedsoftware.com/well-behaved-software/btrfs-dedupe.git > > Then cd in and build using cargo: > > cd btrfs-dedupe > cargo build --release > > There is basically just one binary which will end up in > target/release/btrfs-dedup

Re: Announcing btrfs-dedupe 1.1.0

Hi, could you include some build instructions for people that are unfamiliar with compiling rust code? On 08.01.2017 17:57, James Pharaoh wrote: > Hi everyone, > > I'm pleased to announce a new version of my btrfs-dedupe tool, written > in rust, available here: > > http://btrfs-dedupe.com/ > >

Re: btrfs crashing the kernel with Seagate 8TB SMR drives.

As Chris mentioned, check out the Bug report here: https://bugzilla.kernel.org/show_bug.cgi?id=93581 I have a 8TB SMR Drive and the kernel was reporting drive errors. Switching to Kernel 3.16 (Standard Debian Jessie kernel) fixed it for me ( for the moment). >From what I read in that kernel bug

btrfs-balance convert from raid1 to single on specific device?

Hi, I'm running Kernel 4.3 and Btrfs-tools 4.3 on Debian Jessie. I compiled the tools and kernel myself. Recently I added a new disk to my btrfs volume and wanted to proceed to convert from single to raid1. Unfortunately the new disk seems to be faulty and started throwing a lot of errors. The

Re: btrfs-balance convert from raid1 to single on specific device?

iling list to be merged into one of the repos. What would be the easiest way for me to compile that specific patch? Which kernel version sources do I ideally need? Is there a git repo that already has that patch included? Thank you for your help. On 10.11.2015 11:22, Robert Krig wrote: > Hi, &g

btrfs raid1 metadata, single data

Hi, I was wondering. What exactly is contained in btrfs metadata? I've read about some users setting up their btrfs volumes as data=single, but metadata=raid1 Is there any actual benefit to that? I mean, if you keep your data as single, but have multiple copies of metadata, does that still

Recreate Snapshots and their Parent Relationships on a second Server.

Hi. I have an Old Server with a bunch of btrfs Snapshots. I'm setting up a new server and I would like to transfer those Snapshots as efficiently as possible, while still maintaining their parent-child relationships for space efficient storage. Apart from manually using btrfs send and btrfs send