From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 5BD11158043 for ; Mon, 15 Apr 2024 11:49:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D8DD0E29CD; Mon, 15 Apr 2024 11:48:59 +0000 (UTC) Received: from sienna.cherry.relay.mailchannels.net (sienna.cherry.relay.mailchannels.net [23.83.223.165]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2113CE29BE for ; Mon, 15 Apr 2024 11:48:58 +0000 (UTC) X-Sender-Id: thundermail|x-authsender|confabulate@kintzios.com Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id E91B3802136 for ; Mon, 15 Apr 2024 11:48:57 +0000 (UTC) ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1713181737; a=rsa-sha256; cv=none; b=Pro7glc94Gu5fXG0y2opTPUxt3NHKn463AF8MYZEphY1JGfRkLHztLS8iBpBfKy9gOVEFt X8HLcrmSX8zytT2sOCkns76njDKfNky83CqfawxZw9T4A/RCP1ev4A1mQG4gBQ4TIyQll7 SL585ZDNS/opkM4pwXcQlgwb+4wr6HJo1BImlXVjugmiOJlDGCUoEG9g3O/NjwhzccxyzD Ix7X4admZfVc0DU80D1gbRSWDGQlc/cOw+Thhvt5KjLyoHrh4DQSTxIEuP0uODmc10KlQr +nVm3YWgVY51cpXgmZh+f+CBkvOHyEXAQ9s6I4815bzme/c0TE2JIkts5/bqqw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1713181737; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=Mx0wozlKLSwEmHZA/VGUIfmtDtPzR4M1zNavg0NH4F4=; b=ixKjExqbfCZj00RG0HSepzEgWyfJj9wr8lgCWAnoBlhICDUYeZG2RwNReIjImxqPGoxHme Jl4iIgnd82H4bL2dyUr5ixas2uUlJxYOrCxRt8A3e9Epu2NGHbrJgYMoFVTONHHJj+BOpA hCrbnMs/pbCPCtF+2WFlcS/oUNZUV2Mcpca/oxMWnkz5fPWBGZQ8wOS1IwgwsiZSaV6Ls4 pJPWlxXp5AFIgaTc9P8RdDXE+Ek40CME53jemsAG7YRnJOktjYLZN0KFmPupDFc/gavlcy ckIJSNv+BGBhD5OTcdT//OZAWKf55CchWdelHC7hY1Io59xHSGFjPBNrXuIqcg== ARC-Authentication-Results: i=1; rspamd-878bcf566-rpk8k; auth=pass smtp.auth=thundermail smtp.mailfrom=confabulate@kintzios.com X-Sender-Id: thundermail|x-authsender|confabulate@kintzios.com X-MC-Relay: Neutral X-MailChannels-SenderId: thundermail|x-authsender|confabulate@kintzios.com X-MailChannels-Auth-Id: thundermail X-Vacuous-Oafish: 43969f89373096c2_1713181737558_3524895666 X-MC-Loop-Signature: 1713181737558:711663337 X-MC-Ingress-Time: 1713181737558 Received: from mailclean11.thundermail.uk (mailclean11.thundermail.uk [149.255.60.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.102.214.171 (trex/6.9.2); Mon, 15 Apr 2024 11:48:57 +0000 Received: from cloud238.thundercloud.uk (cloud238.thundercloud.uk [149.255.62.116]) by mailclean11.thundermail.uk (Postfix) with ESMTPS id 3A80B401EA for ; Mon, 15 Apr 2024 12:48:52 +0100 (BST) Authentication-Results: cloud238.thundercloud.uk; spf=pass (sender IP is 217.169.3.230) smtp.mailfrom=confabulate@kintzios.com smtp.helo=rogueboard.localnet Received-SPF: pass (cloud238.thundercloud.uk: connection is authenticated) From: Michael To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Slightly corrupted file systems when resuming from hibernation Date: Mon, 15 Apr 2024 12:48:34 +0100 Message-ID: <3619703.R56niFO833@rogueboard> In-Reply-To: <26140.9061.183864.912153@woitok.gmail.com> References: <26008.16480.838421.880615@woitok.gmail.com> <26140.9061.183864.912153@woitok.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3745967.MHq7AAxBmi"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-PPP-Message-ID: <171318173166.2049929.6994392613134948806@cloud238.thundercloud.uk> X-PPP-Vhost: kintzios.com X-Rspamd-Queue-Id: 3A80B401EA X-Rspamd-Server: mailclean11 X-Spamd-Result: default: False [-1.61 / 999.00]; SIGNED_PGP(-2.00)[]; MID_RHS_NOT_FQDN(0.50)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; ONCE_RECEIVED(0.10)[]; MX_GOOD(-0.01)[]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_ALLOW(0.00)[kintzios.com,none]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:34931, ipnet:149.255.60.0/22, country:GB]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ONE(0.00)[1]; NEURAL_HAM(-0.00)[-0.993]; R_DKIM_NA(0.00)[]; FUZZY_BLOCKED(0.00)[rspamd.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[gentoo-user@lists.gentoo.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(0.00)[+mx]; HAS_REPLYTO(0.00)[confabulate@kintzios.com] X-Rspamd-Action: no action X-Archives-Salt: 2a320233-655c-4e9c-a8e1-31934df080d9 X-Archives-Hash: 2bc247481b5de088d949d3118919432d --nextPart3745967.MHq7AAxBmi Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8"; protected-headers="v1" From: Michael To: gentoo-user@lists.gentoo.org Reply-To: confabulate@kintzios.com Date: Mon, 15 Apr 2024 12:48:34 +0100 Message-ID: <3619703.R56niFO833@rogueboard> In-Reply-To: <26140.9061.183864.912153@woitok.gmail.com> MIME-Version: 1.0 On Sunday, 14 April 2024 19:41:41 BST Dr Rainer Woitok wrote: > Greetings, > > On Friday, 2024-01-05 18:46:09 +0100, I myself wrote: > > ... > > since a few month or so off and on my laptop fails to resume from hiber- > > nation due to the "dirty bit" being set on the ext4 "/home" partition. > > I was reading this flickering by on the screen, and it wasn't quite cor- > rect. Meanwhile I found this in my "openrc.log": > > fsck.fat 4.2 (2021-01-31) > There are differences between boot sector and its backup. > This is mostly harmless. Differences: (offset:original/backup) > 65:01/00 > Not automatically fixing this. > Dirty bit is set. Fs was not properly unmounted and some data may be > corrupt. Automatically removing dirty bit. > *** Filesystem was changed *** > Writing changes. > /dev/sda1: 368 files, 116600/258078 clusters Why have you set your /boot to be mounted at boot? You can run 'fsck.fat -v /dev/sda1' after you unmount it to remove the dirty bit (if not already removed) and then change your fstab to 'noauto'. Just remember to remount /boot before you make any changes to your boot manager/ kernels. > /dev/sdb1: recovering journal > /dev/sdb1: Clearing orphaned inode 54789026 (uid=1000, gid=1000, > mode=0100600, size=32768) /dev/sdb1: Clearing orphaned inode 54788311 > (uid=1000, gid=1000, mode=0100600, size=553900) /dev/sdb1: clean, > 172662/61054976 files, 36598898/244190385 blocks * Filesystems repaired > > So one cause always is some problem on disk "/dev/sda1/" ("/boot/") and > another cause are one or more orphaned inodes on disk "/dev/sdb1/" > ("/home/"). But while the values of offset, original and backup for > "/dev/sda1/" are always the same when this happens, the number of or- > phaned inodes on "/dev/sdb1/" and the inodes itself change from occur- > rence to occurrence. Besides it only happens sporadically when resuming > from hibernation, not every time. More precisely, the problem surfaces > when resuming from hibernation but could as well be caused during the > hibernation process itself. > > Does this ring some bell somewhere what could cause this? > > Sincerely, > Rainer Unlike the /boot partition, the /home partition has data written to it regularly. The ext4 fs does not perform atomic writes - it is not a CoW fs. Therefore a sudden unsync'ed shutdown could leave it in a state of corruption - IF for some reason data in memory is not either fully written to disk or retained in memory. The way ACPI interacts with firmware *should* ensure the S3 system state does not suspend I/O operations halfway through an inline write operation ... but ... MoBo firmware can be notoriously buggy and is typically frozen/abandoned within a couple of years by the OEMs. In addition, kernel code changes and any previous symbiosis with the firmware can fall apart with a later kernel release. On one PC of mine, with the same MoBo/CPU and the same version firmware, I have over the years experienced a whole repertoire of random problems resuming from suspend. At this point in time I avoid placing this PC in sleep, because it always crashes with a Firefox related segfault, some time after waking up. Check if the situation with /dev/sdb1 improves when you leave your /boot unmounted. This may make more process time available for the system to finish I/O operations, which may then allow /dev/sdb1 to suspend cleanly. --nextPart3745967.MHq7AAxBmi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmYdFBIACgkQseqq9sKV ZxmliBAA6r8sOOKo8zBHiEOYsl9UD8ewY2v02MWBmRKDTflKZxvitLwpMuxvMPpa 7QRztpMGJdhvw1f2wkKhctQbK7yPiPN7qrqKw1wQ78VlfUuALe68Ga1WkOduRdb4 oPpT7j9QKyix2GYXtG2drCvk6o1Ch68P4SsSoniPR0vhby4SURwlQ5m0uiKId4CJ 1X/e3t1w+whrm+xyaVoxg3Ae6vtXoaWDRGdUsUSc0gh5Q7MS1nD2LruajKzul5VA 6sERSwxoXJWNYflRlfCG4iWzOSvh542ZFlOJaD7vu3/FcPK7MYrCt8tG8zow4R3q MlvQhFB2fFsm9vF0++VMdVG/nQAWlMhx2G7+hWA9bOlKfXDW/0aCcHd+jCn3P8MX XBPk/52csAvp11P3XKu03S345jGxbbi2RPbwJQxmP+Gl9HoPn1+CRW0LSbxCpUQl 3EiEysfiGmygwIrILjWuXV/LpkGzT2KMrp1n6PcNBGq6n51hiQYxGEFMEia28VW1 ot0c4h2kAgbpxkpa45ZSb3dWRmfpuklgtFFRQVX+OQLfZJWtifk0fvSPcuuePIbI AKPljJkI51cUr25vsZ386mtVaEeSwZCA2s2W6IrXJQeT8uX9xxqicNq9bsvr8PTk me70/CTcYzjdJPwE5nTHN3Lq3Bx8Oca+LKLCpf6toRdCR2giBcM= =hdzB -----END PGP SIGNATURE----- --nextPart3745967.MHq7AAxBmi--