On Sun, Jul 16, 2017 at 04:01:53PM +0200, Giuseppe Della Bianca wrote:
> > On Fri, Jul 14, 2017 at 06:22:16PM -0700, Marc MERLIN wrote:
> > > Dear Chris and other developers,
> ]zac[
> > Others on this thread with the same error: did anyone recover from this
> > without wiping the filesystem?
> >
> On Fri, Jul 14, 2017 at 06:22:16PM -0700, Marc MERLIN wrote:
> > Dear Chris and other developers,
]zac[
> Others on this thread with the same error: did anyone recover from this
> without wiping the filesystem?
>
> Is there a chance a balance might work around the bug so that whatever
> layout
Hi Wictor, Hi List
I'm more or less stuck with the same problem as you. Btrfs on my
external drive got corrupted after I moved a lot of files to it and
would'n mount anymore.
This happened to me in november 2015 and I haven't tried again since
today, as tools and code have matured eventually.
I
let me share with you a segfault on btrfs --repair
I have backups etc. latest kernel and progs.
[root@node ~]# uname -a
Linux node 4.12.2 #1 SMP Sun Jul 16 08:15:48 EEST 2017 x86_64 x86_64
x86_64 GNU/Linux
[root@node ~]# btrfs version
btrfs-progs v4.11.1
GNU gdb (GDB) Red Hat Enterprise Linux
16.07.2017 02:03, Cerem Cem ASLAN пишет:
> A few days ago I tried to copy my backups to another machine by using
> my external hard drive. `btrfs send my-backup | btrfs receive
> /path/to/backup/dir` didn't go right since destination snapshot's
> "Received UUID" does not match with source's
