Date: Sun, 13 Apr 2014 16:03:26 +0400 From: Dmitry Sivachenko <trtrmitya@gmail.com> To: lev@FreeBSD.org Cc: freebsd-fs@FreeBSD.org, pfg@FreeBSD.org, freebsd-stable@freebsd.org, mckusick@FreeBSD.org Subject: Re: UFS2 SU+J could not recover after power-off sgain (was: One process which would not die force me to power-cycle server and ALL UFS SUJ FSes are completely broken after that AGAIN!) Message-ID: <8A3243EF-90D0-428A-99C1-8360DB402B86@gmail.com> In-Reply-To: <482103242.20140413141010@serebryakov.spb.ru> References: <981154629.20140412170953@serebryakov.spb.ru> <482103242.20140413141010@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Turn off journaling, it has many issues reported. I run hundreds of servers at work with UFS2+SU (w/o J), and never had a single problem. On 13 апр. 2014 г., at 14:10, Lev Serebryakov <lev@FreeBSD.org> wrote: > Hello, Freebsd-fs. > You wrote 12 апреля 2014 г., 17:09:53: > > LS> All UFS2 filesystems can not be recovered with using of automated fsck, due > LS> to journal/softupdate inconsistencies. I need to run "fsck -f" TWICE for > LS> each of them (as first run ask to re-run fsck). > "shutdown -h" reboots system, UPS switch power off after that (with delay), > 2 out of 5 FSes could not be checked with journal automatically. Manual full > "fsck" run didn't find any serious problems, only one or two unlinked files > (recovered to lost+found) free block bitmaps! > > WHY?! How could I trust to UFS2 now?! > > Both filesystems have same scenario: > > /dev/ufs/tmp: Journal file sequence mismatch 233263 != 231707 > /dev/ufs/tmp: UNEXPECTED SU+J INCONSISTENCY > /dev/ufs/tmp: INTERNAL ERROR: GOT TO reply() > /dev/ufs/tmp: UNEXPECTED SOFT UPDATE INCONSISTENCY. RUN fsck MANUALLY. > > /dev/ufs/usr: Journal file sequence mismatch 287936 != 282572 > /dev/ufs/usr: UNEXPECTED SU+J INCONSISTENCY > /dev/ufs/usr: INTERNAL ERROR: GOT TO reply() > /dev/ufs/usr: UNEXPECTED SOFT UPDATE INCONSISTENCY. RUN fsck MANUALLY. > > Again: these FSes were checked with full fsck two days ago. They reside at > SATA HDD without any non-standard or complex geom modules (only > geonm_part), and HDD is attahed to chipset SATA port, there is no any RAID > controllers or things like that. > > EVERY non-clean reboot of server leads to "RUN fsck MANUALLY". > > -- > // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org> > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8A3243EF-90D0-428A-99C1-8360DB402B86>