Has there been a solution found for controlling sector writes? We are just launching service and already have around 1093208 total writes on our RouterBoard system. It doesn't seem to be growing very fast now so it may have been something we done before, but it does seem to grow about 8-16 writes if I make any change to the logging settings or an association/pppoe connection connects or disconnects. I have my logging set to none for local and do not echo to console, I only have the syslog set as the remote. What else could be doing the writes on each of these actions above? Any help would be appreciated.

Thanks,
Brad

What version are you using now, what version did you start with, and how long has the disc module been in use?

Sector writes can not be totally avoided, but the number is way down in the 2.8.11 I am using now comparted to the 2.7 series I started with. The recommendation I received was to replace the disc module each year when you renewed the license.

There should be no need to replace a compact flash based on sector writes when using v2.8 and default logging settings. The current flash chips controllers are very advanced with extra sectors, wear leveling, error correction. They are emulating a fixed size hard drive -- so the size will not change unless the bios recognizes the media with different settings. Of course, someday they could crash, but our experience has been that a CF or IDE/DOM crashes because of:

1. older controllers could not handle being installed with incorrect bios settings -- meaning that if you move it around to other computers with different bios that recognize it differently, and install it, it may destroy the unit. Usually using 10 year old motherboards/bios firmware destroys things the fastest. Current controller technology is much better at accepting this.

2. electrical shock -- as with any IC, this or memory, this can ruin it.

John