Hylton Conacher (ZR1HPC) wrote:
Carlos E. R. wrote:
The Saturday 2004-10-09 at 21:17 +0200, Hylton Conacher (ZR1HPC) wrote:
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.
Yes. man fsck.ext3 will tell you how.
I can hear Pat saying I should read the fine MANual on how to fish. :) Putting my best eye forward I READ and re-read the man page.
I see that bad blocks are checked with th -c option, but I am confused as to what the file descriptor (|^^|below) for the -C option should be.
I have decided that the command should be: #>e2fsck -pcfv -C fd <device> |^^|
Moving forward, I know I cannot fsck a mounted fs so how do I get the above to run before the fs are mounted. I have read that /etc/init.d/ is a good place but reading the man page, and searching through the directory, I see many text editable script files that I could add the above into.
Which script should I add it into so that it gets processed in the right place on system boot up?
-- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================
The Saturday 2004-10-16 at 21:48 +0200, Hylton Conacher (ZR1HPC) wrote:
Yes, but does fsck.ext3 check for bad blocks as that is what I am trying to get done here.
Yes. man fsck.ext3 will tell you how.
I can hear Pat saying I should read the fine MANual on how to fish. :) Putting my best eye forward I READ and re-read the man page.
I see that bad blocks are checked with th -c option, but I am confused as to what the file descriptor (|^^|below) for the -C option should be.
I have decided that the command should be: #>e2fsck -pcfv -C fd <device> |^^|
Ah. That is not a file, but a kind of handle so that the program that called e2fsck can "intercept" the output of e2fsck itself, and display it in a cute progress window. That's not for you.
Moving forward, I know I cannot fsck a mounted fs so how do I get the above to run before the fs are mounted. I have read that /etc/init.d/ is a good place but reading the man page, and searching through the directory, I see many text editable script files that I could add the above into.
Which script should I add it into so that it gets processed in the right place on system boot up?
No... I would leave that alone. If you want to check for badblocks with that command, you have to see the result in screen yourself, manually. The fs is checked here: /etc/init.d/boot.rootfsck /etc/init.d/boot.localfs ******* Then, a word: no matter how many times you check for bad blocks can help you prevent a hard disk crash. SMART may help sometimes, and then, it might not. If you are worried, design a proper backup procedure, use RAID arrays. ****** -- Cheers, Carlos Robinson
******* Then, a word: no matter how many times you check for bad blocks can help you prevent a hard disk crash. SMART may help sometimes, and then, it might not. If you are worried, design a proper backup procedure, use RAID arrays. ******
The new file system in Solaris 10 actually checksums each file then compares the checksums on each mirrored disk making any repairs as you go. http://wwws.sun.com/software/solaris/10/ds/zfs.jsp I downloaded and installed the preview and overall I like SuSE 9.1 better, but that ZFS is really interesting stuff. I wonder if there are any open source file systems like that? Jeff
The Monday 2004-10-18 at 18:10 -0400, Jeffrey Laramie wrote:
******* Then, a word: no matter how many times you check for bad blocks can help you prevent a hard disk crash. SMART may help sometimes, and then, it might not. If you are worried, design a proper backup procedure, use RAID arrays. ******
The new file system in Solaris 10 actually checksums each file then compares the checksums on each mirrored disk making any repairs as you go.
Mmm... interesting. A mirror fs may use two strategies: read the file from any of the drives (and thus speed up read operations), or read all copies and compare them. I think Linux sftware raid does the former, but I'm not sure. Having checksums allows that read check to be done without really reading every file twice or thrice. Interesting.
http://wwws.sun.com/software/solaris/10/ds/zfs.jsp
I downloaded and installed the preview and overall I like SuSE 9.1 better, but that ZFS is really interesting stuff. I wonder if there are any open source file systems like that?
I don't know. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The Saturday 2004-10-16 at 21:48 +0200, Hylton Conacher (ZR1HPC) wrote:
I see that bad blocks are checked with th -c option, but I am confused as to what the file descriptor (|^^|below) for the -C option should be.
I have decided that the command should be: #>e2fsck -pcfv -C fd <device> |^^|
Ah. That is not a file, but a kind of handle so that the program that called e2fsck can "intercept" the output of e2fsck itself, and display it in a cute progress window. That's not for you. Sorry, assumption of the meanings of fd in the above. I assumed it stood for 'file descriptor' but really just want to know what value I can insert into it? Why can this GUI 'junkie' not have a fancy bar going across my CLI screen? :(
Moving forward, I know I cannot fsck a mounted fs so how do I get the above to run before the fs are mounted. I have read that /etc/init.d/ is a good place but reading the man page, and searching through the directory, I see many text editable script files that I could add the above into.
Which script should I add it into so that it gets processed in the right place on system boot up?
No... I would leave that alone. If you want to check for badblocks with that command, you have to see the result in screen yourself, manually. OK, idea of running e2fsck automatically dropped, for the moment. :)
******* Then, a word: no matter how many times you check for bad blocks can help you prevent a hard disk crash. SMART may help sometimes, and then, it might not. If you are worried, design a proper backup procedure, use RAID arrays. ****** That's what I was afraid of, RAID and their cost and and and. I was hoping to get a similar, if not slightly degraded, version of using RAID but by using SMART and e2fsck.
-- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================
participants (3)
-
Carlos E. R. -
Hylton Conacher (ZR1HPC) -
Jeffrey Laramie