Ever increasing storage capacity is making me lazy. In years gone by, when resources were more limited, a full filesystem would be cause for investigation, to find out why it had become full, and what could be done about it. These days, the easy option is to just extend the volume a bit more and grow the filesystem. I'm running a bit low on free PV space, so last week I didn't grow my home filesystem by as much as I normally would when it filled up. But even so, I was a little surprised to find out that within a couple of days it was already full again. That's not normal. It turned out that a single log file was continually growing and had taken up nearly a third of the total space on that filesystem. But because the default assumption is that I have more disk space than I'll be able to use, I hadn't been keeping an eye on what was taking up the space. D'oh! So a single rm has taken me back to having loads of free space.
So Libya has cut itself off from the net. This isn't an entirely unexpected move. But it has the side effect of screwing over anyone with a
But somehow I just can't find it in me to feel any sympathy for them. At the time they launched, I pointed out that they were putting themselves at the mercy of the Libyan government. But it seems they preferred the two digit
Maybe it'll act as a warning to those who have jumped on the
It's what we were all hoping for, and I'm pleased that it's come to pass. It's not perfect, and I don't agree with all of their decisions. However, even an imperfect alternative to the current H.264 situation is a massive improvement. I'm pleased they've gone for a full stack solution of not only VP8 but also Matroska(-ish) and Vorbis, too. If nothing else, it's likely to mean that a) Vorbis will be shipped by default on most platforms[1], and b) hardware support for both VP8 and Vorbis should be widespread in the very near future. Further, there's a commitment to transcode all of the existing videos on YouTube. That's a massive endorsement. Of course, the risk with that is the reduced quality that will come from three or more lossy transforms, but given that they've announced it, they're clearly not too concerned about that. The future's looking very bright indeed.
[1] Or will it? I've yet to see any official response from Microsoft or Apple on this. But it's going to be hard for them to ship something that won't play YouTube videos by default. Of course, in the short and probably medium term, YouTube will continue to offer videos in other formats as well. But we'll see how it plays out in the long term.
Also interesting to see the stats on when their systems were delivered to McLaren and Brawn, and where the performance of those cars was afterwards. I know there's more to F1 than CFD, but it certainly plays a large part these days.
building file list
... done
rsync: delete_file: unlink "/backup/local/shared/camera/2009-08-24--foq/img_0507.jpg" failed: Read-only file system (30)
rsync: delete_file: unlink "/backup/local/shared/camera/2009-08-24--foq/.xvpics/img_0507.jpg" failed: Read-only file system (30)
That's never a good sign. Looking through the logs, I see a number of ATA errors, starting with a timeout, a device error, and a bunch of HSM violations. A few examples:
Mar 22 07:56:03 riva kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 22 07:56:03 riva kernel: ata2.00: cmd 25/00:00:87:d1:86/00:02:03:00:00/e0 tag 0 dma 262144 in
Mar 22 07:56:03 riva kernel: res 40/00:00:00:00:00/ff:ff:ff:ff:ff/00 Emask 0x4 (timeout)
Mar 22 07:56:03 riva kernel: ata2.00: status: { DRDY }
Mar 22 07:56:03 riva kernel: ata2: hard resetting link
Mar 22 07:56:03 riva kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar 22 07:56:03 riva kernel: ata2.00: configured for UDMA/33
Mar 22 07:56:03 riva kernel: ata2: EH complete
Mar 22 07:56:03 riva kernel: SCSI device sdb: 1465149168 512-byte hdwr sectors (750156 MB)
Mar 22 07:56:03 riva kernel: sdb: Write Protect is off
Mar 22 07:56:03 riva kernel: SCSI device sdb: drive cache: write back
Mar 22 07:59:05 riva kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar 22 07:59:05 riva kernel: ata2.00: BMDMA2 stat 0x6d0009
Mar 22 07:59:05 riva kernel: ata2.00: cmd 25/00:00:df:ce:87/00:02:03:00:00/e0 tag 0 dma 262144 in
Mar 22 07:59:05 riva kernel: res 51/04:80:5f:cf:87/00:01:03:00:00/e0 Emask 0x1 (device error)
Mar 22 07:59:05 riva kernel: ata2.00: status: { DRDY ERR }
Mar 22 07:59:05 riva kernel: ata2.00: error: { ABRT }
Mar 22 07:59:05 riva kernel: ata2.00: configured for UDMA/33
Mar 22 07:59:05 riva kernel: ata2: EH complete
Mar 22 07:59:05 riva kernel: SCSI device sdb: 1465149168 512-byte hdwr sectors (750156 MB)
Mar 22 07:59:05 riva kernel: sdb: Write Protect is off
Mar 22 07:59:05 riva kernel: SCSI device sdb: drive cache: write back
Mar 22 08:01:15 riva kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 22 08:01:15 riva kernel: ata2.00: cmd 25/00:00:ff:1e:88/00:02:03:00:00/e0 tag 0 dma 262144 in
Mar 22 08:01:15 riva kernel: res ff/ff:ff:ff:ff:ff/ff:ff:ff:ff:ff/ff Emask 0x2 (HSM violation)
Mar 22 08:01:15 riva kernel: ata2.00: status: { Busy }
Mar 22 08:01:15 riva kernel: ata2.00: error: { ICRC UNC IDNF ABRT }
Mar 22 08:01:15 riva kernel: ata2: hard resetting link
Mar 22 08:01:15 riva kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar 22 08:01:15 riva kernel: ata2.00: configured for UDMA/33
Mar 22 08:01:15 riva kernel: ata2: EH complete
Mar 22 08:01:15 riva kernel: SCSI device sdb: 1465149168 512-byte hdwr sectors (750156 MB)
Mar 22 08:01:15 riva kernel: sdb: Write Protect is off
Mar 22 08:01:15 riva kernel: SCSI device sdb: drive cache: write back
SMART doesn't seem to be much help here, with the device refusing to run anything but the mandatory offline test:
riva:~# smartctl --test=offline
/dev/sdb
smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Default Self Test Successful
riva:~# smartctl --test=short/dev/sdb
smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Short offline self test failed [unsupported field in scsi command]
riva:~# smartctl --test=long/dev/sdb
smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Long (extended) offline self test failed [unsupported field in scsi command]
It's a Seagate drive:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST3750528AS Rev: CC38
Type: Direct-Access ANSI SCSI revision: 05
I'm running 2.6.18-128.4.1.el5 on CentOS 5.
Any ideas? Does anyone know enough about the ATA spec to tell me what these errors actually mean? Is this a genuine hardware failure? If so, where's it likely to be? Drive? Controller? Cable? The drive is only a few weeks old, so while sometimes shit happens, I want to investigate the (probably more likely) alternatives as well.
And why oh why doesn't <tbody> nest? I want to refer to part of a table and manipulate it with some Javascript (mostly just to show or hide it in response to user actions). But I can't just stick the relevant bits in a <tbody> and select by that because the table already contains several tbodies. Thus I'm once again stuck in workaround hell, trying to tag each tbody with an appropriate class, so I can iterate over them and check if I'm interested in each one. Further, because I'm dynamically adding and removing parts of the table, I need to check at the time I add to the table whether the bit I'm adding should be visible or not. Life would be so much easier if I could just stick it in an appropriate <tbody> further up the hierarchy, and then mark the whole lot visible or otherwise. But I guess that would be far too easy
Any CPU will be more than sufficient for my needs. The screen needs to be at least 17", and not gloss (which sadly seems to rule out the otherwise promising models from Samsung). I need 2GB RAM, and I don't want to be paying more than £500. A bit of digging reveals that all of the major players have models that meet those requirements. But I still have the nagging feeling that I'm missing out of the "right" model simply because I don't know about it. Where should I be looking?
Oh, and it won't have an Apple badge, so don't even consider suggesting that...
If all else fails, lower your standards.