MS Word at work just complained that it cannot find the file that I told it to open. The solution was to use the File -> Open menu and choose the "Open and repair" button.
I had the biggest PC related scare a couple of days ago. After I had two disks in my RAID5 fail in a very short amount of time and only pure luck saved my data I moved to RAID6 and I felt safer. That was, until two days ago I ran: # pvs -v pvs Scanning for physical volume names pvs Incorrect metadata area header checksum pvs Incorrect metadata area header checksum pvs WARNING: Volume Group vg0 is not consistent pvs Incorrect metadata area header checksum pvs Incorrect metadata area header checksum pvs PV VG Fmt Attr PSize PFree DevSize PV UUID pvs /dev/md2 vg0 lvm2 a- 1.80T 922.19G 1.80T Y9naEo-OKG6-0ZyX-qmZX-u3JP-uCPg-cE1hVX Ooops. Not looking good. # vgs -v vgs Finding all volume groups vgs Incorrect metadata area header checksum vgs Finding volume group "vg0" vgs Incorrect metadata area header checksum vgs Incorrect metadata area header checksum vgs VG Attr Ext #PV #LV #SN VSize VFree VG UUID vgs vg0 wz--n- 4.00M 1 15
Google webmaster tools will not verify a site by the file upload method if it does not return a proper 404 code on missing pages. With Wordpress and permalinks enabled, everything is redirected to index.php, which does exist and unless the PHP code itself overrides the return code, the response would be 200. The solution is to simply edit headers.php in the theme and add the following to the beginning of the file: <?php if (is_404()) { header('HTTP/1.1 404 Not Found'); } ?>
I have been trying to figure out why rsync was Segfault-ing when trying to transfer several hundred gigabytes from the old server to the new one. It was working fine but I interrupted it a few times. And then, when I was down to 5-6 gigabytes it would transfer a file or two (small files at that) and just spit out a weird message, like rsync error: errors with program diagnostics or it would complain about a timeout (I am copying from an NFS volume, what timeout?), or simply receive a Segfault. In a desperate attempt to figure out at least when the problem was occurring I decided to rebuild it with debugging symbols enabled. env CFLAGS=-ggdb3 emerge -av rsync I then fired up gdb an ran the problematic commands gdb run -avPAH /remote/... /var/.... and it worked fine . Since I had -Os in my CFLAGS, I tried using -O2 instead and still, there were no problems. Lesson learned, -Os does break stuff. Update: Well, -O2 saved the day for a while but rsync again started segfaulting when I tri
Comments
Post a Comment