 |
|
 |
Reader's Favorites
Media Casualties Mount Administration Split On Europe Invasion Administration In Crisis Over Burgeoning Quagmire Congress Concerned About Diversion From War On Japan Pot, Kettle On Line Two... Allies Seize Paris The Natural Gore Book Sales Tank, Supporters Claim Unfair Tactics Satan Files Lack Of Defamation Suit Why This Blog Bores People With Space Stuff A New Beginning My Hit Parade
Instapundit (Glenn Reynolds) Tim Blair James Lileks Bleats Virginia Postrel Kausfiles Winds Of Change (Joe Katzman) Little Green Footballs (Charles Johnson) Samizdata Eject Eject Eject (Bill Whittle) Space Alan Boyle (MSNBC) Space Politics (Jeff Foust) Space Transport News (Clark Lindsey) NASA Watch NASA Space Flight Hobby Space A Voyage To Arcturus (Jay Manifold) Dispatches From The Final Frontier (Michael Belfiore) Personal Spaceflight (Jeff Foust) Mars Blog The Flame Trench (Florida Today) Space Cynic Rocket Forge (Michael Mealing) COTS Watch (Michael Mealing) Curmudgeon's Corner (Mark Whittington) Selenian Boondocks Tales of the Heliosphere Out Of The Cradle Space For Commerce (Brian Dunbar) True Anomaly Kevin Parkin The Speculist (Phil Bowermaster) Spacecraft (Chris Hall) Space Pragmatism (Dan Schrimpsher) Eternal Golden Braid (Fred Kiesche) Carried Away (Dan Schmelzer) Laughing Wolf (C. Blake Powers) Chair Force Engineer (Air Force Procurement) Spacearium Saturn Follies JesusPhreaks (Scott Bell) Science
Nanobot (Howard Lovy) Lagniappe (Derek Lowe) Geek Press (Paul Hsieh) Gene Expression Carl Zimmer Redwood Dragon (Dave Trowbridge) Charles Murtaugh Turned Up To Eleven (Paul Orwin) Cowlix (Wes Cowley) Quark Soup (Dave Appell) Economics/Finance
Assymetrical Information (Jane Galt and Mindles H. Dreck) Marginal Revolution (Tyler Cowen et al) Man Without Qualities (Robert Musil) Knowledge Problem (Lynne Kiesling) Journoblogs The Ombudsgod Cut On The Bias (Susanna Cornett) Joanne Jacobs The Funny Pages
Cox & Forkum Day By Day Iowahawk Happy Fun Pundit Jim Treacher IMAO The Onion Amish Tech Support (Lawrence Simon) Scrapple Face (Scott Ott) Regular Reading
Quasipundit (Adragna & Vehrs) England's Sword (Iain Murray) Daily Pundit (Bill Quick) Pejman Pundit Daimnation! (Damian Penny) Aspara Girl Flit Z+ Blog (Andrew Zolli) Matt Welch Ken Layne The Kolkata Libertarian Midwest Conservative Journal Protein Wisdom (Jeff Goldstein et al) Dean's World (Dean Esmay) Yippee-Ki-Yay (Kevin McGehee) Vodka Pundit Richard Bennett Spleenville (Andrea Harris) Random Jottings (John Weidner) Natalie Solent On the Third Hand (Kathy Kinsley, Bellicose Woman) Patrick Ruffini Inappropriate Response (Moira Breen) Jerry Pournelle Other Worthy Weblogs
Ain't No Bad Dude (Brian Linse) Airstrip One A libertarian reads the papers Andrew Olmsted Anna Franco Review Ben Kepple's Daily Rant Bjorn Staerk Bitter Girl Catallaxy Files Dawson.com Dodgeblog Dropscan (Shiloh Bucher) End the War on Freedom Fevered Rants Fredrik Norman Heretical Ideas Ideas etc Insolvent Republic of Blogistan James Reuben Haney Libertarian Rant Matthew Edgar Mind over what matters Muslimpundit Page Fault Interrupt Photodude Privacy Digest Quare Rantburg Recovering Liberal Sand In The Gears(Anthony Woodlief) Sgt. Stryker The Blogs of War The Fly Bottle The Illuminated Donkey Unqualified Offerings What she really thinks Where HipHop & Libertarianism Meet Zem : blog Space Policy Links
Space Future The Space Review The Space Show Space Frontier Foundation Space Policy Digest BBS AWOL
USS Clueless (Steven Den Beste) Media Minder Unremitting Verse (Will Warren) World View (Brink Lindsay) The Last Page More Than Zero (Andrew Hofer) Pathetic Earthlings (Andrew Lloyd) Spaceship Summer (Derek Lyons) The New Space Age (Rob Wilson) Rocketman (Mark Oakley) Mazoo Site designed by 
Powered by Movable Type |
 |
|
Fedora Update Update So I was updating my machine, per the instructions found here, and things were going along swimmingly for a while, until I got the following stretch of error messages: ################################ Is this ok [y/N]: y File "/usr/lib/python2.3/site-packages/urlgrabber/grabber.py", line 852, in _do_grab ####################################### At which point it returned to the root prompt. What now? [Update at noon] Oops! /var is full. ###################################### [root@linux-station home]# df What do I do about that? Any magic tools that can repartition a live drive?
OK, I guess the question is, given that (in theory) I've done a partial update from Core 3 to Core 4, but it bombed out part way through, is the machine rebootable? Or do I have to figure out a way to install and run gparted under the current running shell? I don't want to reboot into a Livedisk for repartioning, only to find out that my OS is FUBAR, even with the bigger partition, on reboot. Posted by Rand Simberg at May 29, 2006 06:43 AMTrackBack URL for this entry:
http://www.transterrestrial.com/mt-diagnostics.cgi/5541 Listed below are links to weblogs that reference this post from Transterrestrial Musings.
Comments
Buy a Mac? Posted by philw at May 29, 2006 09:10 AMNo, a Mac would (literally) not serve my needs. Not to mention the fact that I dislike the interface, and don't find them intuitive at all. Go proselytize somewhere else. Posted by Rand Simberg at May 29, 2006 09:12 AMHey Rand I held off on saying the Mac thing! Reformat and start over with a clean install? Sounds like you may have hardware problems screwing with your upgrade. It all started going downhill with your memory problem. Why don't you find and old hard drive, install Windows and troubleshoot any possible hardware problem with Norton. Linux systems seem to not have as good of hardware troubleshooting software. As you are going now you are just digging your hole deeper. Or buy a Mac and install Linux on that box, or if you really like the interface use the B$D Unix and X Windows on the Mac hardware. You don't have to use Aqua. Dennis No, sorry, I'm generally quite happy with AMD and Linux, and I don't have the money to spend on a new Apple that I don't want. I'm just not happy with this particular machine right now. Posted by Rand Simberg at May 29, 2006 09:24 AMThere's a tool called GParted which will let you edit partitions, including moving and (I think) resizing many of them. http://gparted.sourceforge.net/index.php is the home page. There's a Live CD that you can use to work on a system. Another tool to consider is the Ultimate Boot Disk; it's got a copy of MEMTEST86 on it http://ubcd.sourceforge.net/ I've played with both, but haven't had to use either in a live recovery situation as yet. I'm moderately gifted with Linux-fu, so if you have questions drop me an email. I'm spambait42c on that yahoo.com thingy. (That should be obscure enough to trick the harvestbots...) Posted by Glenn at May 29, 2006 11:49 AMLets see. About once every three or four months you end up with problems like this. Hey its your life. Even if you don't do the Apple thing at least have a hard drive around with another install of Linux or Windows and some troubleshooting tools. It will save you much pain and suffering the next time this happens to you (in about three or four months). Dennis
I have used gparted in a recovery situation. Some years ago, in a sleep deprived state, I accidentily used dd to blast over the first 1.44 MB of my boot drive! Amazingly, Linux continued to run without error, which allowed me to run gparted and reinstall LILO. Rand, you're just having a run of bad luck! OSX, Linux, Windows, whatever - they all need ECC hardware support to conquer defective memory, which your mobo and/or RAM do not have. As for a full partition, I can't imagine any OS doing better than a "No space left on device" message. Posted by Eric at May 29, 2006 12:59 PMAbout once every three or four months you end up with problems like this. No, I had a problem a few months ago (which I never really resolved at the time, because I've been busy, and it's not a mission-critical machine right now), and I had a problem now, because I decided to use the holiday break to resolve it, and it turns out they're the same problem--a previously undiagnosed bad memory stick. I've been running Linux in various forms for about eight years, and had few problems. Going out and spending mucho moolah on a machine in which I have no interest would make no sense under the circumstances. Posted by Rand Simberg at May 29, 2006 03:15 PMYou're making this harder than it needs to be. type in the following command as root: du -s /var/* This will tell you which directories in /var are very full. I'm willing to bet good money that one of the big ones (if not the biggest) will be /var/logs. Look in /var/logs. You will see many files called messages, messages.0, messages.1 and so on. On some versions of Unix they may be called "system" instead of messages. Delete all messages.* files - they are backups of old system messages and not needed at the moment. Now do this: du -s /var/log/* Look for the largest sub-directories. Is one of them especially large? Look at the contents - it's probably logs from one of your applications - the web server, something like that. Delete the contents. -- If this doesn't free up enough space, then the next thing to look at is uninstalling software you don't use. You'll have to look at the man pages for RPM to figure out how to associate files in /var with the software package that owns them (assuming they aren't obvious like "/var/mysqld" or similar. If you're worried about deleting something you need, backup /var to a CD-R first. Posted by Michael heinz at May 29, 2006 05:35 PMThanks, I was wondering when I saw that, "Gee, how much of what's currently in /var do I really need? I can certainly live without the logs. That does sound like the most painless way to go. Just clean up the directory, and try to finish the update. Once that's done, I can repartition to prevent future occurences. Posted by Rand Simberg at May 29, 2006 05:38 PMI'm afraid, my lack of foresight caused this. I'm very sorry. I claimed that the risk of having the box unbootable is minimized with yum, and I stand by that. Reboot at will. If it fails, then... I dunno. Dinner maybe? Yes, yum downloads literally whole distribution into /var/cache/yum before it proceeds upgrading. This means that your /var has to have a lot of free space. [[Never mind everything until the next bracket... Just so you know what kind of idiot I am, I won't delete it. I wrote all that and _then_ looked at your df output, helpfuly provided... Naturally, I ran into this problem before, and completely forgot about it. I overcame it in a couple of different cases in a different way. Unfortunately, both are labor intensive. Method A is to remove worst offenders like OpenOffice.org beforehand, clean them out from /var/cache/yum. Once you see du /var minus du /var/cache/yum going below 55% (of the total!, not just /var; when you remove the size of total decreases), you may proceed. Makes sense, right? This is only good when you can clean that much. Naturally, the list is kept in a file, then missing packages are re-intalled with "yum install", if you need them at all. Method B is to be used when there's just too much to remove. Like, whole GNOME needs to be killed to reach the free percentage. Then, update package by package, like this: "yum update bash". Do "yum clean packages" in between steps when your /var threatens to overflow (it's inefficient if yum has to re-pull again, but oh well... The key is to update by rough groups, e.g. Gnome, KDE, System utils, Daemons, misc.) Now that I spelled the options, the whole story stinks. Maybe it was easier to re-install, after all. But at least the RAM is fixed, which is a good thing regardless.]] Back to real world - your root has 6393744KB free, and /var is only 1004024KB total. The total in the root is only 3489804KB. Isn't the solution obvious? cd / That's it. No need to reboot even. You'll need to kill syslog and anyone who's holding /var open (check with fuser -m /var), before you can umount it. EWWWW, what a goofy error. That'll teach you to follow suggestions of strangers on the Internet. mkdir var.new EWWWW, what a goofy error. Yes, I was scratching my head, trying to figure out the method to your madness. Thanks for the suggestion. Posted by Rand Simberg at May 29, 2006 07:59 PMDon't use multiple partitions. Yes, I know that "everyone" advises you to, but how often has doing so helped and how often has it hurt? Don't use multiple partitions. For a new setup, I probably woudn't, but this is a legacy system (going back several years, when drives were much smaller), in which I was worried about hard disks filling up due to runaway activities in /var and /tmp. It reminds me of the old story about Bill Gates and 640K of RAM. No one will ever need more than a gigabyte for /var, right? Posted by Rand Simberg at May 30, 2006 09:40 AMThe good news is that (if I understand correctly, which is not 100% sure), yum's procedure is: 1) take a list of packages to install 2) figure out what extra packages I need to support those 3) download all the packages in question 4) make a final review to be sure all this will install without contradiction 5) do the actual installations in appropriate order
Post a comment |
|
