Re: fsck: broken file system with background check remains broken after bootup

2005-01-05 Thread Michael Nottebrock
On Wednesday, 5. January 2005 04:29, Wilkinson, Alex wrote: 0n Tue, Jan 04, 2005 at 02:01:22PM +0100, Oliver Fromme wrote: By the way, you can map a key combination (Ctrl-Alt-Del or something else) to the »halt« or »power-down« functions, using kbdcontrol, so it's very easy and

Re: fsck: broken file system with background check remains broken after bootup

2005-01-05 Thread Oliver Fromme
Craig Boston [EMAIL PROTECTED] wrote: On Tuesday 04 January 2005 9:57 pm, Wilkinson, Alex wrote: How can I confirm that ACPI has been setup to do this ? Hmm, well, the easiest thing to check is to run sysctl hw.acpi.power_button_state and see if that sysctl exists and if so,

fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Rob
Hi, I had following situation: Someone suddenly cut the power of a FreeBSD 5.3 PC, leaving the /usr filesystem in a very broken state. During next bootup, there was indeed the message telling 'not properly unmounted', but boot continued with background fsck after 60 seconds; although I

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Dick Davies
* Rob [EMAIL PROTECTED] [0123 10:23]: This scared me. What if /usr was such broken that even single user mode would hang!?! That won't happen, since /usr isn't mounted in single user mode. -- 'common sense is what tells you that the world is flat.' -- Principia Discordia

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Godwin Stewart
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 4 Jan 2005 10:26:27 +, Dick Davies [EMAIL PROTECTED] wrote: That won't happen, since /usr isn't mounted in single user mode. Even if it were, there are always Live BSD CDROMs which should allow you to boot and then fsck your disk

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Rob
Godwin Stewart wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 4 Jan 2005 10:26:27 +, Dick Davies [EMAIL PROTECTED] wrote: That won't happen, since /usr isn't mounted in single user mode. Even if it were, there are always Live BSD CDROMs which should allow you to boot and then

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Boris B. Samorodov
Hi! On Tue, Jan 04, 2005 at 08:25:20PM +0900, Rob wrote: So I want to configure 5.3 similar to former 4.10: a full automatic fix of all filesystems at bootup, in case the system was not properly shutdown. How can I do that? You already mention it -- backgroung_fsck=NO at

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Ceri Davies
On Tue, Jan 04, 2005 at 08:25:20PM +0900, Rob wrote: An automatic fsck could have fixed the system (I eventually did it manually in single user mode), but the background check left the system broken. So I want to configure 5.3 similar to former 4.10: a full automatic fix of all

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Rob
Ceri Davies wrote: On Tue, Jan 04, 2005 at 08:25:20PM +0900, Rob wrote: An automatic fsck could have fixed the system (I eventually did it manually in single user mode), but the background check left the system broken. So I want to configure 5.3 similar to former 4.10: a full automatic fix

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Matthias Andree
Rob [EMAIL PROTECTED] writes: I had following situation: Someone suddenly cut the power of a FreeBSD 5.3 PC, leaving the /usr filesystem in a very broken state. During next bootup, there was indeed the message telling 'not properly unmounted', but boot continued with background fsck

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Oliver Fromme
Rob [EMAIL PROTECTED] wrote: [...] However, the main user of this particular PC is not at all a guru; on 4.10 I had rc.conf configured such that at bootup all filesystems would be automatically fixed with: fsck_y_enable=YES. With 4.10, this always worked nicely, whatever sudden power cut

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Matthias Andree
Matthias Andree [EMAIL PROTECTED] writes: OTOH, I am not convinced that fsck (particularly bgfsck) is bug-free, I Make that fsck and ufs are bug-free... -- Matthias Andree ___ freebsd-stable@freebsd.org mailing list

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Freddie Cash
On January 4, 2005 03:25 am, Rob wrote: Thanks for your replies, but apparently I didn't make my point clearly. Let me try again: If the system ends with a bad filesystem, the background check may leave the system unusable after bootup. For a FreeBSD guru this is indeed easy to fix (single

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Wilkinson, Alex
0n Tue, Jan 04, 2005 at 02:01:22PM +0100, Oliver Fromme wrote: By the way, you can map a key combination (Ctrl-Alt-Del or something else) to the »halt« or »power-down« functions, using kbdcontrol, so it's very easy and intuitive to shut down the machine properly. See the

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Craig Boston
On Wed, Jan 05, 2005 at 01:59:01PM +1030, Wilkinson, Alex wrote: This inspires me to ask this question: Is it possible to set up FreeBSD to do a clean shutdown upon a pressing the power button ? i.e. in the same fashion as Solaris does out of the box. Is this an ATX feature or a kernel

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Wilkinson, Alex
0n Tue, Jan 04, 2005 at 09:50:10PM -0600, Craig Boston wrote: Yes, in FreeBSD 5.3 if ACPI is enabled and working properly, pressing the power button will initiate a graceful shutdown (similar to shutdown -p). This feature is enabled by default if it is available, so you

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Craig Boston
On Tuesday 04 January 2005 9:57 pm, Wilkinson, Alex wrote: How can I confirm that ACPI has been setup to do this ? Hmm, well, the easiest thing to check is to run sysctl hw.acpi.power_button_state and see if that sysctl exists and if so, what it's set to (mine is S5, which IIRC is complete

Re: fsck: broken file system with background check remains broken after bootup

2005-01-04 Thread Wilkinson, Alex
0n Tue, Jan 04, 2005 at 10:17:47PM -0600, Craig Boston wrote: On Tuesday 04 January 2005 9:57 pm, Wilkinson, Alex wrote: How can I confirm that ACPI has been setup to do this ? Hmm, well, the easiest thing to check is to run sysctl hw.acpi.power_button_state