On 2019/10/3 上午11:07, Andrey Ivanov wrote:
> On 03.10.2019 5:19, Qu Wenruo wrote:
>> The problem is the invalid dir item size caused by that bitflip.
>>
>> I'm afraid there are too many unexpected bitflips.
>>
>> But at least you can try to salvage some data.
>
> As I can see, there is only one
On 03.10.2019 5:19, Qu Wenruo wrote:
The problem is the invalid dir item size caused by that bitflip.
I'm afraid there are too many unexpected bitflips.
But at least you can try to salvage some data.
As I can see, there is only one damaged directory, which did not
contain any important data.
On 2019/10/3 上午10:18, Andrey Ivanov wrote:
> On 03.10.2019 5:00, Qu Wenruo wrote:
>>> I think "btrfs check" is looped somewhere. Or not?
>>
>> You can try "btrfs check --mode=lowmem --repair" as an alternative.
>
> $ btrfs check -p --mode=lowmem --repair sda4.image.copy
> enabling repair mode
>
On 03.10.2019 5:00, Qu Wenruo wrote:
I think "btrfs check" is looped somewhere. Or not?
You can try "btrfs check --mode=lowmem --repair" as an alternative.
$ btrfs check -p --mode=lowmem --repair sda4.image.copy
enabling repair mode
WARNING: low-memory mode repair support is only partial
Open
On 2019/10/3 上午9:47, Andrey Ivanov wrote:
> On 01.10.2019 8:35, Qu Wenruo wrote:
I recommend to do a "btrfs check" on all fses.
>>>
>>> I had done "btrfs check" on /dev/sda4:
>>>
>>> attached btrfs-check-sda4.output
>>>
>>> There are some errors. How to fix them?
>>
>> It looks like "btrfs c
On 01.10.2019 8:35, Qu Wenruo wrote:
I recommend to do a "btrfs check" on all fses.
I had done "btrfs check" on /dev/sda4:
attached btrfs-check-sda4.output
There are some errors. How to fix them?
It looks like "btrfs check --repair" can handle most of these bugs.
Please do a backup and try
On 2019/10/1 下午12:08, Andrey Ivanov wrote:
> On 30.09.2019 9:27, Qu Wenruo wrote:
>> I recommend to do a "btrfs check" on all fses.
>
> I had done "btrfs check" on /dev/sda4:
>
> attached btrfs-check-sda4.output
>
> There are some errors. How to fix them?
It looks like "btrfs check --repair"
On 30.09.2019 10:31, Qu Wenruo wrote:
Please provide the following dump:
# btrfs ins dump-tree -b 855738744832 /dev/sdc1
attached btrfs-ins-dump-tree-855738744832-sdc1.output
OK, tree-checker is again detecting the problem correctly.
item 19 key (613039370240 EXTENT_ITEM 1048576) it
On 30.09.2019 9:27, Qu Wenruo wrote:
I recommend to do a "btrfs check" on all fses.
I had done "btrfs check" on /dev/sda4:
attached btrfs-check-sda4.output
There are some errors. How to fix them?
[1/7] checking root items
[2/7] checking extents
incorrect local backref count on 1533538304 root
On 30.09.2019 15:27, Qu Wenruo wrote:
We have another report internally about a similar corruption (multiple
bit flips in a single fs), and they are also using VMware, along with
VMware guest kernel modules.
Would you mind to migrate to KVM based hypervisor to see if the
corruption happens again
On 2019/9/30 下午8:10, Andrey Ivanov wrote:
>>
>> We have another report internally about a similar corruption (multiple
>> bit flips in a single fs), and they are also using VMware, along with
>> VMware guest kernel modules.
>>
>> Would you mind to migrate to KVM based hypervisor to see if the
>>
We have another report internally about a similar corruption (multiple
bit flips in a single fs), and they are also using VMware, along with
VMware guest kernel modules.
Would you mind to migrate to KVM based hypervisor to see if the
corruption happens again?
I had this problem with btrfs afte
On 2019/9/30 下午6:57, Qu Wenruo wrote:
>
>
> On 2019/9/30 下午6:23, Andrey Ivanov wrote:
>> On 30.09.2019 13:10, Qu Wenruo wrote:
I had built and run it:
# /home/andrey/devel/src/btrfs/btrfs-progs-dirty_fix/btrfs-corrupt-block
-X /dev/sdc1
incorrect offsets 15223 15287
>>>
On 2019/9/30 下午6:23, Andrey Ivanov wrote:
> On 30.09.2019 13:10, Qu Wenruo wrote:
>>> I had built and run it:
>>>
>>> # /home/andrey/devel/src/btrfs/btrfs-progs-dirty_fix/btrfs-corrupt-block
>>> -X /dev/sdc1
>>> incorrect offsets 15223 15287
>>> Open ctree failed
>>
>> That branch updated to skip
On 9/30/19 12:23 PM, Andrey Ivanov wrote:
>
> # /home/andrey/devel/src/btrfs/btrfs-progs-dirty_fix/btrfs-corrupt-block -X
> /dev/sdc1
> key (613019873280 EXTENT_ITEM 1048576)slot end outside of leaf 1073755934 >
> 16283
> Open ctree failed
>
> [...]
bin(1073755934)
'0b1110111000
On 30.09.2019 13:10, Qu Wenruo wrote:
I had built and run it:
# /home/andrey/devel/src/btrfs/btrfs-progs-dirty_fix/btrfs-corrupt-block
-X /dev/sdc1
incorrect offsets 15223 15287
Open ctree failed
That branch updated to skip the item offset check completely.
But please keep in mind that, that
On 2019/9/30 下午6:01, Andrey Ivanov wrote:
> On 30.09.2019 11:59, Qu Wenruo wrote:
Please prepare an environment to compile btrfs-progs (at least
btrfs-corrupt-block) if you want to try.
>>>
>>> Great, I'm ready to do it. Environment is ready.
>>
>> Here it is.
>>
>> https://github.com/a
On 30.09.2019 11:59, Qu Wenruo wrote:
Please prepare an environment to compile btrfs-progs (at least
btrfs-corrupt-block) if you want to try.
Great, I'm ready to do it. Environment is ready.
Here it is.
https://github.com/adam900710/btrfs-progs/tree/dirty_fix
To use it:
$ ./btrfs-corrupt-b
On 2019/9/30 下午4:00, Andrey Ivanov wrote:
> On 30.09.2019 10:31, Qu Wenruo wrote:
>> For this one, I could help you by just reverting that bit, and then you
>> may be able to continue mounting the fs or at least run btrfs check on
>> it.
>>
>> Please prepare an environment to compile btrfs-progs
On 2019/9/30 下午4:00, Andrey Ivanov wrote:
> On 30.09.2019 10:31, Qu Wenruo wrote:
>> For this one, I could help you by just reverting that bit, and then you
>> may be able to continue mounting the fs or at least run btrfs check on
>> it.
>>
>> Please prepare an environment to compile btrfs-progs
On 30.09.2019 10:31, Qu Wenruo wrote:
For this one, I could help you by just reverting that bit, and then you
may be able to continue mounting the fs or at least run btrfs check on it.
Please prepare an environment to compile btrfs-progs (at least
btrfs-corrupt-block) if you want to try.
Great
On 2019/9/30 下午2:58, Andrey Ivanov wrote:
> On 30.09.2019 9:27, Qu Wenruo wrote:
>>> This is the kernel message for /dev/sda4. It is also have some problems,
>>> but it is successfully mounted. I can't mount /dev/sdc1.
>>>
>>> Kernel message for /dev/sdc1:
>>> [ 6.503265] BTRFS info (device sd
On 30.09.2019 9:27, Qu Wenruo wrote:
This is the kernel message for /dev/sda4. It is also have some problems,
but it is successfully mounted. I can't mount /dev/sdc1.
Kernel message for /dev/sdc1:
[ 6.503265] BTRFS info (device sdc1): disk space caching is enabled
[ 6.503266] BTRFS info (d
On 2019/9/30 下午2:14, Andrey Ivanov wrote:
> On 30.09.2019 7:53, Qu Wenruo wrote:
>> [[PROBLEM]]
>> It's invalid DIR_ITEM, as the dmesg shows:
>>
>> [ 49.479561] BTRFS critical (device sda4): corrupt leaf: root=5
>> block=134079905792 slot=0 ino=843063, dir item with invalid data len,
>> have 25
On 2019/9/30 上午11:44, Andrey Ivanov wrote:
>
> During work I had experienced problems with access to files on the btfs
> partition.
> I rebooted the computer and after that the partition did not mount.
>
> # mount /dev/sdc1 /data
> mount: /data: wrong fs type, bad option, bad superblock on /dev
During work I had experienced problems with access to files on the btfs
partition.
I rebooted the computer and after that the partition did not mount.
# mount /dev/sdc1 /data
mount: /data: wrong fs type, bad option, bad superblock on /dev/sdc1, missing
codepage or helper program, or other erro
26 matches
Mail list logo
