Date: Mon, 05 Jun 2023 09:17:46 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 271835] seeing inode issues/ file corruption in freeBSD13 on long run Message-ID: <bug-271835-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271835-227>