Carlos E. R. wrote:
The Friday 2006-01-06 at 15:33 +0200, Hylton Conacher (ZR1HPC) wrote:
Anyone?
It isn't easy... it is too vague, and the feeling is that you are too "paranoid" ;-)
As I said to Per Jessen. I know I am going to lose data however I would like the time until it happens to be as far away as possible ie until I get a reliable backup solution implemented.
I have had a couple of fsck failures on booting my machine and whilst this is not many, I would like to prevent data loss as much as possible until I can implement a thorough backup solution.
No, that's not the correct way to look at it. Sooner or later, you will have data loss, no matter what you do: so you must have a backup. OK. One of the next emails thru to the list will be the startup of a backup script that I will use as opposed to fiddling around with fscks.
One last thing when the fs fails after a power outage, should I just run #fsck /dev/<bad partition> , or should I run an argument under fsck, besides a/p as warned against ie #fsck > /dev/<bad partition>? I assume the plain fsck would be OK as it will know about the journal etc but maybe '-c' to check for blocks? To the drawing board I go to design the backup script. <anip>
But this is Linux, not windows: it is very difficult to develop filesystem errors; most are caused by system crashes or power failures. The system will not corrupt your fs while running, even during months. Windows it is not but I would like to protect my fs as much as possible during power outages as I cannot get a UPS, yet.
I would like to run a fsck at varying times on the different partitions so that, while the disk might fail, the fs on it would be correct.
That would be of very little use. If the disk fails, a) you will probably not be able to read it. b) the fs would probably get corrupted in the process of failing. In hindsight after looking at my message I agree.
<snip>
So I figured I needed the following:
#tune2fs -c0 -id<days between checks> /dev/hdd<partition number>
This would disable to mount_count checking and run a check on ? no of days on the given device. However no matter how I have tried to amend it to work each time I run the command it just gives me the syntax help(Which really isn't any help).
Why on earth do you want to disable either mount count or time dependency count? Why not both? The settings that SuSE does by default are very sensible, I would not alter them so much. Ah, but I have altered them a while back with the tune2fs command and now want to 'undo' those changes by redoing them.
Currently /root and /home are checked every two days, /usr = x days, /opt is checked every y days etc. Which /etc or other location/file holds a list of the settings I set on the fs that I could print? -- ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 ========================================================================