On 07/23/2015 12:59 PM, David Wright wrote:
Quoting Ralph Katz (ralph.k...@rcn.com):
Yesterday I learned (from this list) that apparently Debian now defaults
to no periodic disk checks after file system installation. So I
manually added one yesterday.
Yet when I rebooted after today's kernel update, no check was forced on
the up-to-date jessie system.
Am I missing something,
Yes, you missed yesterday's posting:
https://lists.debian.org/debian-user/2015/07/msg00977.html
Cheers,
David.
Thank you for responding to my post in the other thread, David. For some
reason I missed seeing it. So my lack of an acknowledgment was not
caused by rudeness, just incompetence or mail gone awry. (Comcast
occasionally decides to block one or two messages from this list for no
reason that either Comcast or I can fathom.)
;-)
-- excerpting your response to me in that thread --
Like you in https://lists.debian.org/debian-user/2015/04/msg01423.html
I revisit this problem once in a while.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783410
seems to have fallen on deaf ears, so in the meantime, here's a
solution:
Reboot,
At grub's prompt type e to edit,
Add forcefsck to the end of the linux ... line,
Ctrl-X or F10 to boot.
This will fsck (just this once) all the partitions that
shutdown -t1 -a -r -F now
would do in the traditional manner in wheezy and previously.
All that's missing is any progress indication because that bit
of code in /etc/init.d/checkroot.sh didn't get copied.
--------------------end excerpt--------------------
Most of the systems on which I periodically force fsck are remote, so I
just use the tune2fs utility. I could, of course, add a line to grub
which contains forcefsck and use grub-reboot to get the same effect on
those remote systems. I'm just using tune2fs because it doesn't involve
my having to edit the grub configuration and then having to update it.
I'm mystified as to the inattention of upstream and the maintainers of
initramfs to the bug reported by Michael Biebl after he and I discussed
this matter here. (I had planned to file the bug, but Michael did so and
did it better than I would have.)
The last time I checked you still get a warning in the log if you use
"touch /forcefsck" to force an fsck. That warning tells the user (or at
least used to tell the user) to do something that did *not* result in a
file system check being forced. Has that changed?
At any rate, I'll try your suggestion on my local system next time I
want to force an fsck. I'll also try using "touch /forcefsck" again just
to see if the warning has changed.
Regards,
Jape
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55b1254f.2030...@comcast.net
