On 2018年04月17日 22:32, Anand Jain wrote:
>
>
> On 04/17/2018 05:58 PM, Qu Wenruo wrote:
>>
>>
>> On 2018年04月17日 17:05, Anand Jain wrote:
>>>
v3:
Update commit message to show the corruption in details.
Modify the kernel error message to show corruption is detected
On 04/17/2018 05:58 PM, Qu Wenruo wrote:
On 2018年04月17日 17:05, Anand Jain wrote:
v3:
Update commit message to show the corruption in details.
Modify the kernel error message to show corruption is detected before
transaction commitment.
Nice. Thanks. more below.
@@ -3310,6
On 2018年04月17日 17:05, Anand Jain wrote:
>
>> v3:
>> Update commit message to show the corruption in details.
>> Modify the kernel error message to show corruption is detected before
>> transaction commitment.
> Nice. Thanks. more below.
>
>> @@ -3310,6 +3311,27 @@ static int
v3:
Update commit message to show the corruption in details.
Modify the kernel error message to show corruption is detected before
transaction commitment.
Nice. Thanks. more below.
@@ -3310,6 +3311,27 @@ static int write_dev_supers(struct btrfs_device *device,
There are already 2 reports about strangely corrupted super blocks,
where csum still matches but extra garbage gets slipped into super block.
The corruption would looks like:
--
superblock: bytenr=65536, device=/dev/sdc1
-
csum_type
On Mon, Apr 16, 2018 at 09:00:38PM +0800, Qu Wenruo wrote:
>
>
> On 2018年04月16日 20:55, Anand Jain wrote:
> >
> >
> > On 04/16/2018 10:02 AM, Qu Wenruo wrote:
> >> There are already 2 reports about strangely corrupted super blocks,
> >> where csum type and incompat flags get some obvious
On Mon, Apr 16, 2018 at 10:02:27AM +0800, Qu Wenruo wrote:
> There are already 2 reports about strangely corrupted super blocks,
> where csum type and incompat flags get some obvious garbage, but csum
> still matches and all other vitals are correct.
>
> This normally means some kernel memory
On 2018年04月16日 20:55, Anand Jain wrote:
>
>
> On 04/16/2018 10:02 AM, Qu Wenruo wrote:
>> There are already 2 reports about strangely corrupted super blocks,
>> where csum type and incompat flags get some obvious garbage, but csum
>> still matches and all other vitals are correct.
>>
>> This
On 04/16/2018 10:02 AM, Qu Wenruo wrote:
There are already 2 reports about strangely corrupted super blocks,
where csum type and incompat flags get some obvious garbage, but csum
still matches and all other vitals are correct.
This normally means some kernel memory corruption happens,
There are already 2 reports about strangely corrupted super blocks,
where csum type and incompat flags get some obvious garbage, but csum
still matches and all other vitals are correct.
This normally means some kernel memory corruption happens, although the
cause is unknown, at least detect it
10 matches
Mail list logo
