From nobody Mon Jun 05 09:17:46 2023 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QZSgZ20Jrz4Z1W4 for ; Mon, 5 Jun 2023 09:17:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QZSgZ0xw3z48rc for ; Mon, 5 Jun 2023 09:17:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685956666; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=HuV5xil0ojNSsGZk4AwQnjAYSJgDzCYrj2wr866BQKo=; b=GQuyWffoPejzDT8T80aG3jQVtWfVBngv8ZVmmdnQ71Nb0ok+1o9PjUE99x54YvBrcDlwwl wbswTuO4sCMi9b6bM2VXkiijKkXDahW1IugtJJqY8D1nkQY7BBm30/JBLjr+/8eCGYOPBl d9SPnZqDtB/wjvWn/nyTQtHCUSjNrlPlUFqt/6xfDhwuL84IEaXpxrHWAhSur2XDEbKHqI 5uqmZkFJN71cZvfHFYy5odU4Aw9upbYn6wUD6HsYaKs87g84K03f21b+IHxfKOve7R3Cg6 6hpqqB+L+xW+GcQ2h92aO7aCAsaODFdrRGwVxO96cv0s18SIq2jGnczVUu9xlQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685956666; a=rsa-sha256; cv=none; b=Wd32yXJUzR6QDcojelmMO/yBMGfmt/FXRZSHsCQVJtNpOlxOXUXYLu11YvX2qSaesPp63Z XOi4mQLW25qsPa+Q+ADwcC7Dhp1ozazCsQUmOc0DQfznpBG8B17BfwyFSQupm++nEg2veB 9vv66ahkeaZBeP/xXAhajKpFTE99lQ31N9wRsjmikkABLGeT4zQITxNN4PLp72mSpTSSZS wEysHzB8yM6TT0q+KmIYfiUZtE3ut03OrvJtL68KjGem92MPpQ4t2wiyUre4W2ZsXjt3Vl 6M2RqauiHb5SDZJOSJaB0RSt3rYS0rC6RxacxntDd4JrxhEWGeCSzNjYu8LiAQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4QZSgZ02Ftzhp4 for ; Mon, 5 Jun 2023 09:17:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 3559Hjd6056727 for ; Mon, 5 Jun 2023 09:17:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3559HjQH056726 for bugs@FreeBSD.org; Mon, 5 Jun 2023 09:17:45 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 271835] seeing inode issues/ file corruption in freeBSD13 on long run Date: Mon, 05 Jun 2023 09:17:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: meetshamsher@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271835 Bug ID: 271835 Summary: seeing inode issues/ file corruption in freeBSD13 on long run Product: Base System Version: 13.1-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: meetshamsher@gmail.com Hi, Looks like file inode is getting corrupted on writing multiple times on one= of the files. Initially writing in same folder (incoming) as outbox is working fine but in long run (~20-30days) observing file corruption issues for same folder/file. Note : for this we are using haystack with luecene database, which uses this folder. Post reboot it runs fsck and then it becomes fine. 3727 Jun 2 13:15:19 sma1 kernel: ** Processing journal entries. 3728 Jun 2 13:15:19 sma1 kernel: /dev/da0p9: ino 2620925 nlink manipulation error, new 18446744073709551600, old 0 3729 Jun 2 13:15:19 sma1 kernel: /dev/da0p9: UNEXPECTED SU+J INCONSISTENCY 3730 Jun 2 13:15:19 sma1 kernel: /dev/da0p9: INTERNAL ERROR: GOT TO reply() 3731 Jun 2 13:15:19 sma1 kernel: /dev/da0p9: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. 3732 Jun 2 13:15:19 sma1 kernel: ** /dev/da0p9 3733 Jun 2 13:15:19 sma1 kernel: ** SU+J Recovering /dev/da0p9 OR Jun 3 05:36:21 sma1 kernel: Jun 3 05:36:21 sma1 kernel: DIR I=3D885977 CONNECTED. PARENT WAS I=3D22664= 82 Jun 3 05:36:21 sma1 kernel: Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: DIR I=3D359730 CONNECTED. PARENT WAS I=3D22664= 82 Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: UNREF DIR I=3D351356 OWNER=3Droot MODE=3D407= 55 Jun 3 05:36:21 sma1 kernel: SIZE=3D512 MTIME=3DMay 25 08:48 2023 Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: RECONNECT? yes Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: DIR I=3D351356 CONNECTED. PARENT WAS I=3D22664= 82 Jun 3 05:36:21 sma1 kernel: Jun 3 05:36:21 sma1 kernel: UNREF DIR I=3D349918 OWNER=3Droot MODE=3D407= 55 Jun 3 05:36:21 sma1 kernel: SIZE=3D512 MTIME=3DMay 25 08:48 2023 Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: RECONNECT? yes Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: DIR I=3D349918 CONNECTED. PARENT WAS I=3D22664= 82 Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: ** Phase 4 - Check Reference Counts Jun 3 05:36:21 sma1 kernel: LINK COUNT FILE I=3D350699 OWNER=3Droot MODE= =3D100644 Jun 3 05:36:21 sma1 kernel: SIZE=3D254 MTIME=3DJan 13 11:18 2022 COUNT 16= SHOULD BE 12 Jun 3 05:36:21 sma1 kernel: ADJUST? yes Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: LINK COUNT FILE I=3D351284 OWNER=3Droot MODE= =3D100644 Jun 3 05:36:21 sma1 kernel: SIZE=3D1205 MTIME=3DJan 13 11:18 2022 COUNT 1= 6 SHOULD BE 12 Jun 3 05:36:21 sma1 kernel: ADJUST? yes Jun 3 05:36:21 sma1 kernel: Jun 3 05:36:21 sma1 kernel: LINK COUNT DIR I=3D2266482 OWNER=3Droot MODE= =3D40755 Jun 3 05:36:21 sma1 kernel: SIZE=3D512 MTIME=3DMay 25 08:48 2023 COUNT 18= SHOULD BE 2 Jun 3 05:36:21 sma1 kernel: ADJUST? yes Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: ** Phase 5 - Check Cyl groups Jun 3 05:36:21 sma1 kernel: FREE BLK COUNT(S) WRONG IN SUPERBLK Jun 3 05:36:21 sma1 kernel: SALVAGE? yes Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: BLK(S) MISSING IN BIT MAPS Jun 3 05:36:21 sma1 kernel: SALVAGE? yes Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: 209770 files, 591288 used, 3041595 free (0 fra= gs, 3041595 blocks, 0.0% fragmentation) Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: ***** FILE SYSTEM STILL DIRTY ***** Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: ***** FILE SYSTEM WAS MODIFIED ***** Jun 3 05:36:21 sma1 kernel:=20 Jun 3 05:36:21 sma1 kernel: ***** PLEASE RERUN FSCK ***** Jun 3 05:36:21 sma1 kernel: mount: /dev/da0p9: R/W mount of /data denied. Filesystem is not clean - run fsck. Forced mount will invalidate journal contents: Operation not permitted Jun 3 05:36:21 sma1 kernel: da0 recovering is not needed Jun 3 05:36:21 sma1 kernel: da0p9 resized # find / -inum 2266482 /data/aggregator/incoming_queue/0/1minute/42145427B09C8E182260-02F017004D1B Is there way to resolve it without rebooting the system? or is there any pa= tch available for this fix in FreeBSD13.0 --=20 You are receiving this mail because: You are the assignee for the bug.=