On Mon, 26 Mar 2012, Craig Sanders wrote:
On Mon, Mar 26, 2012 at 03:01:18PM +1100, Tim Connors wrote:
[ ... xfs_repair ... ]
Now if only there was a fsck.xfs and regular checks every ~20 mounts.
alternatively, and with 50% less facetiousness, you can even make ext[234] filesystems behave in a non-annoying manner:
tune2fs -i 0 -c 0 /dev/ext[234]partition
:-)
craig
-- craig sanders <cas@taz.net.au>
Interesting, I still use ext2/3 and what I have done to sort of partly get around the problem is to increase the number of mounts before a forced fsck. This was done by simple mutilpying the value debian setup be 4. The current ranges on my systems now being inthe range 70 to around 130 mounts. As the systems are shut down at night and usualy only started every 2nd day a forced fsck every 6 to 8 months is not a major disaster. But I must say I question the necesity of such a check. From memory the only time it showed up any problems was some days before the voltage regulation on a 12V line on one of my systems completely failed. Every other time fsck has run was caused by some thing I had done. As for data backups I have 5 copies of all important data (Note 1). at least once a year the entire lot is writen to a drive and then compared with the others make sure its is complete. So a single drive failure is not a disaster. The back procedure also includes baking up copies of items I have just done or are in the process of doing, Note 3. Note 1: Important data is mostly data I have entered myself or data that the original is unlikely to be/ or is no longer avaible. Such things as old engineering documents, programs and graphics I have done myself, my vinyl record colection and more recently my digital photos. The greatest share of the space is taken up by the photos a single raw photo from my Nikon D700 being in the order of 17 mbytes. Note 2: I have never realy bothered about newer filesystem formats, for nearly 30 years I look after some very complex systems and what this taught me was if such a thing was not broken _____DON'T_____ fix it, that is if the old system is providing what one requires why change it. The change will cause pain. Note 3: I have actually never lost any data, I come up with this way of treating data from one of the first PC's I ever encounted that was a Time 4500, way back in the "bad old days". This had a quite enreliable drive set up and one very quickly got used to backing up every thing not matter how unimportant. A __real__ good training tool it was. Lindsay