At 06/18/2017 09:42 PM, Adam Borowski wrote:
On Sun, Jun 18, 2017 at 07:23:00PM +0800, Qu Wenruo wrote:
[ 39.726215] BTRFS warning (device sda1): unhandled fiemap cache
detected: offset=phys$35798867968 len1072 flags=0x2008
[ 151.882586] BTRFS warning (device sda1): unhandled fiemap cache
detected: offset=phys$35798867968 len1072 flags=0x2008
I created file extents which returns 0x2008 and the last extent with 0x9.
But still failed to reproduce the error message.
BTW, I noticed that your output is a little strange.
Normally we should have "offset=%llu phys=%llu len=%llu and flags=0x%x".
But your output seems a little out of shape.
And further more, the len (if it's correct) is not aligned even to 512
bytes.
[24031.309852] BTRFS warning (device sda1): unhandled fiemap cache detected:
offset=0 phys=2012381351936 len=131072 flags=0x2008
Eh? All the numbers in my mails not only match that printf format but also
are nice round numbers; len being always 128KB (not in just what I posted,
also in all other occurences).
Well the new line seems pretty normal now.
I'll create a debug patch for you to get more info to pin down the bug.
But, in your replies there's '$'blahblab and 0x13"1072".
Seems something went wrong totally.
Perhaps there's some mail client borkage? I see it ok in my Sent mbox but
it could have been corrupted in transit or on your side.
Here's my current dmesg: http://sprunge.us/ajag
In my work mailbox, everything is just as fine as yours.
But my gmx mailbox gives the wrong output even the message has the same
message id (<20170617145725.y3wsex73aaf3v...@angband.pl>).
I'd reduce the usage of my gmx mailbox.
Thanks,
Qu
Meow!
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
