Date: Sat, 16 Mar 2002 17:57:48 -0800 (PST) From: Roy Hooper <rhooper@toybox.ca> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/35992: /etc/rc has no way to force fsck -y at next boot, corrupt filesystems with soft updates required manual intervention Message-ID: <200203170157.g2H1vms18924@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 35992 >Category: misc >Synopsis: /etc/rc has no way to force fsck -y at next boot, corrupt filesystems with soft updates required manual intervention >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: wish >Submitter-Id: current-users >Arrival-Date: Sat Mar 16 18:00:04 PST 2002 >Closed-Date: >Last-Modified: >Originator: Roy Hooper >Release: 4.5-RELEASE >Organization: >Environment: FreeBSD plumber.cyberus.ca 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Mon Jan 28 14:31:56 GMT 2002 murray@builder.freebsdmall.com:/usr/src/sys/compile/GENERIC i386 >Description: /etc/rc performs fsck -p then only fsck -y if fsck_y_enable="YES" with softupdates, I managed to end up with a corrupt filesytem (in /usr/lib of all places!) causing the following kinds of error messages: Mar 13 01:17:16 plumber /kernel: dscheck(#ad/0x20006): negative b_blkno -300154849 /usr/lib/compat/aout/libalias.so.2.4: Bad file descriptor >How-To-Repeat: Actually corrupt your FFS filesystem with softupdates (somehow). I think the combination of multiple hard poweroffs during compiles should do the trick. >Fix: The solution was to force a fsck -y at boot time by modifying /etc/rc so that I could remotely reboot the machine. Adding the ability to touch a temporary file such as /force-fsck-y would be very useful for remote maintenance. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203170157.g2H1vms18924>