From: Filipe Manana <fdmanana@suse.com>
To: Marc Dietrich <marvin24@gmx.de>, dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: FIBMAP unsupported
Date: Fri, 03 Oct 2014 14:15:11 +0100 [thread overview]
Message-ID: <542EA15F.9080703@suse.com> (raw)
In-Reply-To: <6603452.o3OqIjYaDr@ax5200p>
On 10/02/2014 11:11 PM, Marc Dietrich wrote:
> Am Donnerstag 02 Oktober 2014, 21:55:55 schrieb Marc Dietrich:
>> Will try to restore the file using btrfs restore....
>
> ok, restore worked. I did some more tests. This is unrelated to CoW. It seems
> that the "fallocate -n" in combination with "dd conv=notrunc" using large
> files (>10G) triggers it. Maybe this rings some bells.
Just tried it and I confirm filefrag's call to ioctl FS_IOC_FIEMAP fails
with -EEXIST.
It's actually a known issue affecting any of the 3.17 RCs (except RC1).
The extent map manipulation/merging is broken for some cases. Try with
this 2 patches on top of 3.17-rcX:
https://patchwork.kernel.org/patch/4929981/
https://patchwork.kernel.org/patch/4945191/
Or, alternatively, reverting this patch:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=51f395ad4058883e4273b02fdebe98072dbdc0d2
Someone else reported on this list a write/pwrite/writev failure with
errno EEXIST too (and apparently caused by the same reason).
This broken extent map handling is serious IMHO, it can make fsync log
bogus extent items for example, amongst other possible bad and weird things.
>
> Marc
>
> --
> 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
>
next prev parent reply other threads:[~2014-10-03 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 15:13 FIBMAP unsupported Marc Dietrich
2014-10-02 17:25 ` David Sterba
2014-10-02 17:39 ` Hugo Mills
2014-10-02 19:55 ` Marc Dietrich
2014-10-02 22:11 ` Marc Dietrich
2014-10-03 13:15 ` Filipe Manana [this message]
2014-10-04 21:33 ` Marc Dietrich
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=542EA15F.9080703@suse.com \
--to=fdmanana@suse.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=marvin24@gmx.de \
/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.