Observation: running fsck on a 20G partition takes a whole lot longer when the output is chock full of "NotReady | SeekFailed" errors and "short read" errors. (Not sure I've remembered the exact phrasing of the first category -- the system's running again despite some scary notices about unrecoverable files ... less scary on /home than if they'd been on /, but still...) I thought "not ready" messages looked a little funny considering that /home is on the same physical drive as the partition from which I was running the OS and fsck (/dev/hda6 vs. /dev/hda1).
Reminder to self: procrastination'll bite ya'. I'd been meaning to copy everything from /home over to the file server and automount the home directories from there, but hadn't gotten around to it, so there's stuff on this machine that I have in /home/dglenn and a bunch of other stuff that I access at /mnt/richards/dglenn and can get to from every other machine in the house. I'm sure NFS on the server downstairs would've dealt with this box suddenly turning itself off far more gracefully than its own local filesystem did.
Question: I've finally bothered to fire up the Debian "Music Player" (Rhythmbox) and tell it to find a bunch of my MP3 files. But when I import a folder, it finds a few tunes then half-hangs (it can play music and I can navigate its browser, but the process/thread/whatever that's adding new music hangs and the application has to be "force-quit", which I presume is just a GUI-friendly way of saying "kill -9"(?)); and of the tunes it's gotten, some play at chipmunk speed despite sounding fine in other players. Whiskey Tango Foxtrot? Clue, please?
Another reminder to self: read up on just what EXT3 is (it's journalled, right?) and what it's supposed to give me, and why the fs-type-specific program that fsck invoked for an EXT3 volume had a name that sounded like it was for EXT2.