Re: reboot with fsck and bad block check
- To: firstname.lastname@example.org
- Subject: Re: reboot with fsck and bad block check
- From: Seeker5528 <email@example.com>
- Date: Tue, 4 Oct 2005 19:53:54 -0700
- Message-id: <20051004195354.52ee5d02@localhost>
- In-reply-to: <20051001100415.GK3017@kan>
- References: <4334AE5D.firstname.lastname@example.org> <email@example.com> <43361A30.firstname.lastname@example.org> <20050927030715.3f7f0887@localhost> <20051001100415.GK3017@kan>
On Sat, 1 Oct 2005 22:04:15 +1200
Chris Bannister <email@example.com> wrote:
> > I see that the badblocks man page has a big fat warning:
> > This can be overridden using the -f
> > flag, but should almost never be used --- if you think you're smarter
> > than the badblocks program, you almost certainly aren't.
> I'm sorry, I'll read that again. Um it *is* in the man page!
Fsck.ext3 and fsck.ext2 are file system specific and have the -c option
to check for bad blocks, but these are not called directly by the init
scripts during the boot process.
Fsck is called during boot up, which hands off the workload to the
file system specific variants as needed and the man page only lists a
subset of the file system specific options, no -c option.
If you type fsck --help at the command line, it shows you the fsck.ext3
options that show on the fsck.ext3 man page not the generic subset
that shows on the fsck man page.
If it did accept the -c option it would be less of a hack job to get it
to be used, but I think it would still take hacking on the init scripts.