From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Josef Bacik <josef@toxicpanda.com>, Josef Bacik <jbacik@fusionio.com>
Subject: Re: btrfs scrub gives unable to find logical $hugenum len 16384
Date: Mon, 22 Apr 2013 16:00:02 +0200 [thread overview]
Message-ID: <201304221600.02454.Martin@lichtvoll.de> (raw)
In-Reply-To: <CAEzrpqf1_FU2p_A1c7fcefz4yxw-H3b=i5UemJtf=UtN=SjyYQ@mail.gmail.com>
Am Samstag, 20. April 2013 schrieb Josef Bacik:
> So I found your bug on the plane ride, as soon as I get home I'll email
> it. Thanks,
Did you get home yet?
I would like to know the impact of the bug. I am running from a restauration
of a backup via rsync which went without any errors, but still.
I also still have the backup dd image available for testing.
Thanks,
Martin
> Josef
>
> On Apr 20, 2013 4:43 AM, "Martin Steigerwald" <Martin@lichtvoll.de> wrote:
> > Am Samstag, 20. April 2013 schrieb Josef Bacik:
> > > On Fri, Apr 19, 2013 at 03:15:30AM -0600, Martin Steigerwald wrote:
> > > > Am Dienstag, 16. April 2013 schrieb Martin Steigerwald:
> > > > > On Saturday 13 April 2013 17:48:31 Martin Steigerwald wrote:
> > > > > > Hi!
> > > > > >
> > > > > > Please answer soon whether it would be a good idea to replay a
> > > > > > backup right now as I am leaving to Berlin tomorrow for a week
> > > > > > without my backup drive with me. Well, I made space on an
> > > > > > external 2,5 inch drive, that I can take with me. I am taking
> > > > > > that one with me, after having made sure it has a consistent
> > > > > > backup. :)
> > > > >
> > > > > Ping.
> > > > >
> > > > > Any hints on this one? I am going to recreate the filesystem next
> > > > > weekend at latest.
> > > > >
> > > > > I did not see any I/O or BTRFS errors in logs so far, so
> > > > > filesystem appears to be good.
> > > >
> > > > Last chance to let me dig out some more information about this.
> > > >
> > > > Even with lack of any other oddities I am not going to tolerate a
> > > > non scrubbing BTRFS filesystem for longer than a week and will
> > > > redo it during the weekend.
> > >
> > > Can you get a btrfs-image of the file system as it is and upload it
> > > somewhere for me to pull down so I can try and reproduce? Thanks,
> >
> > Hmmm, this doesn´t seem to work:
> >
> > merkaba:~#134> btrfs-image -c9 -t4 /dev/merkaba/home /mnt/zeit/home.img
> > checksum verify failed on 65536 wanted E79F04C2 found 73
> > checksum verify failed on 65536 wanted E79F04C2 found 73
> > Csum didn't match
> > btrfs-image: btrfs-image.c:394: flush_pending: Assertion `!(!eb)'
> > failed. zsh: abort btrfs-image -c9 -t4 /dev/merkaba/home
> > /mnt/zeit/home.img merkaba:~#134> btrfs-image /dev/merkaba/home
> > /mnt/zeit/home.img checksum verify failed on 65536 wanted E79F04C2
> > found 73
> > checksum verify failed on 65536 wanted E79F04C2 found 73
> > Csum didn't match
> > btrfs-image: btrfs-image.c:394: flush_pending: Assertion `!(!eb)'
> > failed. zsh: abort btrfs-image /dev/merkaba/home
> > /mnt/zeit/home.img merkaba:~#134>
> >
> >
> > merkaba:~> ls -l /mnt/zeit/home.img
> > -rw-r--r-- 1 root root 0 Apr 20 10:32 /mnt/zeit/home.img
> >
> >
> > In order to be able to restore to a sane setup, I will do the following
> > now:
> >
> > - make another rsync backup without deleting older backup snapshots in
> > case the BTRFS filesystem got corrupted and cannot retrieve some files
> > which seems
> > so from above and btrfs-debug-tree outputs.
> >
> > - make a dd backup of the home partition to my backup harddisk for
> > further investigation
> >
> > - recreate the home filesystem as BTRFS or Ext4/XFS. But I think I will
> > try BTRFS again, but I will put all the KDE Akonadi / Nepomuk related
> > stuff onto
> > another Ext4 partition as asked by a KDE developer to see whether the
> > mail data loss issue is somehow related to using BTRFS, cause the
> > developer as well as the main KMail developer also use KMail 2 with
> > POP3 and they have no
> > data losses.
> >
> >
> > I can try some stuff on the dd image then, maybe its still possible to
> > get an
> > btrfs-image somehow.
> >
> > Thanks,
> > --
> > Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
> > GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2013-04-22 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 15:48 btrfs scrub gives unable to find logical $hugenum len 16384 Martin Steigerwald
2013-04-13 16:03 ` Martin Steigerwald
2013-04-16 12:35 ` Martin Steigerwald
2013-04-19 9:15 ` Martin Steigerwald
2013-04-19 11:51 ` Liu Bo
2013-04-19 19:41 ` Martin Steigerwald
2013-04-20 3:49 ` Josef Bacik
2013-04-20 8:26 ` Martin Steigerwald
2013-04-20 8:43 ` Martin Steigerwald
[not found] ` <CAEzrpqf1_FU2p_A1c7fcefz4yxw-H3b=i5UemJtf=UtN=SjyYQ@mail.gmail.com>
2013-04-20 15:28 ` Martin Steigerwald
2013-04-22 14:00 ` Martin Steigerwald [this message]
2013-04-22 14:01 ` Martin Steigerwald
2013-04-22 15:25 ` Dan van der Ster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201304221600.02454.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=jbacik@fusionio.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.