![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
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.
(no subject)
(no subject)
(no subject)
If your drive is giving 0x51 Drive Unready messages, it's probably about to die.
(no subject)
(no subject)
(no subject)
(no subject)
ext3 has issues. Switch to OpenSolaris or Windows for a more robust fs. Or at least BSD or some form of Unix if you're old fashioned.
(no subject)
(no subject)
So in this (unusual) case, screwing up the system and making it temporarily un-runnable would actually have been a bigger pain.
Though I really do need to get around to reinstalling the OS with the full list of packages I want and current versions of everything at some point, or trying to update it piecemeal.
But my file server is also running Linux (Mandrake 6 there, vs Debian 3 in the bedroom), and its partitions are all EXT2. The file server is supporting NFS, Samba, and Appletalk (I considered Andrew but haven't gotten around to setting it up to experiment with). Does Netatalk run under BSD or Solaris? If so, I could see changing operating systems for that machine when I get around to upgrading it -- I'd already been planning to at least use a more recent version of Linux.
Of course, with the age-related hardware problems I tend to get, I'd love to use RAID on the server, but the only sizes of drives I have four of are too small to do the job. (And yeah, I'd be doing software RAID on IDE if I set it up, 'cause I don't have a RAID controller ... and I've got fewer and smaller SCSI drives than ISE drives, otherwise I'd considering making one of the Sparcs play file server.)
(no subject)
Netatalk could probably even work on MacOS X. :-)
(no subject)
Though the smartass MacOS comment reminded me of a question for a hypothetical future: Ifwhen I get ahold of a Mac that can handle OS X, what'll be the best way to hook it to the file server? Netatalk, NFS, or something else entirely?
(Note: I really really like OS X. I just haven't got a studly enough Mac at home for it, so in the house I'm running 8.6 and 9.1, where Netatalk is the obvious choice.)