On 2016/4/22 11:17, Gang He wrote:
>
>
>
>> Hi Gang,
>>
>> On 2016/4/21 17:50, Gang He wrote:
>>>
>>>
>>>
>>
Hi Gang,
May be. If so, it seems that it has relations with locks.
Can we know which data is newer?
>>> Hi Joseph, I do not get your question.
>>> About this
>>>
> Hi Gang,
>
> On 2016/4/21 17:50, Gang He wrote:
>>
>>
>>
>
>>> Hi Gang,
>>> May be. If so, it seems that it has relations with locks.
>>> Can we know which data is newer?
>> Hi Joseph, I do not get your question.
>> About this bug, the customer only have a panic message, no
Hi Gang,
On 2016/4/21 17:50, Gang He wrote:
>
>
>
>> Hi Gang,
>> May be. If so, it seems that it has relations with locks.
>> Can we know which data is newer?
> Hi Joseph, I do not get your question.
> About this bug, the customer only have a panic message, no message/kernel
> dump is
>>>
> Hi Gang,
> May be. If so, it seems that it has relations with locks.
> Can we know which data is newer?
Hi Joseph, I do not get your question.
About this bug, the customer only have a panic message, no message/kernel dump
is provided.
Thanks
Gang
>
> Thanks,
> Joseph
>
> On
Hi Gang,
May be. If so, it seems that it has relations with locks.
Can we know which data is newer?
Thanks,
Joseph
On 2016/4/21 15:59, Gang He wrote:
> Hello Guys,
>
> Sorry for delayed reply, the fsck log was reported from the customer.
> OCFS2 volumes to check are:
> /dev/dm-11
Hello Guys,
Sorry for delayed reply, the fsck log was reported from the customer.
OCFS2 volumes to check are:
/dev/dm-11 83886080 44540260 39345820 54% /sapmnt
/dev/dm-14 62914560 15374960 47539600 25% /usr/sap
/dev/dm-13
Hello Joseph and Junxiao,
Unfortunately, there were not any kernel dump/message/fsck report, just
happened twice at the customer environment.
The customer kept the last log as below, the customer used SLES11SP3 for x86_64
(3.0.x-xx).
Thanks
Gang
>>>
> Hi Gang,
> I haven't found any related
Hi Gang,
I haven't found any related information about this BUG.
Which kernel version are you using? It seems inode size mismatch between
disk and memory, so any further log about these?
Thanks,
Joseph
On 2016/3/31 10:56, Gang He wrote:
> Hello Joseph and Junxiao,
>
> Did you encounter this
On 03/31/2016 10:56 AM, Gang He wrote:
> Hello Joseph and Junxiao,
>
> Did you encounter this issue in the past? I doubt this is possible a race
> condition bug (rather than data inconsistency).
Never saw this. fsck report any corruption?
Thanks,
Junxiao.
>
> Thanks
> Gang
>
>
>> Hello
Hello Joseph and Junxiao,
Did you encounter this issue in the past? I doubt this is possible a race
condition bug (rather than data inconsistency).
Thanks
Gang
>>>
> Hello Guys,
>
> I got a bug, which reported a kernel BUG in function ocfs2_truncate_file,
> Base on my initial analysis, this
Hello Guys,
I got a bug, which reported a kernel BUG in function ocfs2_truncate_file,
Base on my initial analysis, this bug looks like a race condition problem.
Unfortunately, there was no kernel crash dump caught, just got some kernel log
as below,
kernel BUG at
11 matches
Mail list logo
