Your message dated Tue, 24 Oct 2006 18:56:18 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [Pkg-sysvinit-devel] Bug#394657: initscripts: Option for an
fsck no matter whether the machine is on AC or battery
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: initscripts
Version: 2.86.ds1-33
Severity: wishlist
Hi
IINM: after a system crash - when rebooting the machine - an fsck is
crucial for the sanity of some filesystem and the data on it.
But currently a check is skipped in such a situation, if the system
thinks the machine is running on battery.
So I'd suggest an option to force the usual fsck no matter whether the
machine is running on AC or battery -- perhaps via some setting in
/etc/default/.
If there already is some way to easily disable the fsck skip,
please let me know: At least until now I didn't find it.
Thanks in anticipation.
Best Regards
Wolfgang
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-rc4-060811-dirty
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages initscripts depends on:
ii debianut 2.17.3 Miscellaneous utilities specific t
ii e2fsprog 1.39+1.40-WIP-2006.10.02+dfsg-1 ext2 file system utilities and lib
ii libc6 2.3.6.ds1-6 GNU C Library: Shared libraries
ii lsb-base 3.1-17 Linux Standard Base 3.1 init scrip
ii mount 2.12r-11 Tools for mounting and manipulatin
ii sysvinit 2.86.ds1-33 System-V-like utilities
Versions of packages initscripts recommends:
ii psmisc 22.3-1 Utilities that use the proc filesy
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Oct 22 2006, at 23:44 -0300, Henrique de Moraes Holschuh wrote:
> On Sun, 22 Oct 2006, Wolfgang Pfeiffer wrote:
> > So I'd suggest an option to force the usual fsck no matter whether the
> > machine is running on AC or battery -- perhaps via some setting in
> > /etc/default/.
>
> Is anything wrong with the /forcefsck file?
*** 1:
/forcefsck does not seem to be documented anywhere on Debian when
searching like this:
grep -irs forcefsck /usr/share/
Nor does a "site:debian.org/doc forcefsck" yield any results on
Google.
Yes, I found a few documents on the topic, of unknown reliability,
via Google.
I believe that using sensitive software routines like filesystem
checks on a computer without really knowing what they do is stupid
like hell. To learn about these routines the reading of documentation
- if available - might help.
*** 2:
I hope we can agree that there is a crucial difference
between what I was suggesting and what you were hinting:
Issuing a
touch /forcefsck
will run a single complete check of the filesystems on the various
partitions that easily can take several minutes. On the next
reboot. After this check /forcefsck was deleted here, without my
intervention.
So with your hint you basically have the option of issuing
'touch /forcefsck' every time you have been booting the system
(because you can't do that anymore after a system crash - this is what
makes a system crash a system crash). And you'll have an
unnecessary fsck if the system was shut down cleanly: Because the
check will obviously be done no matter whether the shutdown was a
clean one or not.
Whereas I was suggesting an option to set up a check, for the time of
booting, to see whether the last shutdown was clean and, if it wasn't,
perform the check.
I think this could have been understood if one reads my email with
medium sized interest.
The next section is the most important part of this mail:
Please be fully ensured that I never write bug reports - be them
wishlist or bug items - because I didn't know anything else to with
my time.
Wolfgang
--
Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer
Key ID: E3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on
--- End Message ---
