From: Marc Dietrich <marvin24@gmx.de>
To: Filipe Manana <fdmanana@suse.com>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: FIBMAP unsupported
Date: Sat, 4 Oct 2014 23:33:33 +0200 [thread overview]
Message-ID: <20141004233333.a31053a21e4f5c446e4eebac@gmx.de> (raw)
In-Reply-To: <542EA15F.9080703@suse.com>
On Fri, 03 Oct 2014 14:15:11 +0100
Filipe Manana <fdmanana@suse.com> wrote:
> 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/
ok, 2nd patch did not apply cleanly, so I just replaced the < with <=.
Otherwise, I can confirm the patches are fixing the issue here.
> 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.
Yes, it clearly corrupted by files in a strange way. Please try to get
it into final, or at least -stable if too late.
Marc
prev parent reply other threads:[~2014-10-04 21:33 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
2014-10-04 21:33 ` Marc Dietrich [this message]
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=20141004233333.a31053a21e4f5c446e4eebac@gmx.de \
--to=marvin24@gmx.de \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=fdmanana@suse.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 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).