Carlos E. R. wrote:
El 2004-10-01 a las 18:54 +0200, Hylton Conacher (ZR1HPC) escribió:
(you forgot to email to the list) Tnx I keep forgetting as it is not the same as the many other lists I am on, Tnx.
You do not need that. You only have to tune your partitions so that they "want" to be fsck-ed oftener.
Th st I did, but reading the fsck man page I see there is no option to check for bad blocks, unlike e2fsck which does have tis option. I initially thought along the lines of an alias for fsck as e2fsck but realised that it could be more problematic.
fsck does in fact pass options to fsck.ext3 Yes, but does fsck.ext3 check for bad blocks as that is what I am trying to get done here.
Remember that suse scripts boot.rootfsck and boot.localfs check the filesystem when required.
I did remember that fsck will fsck the system when required, but wanted additional safety nets.
Also, creating the file "/forcefsck" will force fsck of all partitions on every boot.
It doesn't need to be on every boot, but rather on a weekly or even daily basis, no matter how many times the machine is rebooted.
Well, you can create that file weekly using a cron job, then delete it after boot.
# e2fsck -pcfv </device>| > /home/hylton/e2fsckresult
Remember that you can not check a mounted partition, so above you can not check home.
mmm, I saw that oops as I sent it. The reason for putting the location in is that I do not know where to put system admin stuff. In retrospect I would probably have the result mailed to a user.
It doesn't matter, you can not email or save it at that time, because the filesystem is mounted read-only at the time of checking - unless you are checking manually some other partition. You have to "see" it, or invent some way to keep it memory and save later, kind of what SuSE does with the kernel booting messages.
I know an ext3 fs is 'safe' but it is not the fs I am worried about but the hardware deteriorating. Call me paranoid but rather safer than sorrier. :)
Then, what you need is smartd instead. fsck will only tell about logical errors on the filesystem sctructure, not about the motor getting overhot, for example. SMART will, however.
mmm, I think that a more substantial backup method is needed. JIC
SMART is quite good. It can quick test your HD at the same time you are using it, any time. It can check it thoroughly, in an hour or so, also transparently. When done, you read the result. It checks many things, including read errors, hardware, interfaces, temperatures, moving parts wear, voltages... read it up (smartctl). I did a search on man and apropos of smartctl and came up with nothing. Even the SuSE help couldn't find anything in GUI mode. :(
If I remember correctly SMART is a technology implemented by the BIOS and so I shall check there too. Pat, any 'man ' comments from you :) ? -- ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================