From: Marc MERLIN <marc@merlins.org>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: David Sterba <dsterba@suse.cz>,
Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-image failure (btrfs-tools 4.4)
Date: Thu, 11 Feb 2016 07:09:47 -0800 [thread overview]
Message-ID: <20160211150947.GY13969@merlins.org> (raw)
In-Reply-To: <56BC355F.1080305@cn.fujitsu.com>
On Thu, Feb 11, 2016 at 03:16:47PM +0800, Qu Wenruo wrote:
> >I started making a dump, image was growing past 3GB, and then it failed
> >and the image got deleted:
> >
> >gargamel:~# btrfs-image -s -c 9 /dev/mapper/dshelf1old /mnt/dshelf1/ds1old.dump
> >Error adding space cache blocks -5
>
> It seems that btrfs-image failed to read space cache, in
> read_data_extent() function.
>
> And since there is no "Couldn't map the block XXXX" error message,
> either some device is missing or pread64 failed to read the desired
> data.
It's a 5 drive raid5 underneath, all drives are there.
> >Is there a 4G file size limit, or did I hit another problem?
>
> For the 4G file size limit, did you mean the limit from old
> filesystem like FAT32?
No, I wrote on btrfs, so it's not a filesystem limit, but I meant that
maybe if there was a 32bit pointer somewhere, it could have caused this.
I did use the 64bit version of the tools on a 64bit kernel though, so I
don't see why it could have happened.
> I didn't think there is such limit for modern Linux filesystem, or
> normal read/write operation won't has such limit either.
Agreed.
At this point, is there anything else I should get/do before I wipe this
filesystem?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2016-02-11 15:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 0:27 BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0 Marc MERLIN
2016-01-18 3:21 ` Duncan
2016-01-18 23:39 ` Marc MERLIN
2016-01-19 9:39 ` Duncan
2016-01-21 4:52 ` Marc MERLIN
2016-01-23 17:03 ` Marc MERLIN
2016-01-23 23:13 ` Marc MERLIN
2016-01-25 1:37 ` Qu Wenruo
2016-01-25 15:55 ` 4.4.0: btrfs-send BUG_ON(sctx->cur_ino != sctx->cmp_key->objectid); Marc MERLIN
2016-01-25 19:46 ` Filipe Manana
2016-01-25 19:56 ` Marc MERLIN
2016-01-25 20:24 ` Filipe Manana
2016-01-25 21:21 ` Marc MERLIN
2016-01-25 20:55 ` BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0 Marc MERLIN
2016-01-26 1:03 ` Qu Wenruo
2016-02-11 6:31 ` btrfs-image failure (btrfs-tools 4.4) Marc MERLIN
2016-02-11 7:16 ` Qu Wenruo
2016-02-11 15:09 ` Marc MERLIN [this message]
2016-02-11 15:13 ` Marc MERLIN
2016-02-12 0:33 ` Qu Wenruo
2016-02-12 17:26 ` Marc MERLIN
2016-02-14 17:26 ` Marc MERLIN
2016-02-15 0:17 ` Qu Wenruo
2016-02-15 16:40 ` Marc MERLIN
2016-01-18 12:45 ` BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0 Hugo Mills
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=20160211150947.GY13969@merlins.org \
--to=marc@merlins.org \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).