On Mon, Aug 1, 2016 at 9:26 AM, Chris Mason wrote:
>
>
> On 07/23/2016 04:05 PM, Chris Murphy wrote:
>>
>> Using btrfs-debug-tree, I'm finding something a bit odd about some of
>> the items in this 39P file.
>>
>> Seems normal
>>
>> item 71 key (994163 EXTENT_DATA 43689967616)
On 07/23/2016 04:05 PM, Chris Murphy wrote:
Using btrfs-debug-tree, I'm finding something a bit odd about some of
the items in this 39P file.
Seems normal
item 71 key (994163 EXTENT_DATA 43689967616) itemoff 12467 itemsize 53
extent data disk byte 617349906432 nr 80805888
Kindof a rudimentary way of making a debug tree smaller, by filtering
by inode...
[root@f24m images]# btrfs-debug-tree -t 583 /dev/sda5 | grep -A 50 -B
50 994163 > inode994163_39PBfile.txt
381K gzip file
https://drive.google.com/open?id=0B_2Asp8DGjJ9Rk1qMG54MUNDWkE
But I'm going to rm this file
Using btrfs-debug-tree, I'm finding something a bit odd about some of
the items in this 39P file.
Seems normal
item 71 key (994163 EXTENT_DATA 43689967616) itemoff 12467 itemsize 53
extent data disk byte 617349906432 nr 80805888
extent data offset 0 nr 80805888 ram 80805888
Here is the bug write up so far, which contains most of the relevant details.
https://bugzilla.redhat.com/show_bug.cgi?id=1359325
Here are three teasers to get you to look at the bug:
1.
[root@f24m ~]# ls -lsh /var/lib/libvirt/images
total 57G
1.5G -rw-r-. 1 qemu qemu 1.5G Jul 21 10:54