You can limit the amount of data loss in the event of a power failure to one minute by setting vm.dirty_writeback_centisecs = 6000.Ī side effect is that shutting down your computer will may take several minutes where it appears to be doing nothing. If your system loses power unexpectedly, you will get bad blocks. The problem: using this tip means that your system stops writing changes to disk until you shut down or type "sync" at a command line. This has an instant, noticeable effect, but it can lead to data loss.Īdd these lines to /etc/nf, and reboot. All changes will be written to memory, and the excruciatingly slow writes to happen in the background while you continue working. Since disk writes are so slow, you can change your system to keep things in memory longer. Linux usually ensures that all changes are written to disk every few seconds. If you do it, you will have to always shut down your computer properly from now on, because unexpected power failures will lead to data loss. If it works, remove the /usr.old directory to reclaim the space. Your fstab or undo the changes before continuing. If you get error messages or your /usr directory shows up empty, either fix Test whether you previously edited fstab successfully by typing: Move aside the old /usr directory and create a new mount point: (Ubuntu will close all open programs, then prompt you what to do. Unionfs /usr unionfs nodev,noatime,dirs=/.filesystems/usr/overlay=rw:/usr=ro 0 0 filesystems/usr/usr.sqfs /usr squashfs ro,loop,nodev 0 0 Sudo mksquashfs /usr /.filesystems/usr/usr.sqfs Otherwise, the cups print server will stop working: Sudo apt-get install squashfs-tools unionfs-tools I've adapted these instructions from here. Since read speeds are so slow, you can actually gain performance because there is less data to read. Using squashfs, it can be compressed to 0.7 GB. The /usr folder contains your programs, and it is usually 1.8 GB. Ubuntu uses a huge amount of space will all the programs it installs. On solid state storage, space is expensive. If you can't do that, then skip this tip. At worst you will need to mount the USB key on another linux system to recover (by editing /etc/fstab). Tip 3: Compress your files This tip can wreck your system, and to undo it you will need to be able to use a command line editor like nano, emacs, or vim. Maybe it's having an effect, but I can't tell. It's kind of like putting magnets under your pillow to improve health. The background is described in the author's Master's thesis. When you start your computer, it automatically loads these programs and library from disk in the background, so when you start firefox, for example, it will pop up right away. The preload daemon is a program that constantly looks at the programs you are running and figures out which ones you are most likely to use. Under the Advanced Tab, select Network and ensure that you use up to 0 MB of disk space for the cache.Under the Privacy setting, uncheck "Keep my history for.".Unfortunately, your USB key might only have a 6 MB/s write speed, causing everything to freeze up. But it doesn't just write Firefox stuff - it causes your entire system to dump all changes to disk. Fortunately, by following the tips below, you can make your USB or SD card based linux system fly!įirefox 3 has a hard-to-fix bug that causes linux to write to disk every time you visit a write page. Like many things on Ubuntu, it doesn't work right out of the box and needs some tweaking. It freezes up for a couple of seconds every time you click a link. ![]() If you've installed Ubuntu on a USB key or SD card, you are probably experiencing the annoying slowness of Firefox.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |