From: jim owens <owens6336@gmail.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: extent map merge bad block_len
Date: Wed, 17 Mar 2010 15:27:56 -0400 [thread overview]
Message-ID: <4BA12D3C.4000905@gmail.com> (raw)
Chris,
Something that probably should be fixed is how
merging extent maps with block_len == -1 produces
illegal lengths, as in 8191.
I saw it with holes in directIO and it is not the
cause of my current problems so I'll hope someone
else decides to fix.
jim
reply other threads:[~2010-03-17 19:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BA12D3C.4000905@gmail.com \
--to=owens6336@gmail.com \
--cc=chris.mason@oracle.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.