Date: Sat, 22 Nov 2014 08:14:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195278] New: gjournal UFS: svn update /usr/ports panics with corrupt directory emulators/aqemu/files missing `.' and `..' Message-ID: <bug-195278-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195278 Bug ID: 195278 Summary: gjournal UFS: svn update /usr/ports panics with corrupt directory emulators/aqemu/files missing `.' and `..' Product: Base System Version: 10.1-RELEASE Hardware: i386 OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: kennethsalerno@yahoo.com x86, 1 GB RAM. Issue in 10.0-RELEASE and 10.1-RELEASE. GEOM_JOURNAL UFS2 mount options for file system containing /usr/ports: rw,noatime,async,gjournal Whenever I run "svn update /usr/ports" a kernel panic ensues from UFS corruption, when the system boots, GEOM_JOURNAL thinks everything is peachy, mounts FS consistent even though there is a corruption. If I hit that corrupt dir with "svn update /usr/ports" system panics again. An "fsck -fy /" fails to fix the issue automatically (bad block cannot be written) so I am always forced to go into "fsdb /dev/label/rootfs", "findblk BLOCK", "inode INODE", "clri INODE", "q", "fsck -fy /" to fix the issue. I really want to use "svn" instead of "portsnap" but this repeatable FS corruption issue is preventing me from doing so. -- 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-195278-8>