From: Thomas Voegtle <tv@lio96.de>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Heming Zhao <heming.zhao@suse.com>, Su Yue <glass.su@suse.com>,
stable@vger.kernel.org
Subject: Re: ocfs2 broken for me in 6.6.y since 6.6.55
Date: Thu, 12 Dec 2024 11:47:24 +0100 (CET) [thread overview]
Message-ID: <2735fe61-3c53-90d2-5571-647fef41b9ea@lio96.de> (raw)
In-Reply-To: <0f122ee5-56e3-45b0-b531-455fcf9cea3c@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
On Thu, 12 Dec 2024, Joseph Qi wrote:
> See: https://lore.kernel.org/ocfs2-devel/20241205104835.18223-1-heming.zhao@suse.com/T/#t
>
> On 2024/12/12 18:32, Thomas Voegtle wrote:
>>
>> Hi,
>>
>> ocfs2 on a drbd device, writing something to it, then unmount ends up in:
>>
>>
>> [ 1135.766639] OCFS2: ERROR (device drbd0): ocfs2_block_group_clear_bits:
>> Group descriptor # 4128768 has bit count 32256 but claims 33222 are freed.
>> num_bits 996
>> [ 1135.766645] On-disk corruption discovered. Please run fsck.ocfs2 once
>> the filesystem is unmounted.
>> [ 1135.766647] (umount,10751,3):_ocfs2_free_suballoc_bits:2490 ERROR:
>> status = -30
>> [ 1135.766650] (umount,10751,3):_ocfs2_free_clusters:2573 ERROR: status =
>> -30
>> [ 1135.766652] (umount,10751,3):ocfs2_sync_local_to_main:1027 ERROR:
>> status = -30
>> [ 1135.766654] (umount,10751,3):ocfs2_sync_local_to_main:1032 ERROR:
>> status = -30
>> [ 1135.766656] (umount,10751,3):ocfs2_shutdown_local_alloc:449 ERROR:
>> status = -30
>> [ 1135.965908] ocfs2: Unmounting device (147,0) on (node 2)
>>
>>
>> This is since 6.6.55, reverting this patch helps:
>>
>> commit e7a801014726a691d4aa6e3839b3f0940ea41591
>> Author: Heming Zhao <heming.zhao@suse.com>
>> Date: Fri Jul 19 19:43:10 2024 +0800
>>
>> ocfs2: fix the la space leak when unmounting an ocfs2 volume
>>
>> commit dfe6c5692fb525e5e90cefe306ee0dffae13d35f upstream.
>>
>>
>> Linux 6.1.119 is also broken, but 6.12.4 is fine.
>>
>> I guess there is something missing?
>>
>>
>> Thomas
>
>
Ah, thanks, I didn't read that.
Thomas
next prev parent reply other threads:[~2024-12-12 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 10:32 ocfs2 broken for me in 6.6.y since 6.6.55 Thomas Voegtle
2024-12-12 10:41 ` Joseph Qi
2024-12-12 10:47 ` Thomas Voegtle [this message]
2024-12-12 10:54 ` Greg KH
2024-12-12 11:01 ` Heming Zhao
2024-12-12 11:06 ` Greg KH
2024-12-12 11:15 ` Joseph Qi
2024-12-12 11:31 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2735fe61-3c53-90d2-5571-647fef41b9ea@lio96.de \
--to=tv@lio96.de \
--cc=glass.su@suse.com \
--cc=heming.zhao@suse.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox