Op 20-10-2019 om 16:24 schreef Ferry Toth:
Op 20-10-2019 om 16:11 schreef Qu Wenruo:
On 2019/10/20 下午9:29, Ferry Toth wrote:
Op 20-10-2019 om 15:15 schreef Qu WenRuo:
On 2019/10/20 下午9:04, Ferry Toth wrote:
Op 20-10-2019 om 02:51 schreef Qu Wenruo:
On 2019/10/20 上午8:26, Qu Wenruo wr
Op 20-10-2019 om 16:11 schreef Qu Wenruo:
On 2019/10/20 下午9:29, Ferry Toth wrote:
Op 20-10-2019 om 15:15 schreef Qu WenRuo:
On 2019/10/20 下午9:04, Ferry Toth wrote:
Op 20-10-2019 om 02:51 schreef Qu Wenruo:
On 2019/10/20 上午8:26, Qu Wenruo wrote:
On 2019/10/20 上午12:24, Ferry Toth wrote
On 2019/10/20 下午9:29, Ferry Toth wrote:
> Op 20-10-2019 om 15:15 schreef Qu WenRuo:
>>
>>
>> On 2019/10/20 下午9:04, Ferry Toth wrote:
>>> Op 20-10-2019 om 02:51 schreef Qu Wenruo:
On 2019/10/20 上午8:26, Qu Wenruo wrote:
>
>
> On 2019/10/20 上午12:24, Ferry Toth wrote:
>
Op 20-10-2019 om 15:15 schreef Qu WenRuo:
On 2019/10/20 下午9:04, Ferry Toth wrote:
Op 20-10-2019 om 02:51 schreef Qu Wenruo:
On 2019/10/20 上午8:26, Qu Wenruo wrote:
On 2019/10/20 上午12:24, Ferry Toth wrote:
Hi,
Op 19-10-2019 om 01:50 schreef Qu WenRuo:
On 2019/10/19 上午4:32, Ferry Toth
On 2019/10/20 下午9:04, Ferry Toth wrote:
> Op 20-10-2019 om 02:51 schreef Qu Wenruo:
>>
>>
>> On 2019/10/20 上午8:26, Qu Wenruo wrote:
>>>
>>>
>>> On 2019/10/20 上午12:24, Ferry Toth wrote:
Hi,
Op 19-10-2019 om 01:50 schreef Qu WenRuo:
>
>
> On 2019/10/19 上午4:32, Ferry Toth
Op 20-10-2019 om 02:51 schreef Qu Wenruo:
On 2019/10/20 上午8:26, Qu Wenruo wrote:
On 2019/10/20 上午12:24, Ferry Toth wrote:
Hi,
Op 19-10-2019 om 01:50 schreef Qu WenRuo:
On 2019/10/19 上午4:32, Ferry Toth wrote:
Op 24-09-2019 om 10:11 schreef Qu Wenruo:
We have at least two user reports a
Op 20-10-2019 om 02:26 schreef Qu Wenruo:
On 2019/10/20 上午12:24, Ferry Toth wrote:
Hi,
Op 19-10-2019 om 01:50 schreef Qu WenRuo:
On 2019/10/19 上午4:32, Ferry Toth wrote:
Op 24-09-2019 om 10:11 schreef Qu Wenruo:
We have at least two user reports about bad inode generation makes
kernel rej
On 2019/10/20 上午8:26, Qu Wenruo wrote:
>
>
> On 2019/10/20 上午12:24, Ferry Toth wrote:
>> Hi,
>>
>> Op 19-10-2019 om 01:50 schreef Qu WenRuo:
>>>
>>>
>>> On 2019/10/19 上午4:32, Ferry Toth wrote:
Op 24-09-2019 om 10:11 schreef Qu Wenruo:
> We have at least two user reports about bad inode
On 2019/10/20 上午12:24, Ferry Toth wrote:
> Hi,
>
> Op 19-10-2019 om 01:50 schreef Qu WenRuo:
>>
>>
>> On 2019/10/19 上午4:32, Ferry Toth wrote:
>>> Op 24-09-2019 om 10:11 schreef Qu Wenruo:
We have at least two user reports about bad inode generation makes
kernel reject the fs.
>>>
>>> M
Hi,
Op 19-10-2019 om 01:50 schreef Qu WenRuo:
On 2019/10/19 上午4:32, Ferry Toth wrote:
Op 24-09-2019 om 10:11 schreef Qu Wenruo:
We have at least two user reports about bad inode generation makes
kernel reject the fs.
May I add my report? I just upgraded Ubuntu from 19.04 -> 19.10 so
kernel
On 2019/10/19 上午4:32, Ferry Toth wrote:
> Op 24-09-2019 om 10:11 schreef Qu Wenruo:
>> We have at least two user reports about bad inode generation makes
>> kernel reject the fs.
>
> May I add my report? I just upgraded Ubuntu from 19.04 -> 19.10 so
> kernel went from 5.0 -> 5.3 (but I was using
Op 24-09-2019 om 10:11 schreef Qu Wenruo:
We have at least two user reports about bad inode generation makes
kernel reject the fs.
May I add my report? I just upgraded Ubuntu from 19.04 -> 19.10 so
kernel went from 5.0 -> 5.3 (but I was using 4.15 too).
Booting 5.3 leaves me in initramfs as
We have at least two user reports about bad inode generation makes
kernel reject the fs.
According to the creation time, the inode is created by some 2014
kernel.
And the generation member of INODE_ITEM is not updated (unlike the
transid member) so the error persists until latest tree-checker dete
13 matches
Mail list logo