Re: Confused-New Stable Sarge Dist-Upgrade
Luis Finotti wrote: Dear Basajaun and all, Basajaun wrote: [snip] Well, you could try the old link trick. First of all locate the biggest directory(ies) residing in /, e.g. du -sh /* then, move that directory and all of its contents to a bigger partition, where space is not a problem, e.g. cp -R /big_dir /scratch/ then create a link in / with the old dir name, and pointing to the new location, e.g. ln -s /scratch/big_dir /big_dir Yes, it is a dirty trick, but will save your day until you repartition properly (say, when reinstalling the whole system). HTH, Basajaun That was my first idea when reading the original post. In fact, I was thinking of doing that in a laptop of a friend. Is there any reason why this is a dirty trick. Is there any problem or disavantage in doing so? It seemed to me it would be safer (and easier) than changing partitions sizes... Thanks in advance, Luis In fact I don't consider it to be dirty, I was just being humble :^) A problem I could think of is that symlinking makes it more difficult to track what exactly is in each partition. In my example, supposedly /scratch/ is a big dir where all the temporal files for the execution of some programs reside. It gets trashed periodically (these programs don't always successfully delete their temp files), and it is good practice to delete its contents once in a while. If I am not careful, I could end up deleting files that _are_ important, and that shouldn't really be there. Another problem is that it defeats the whole purpose of partitioning, which is making independent compartments, so that if one of them fills up or gets corrupted, the others don't suffer. Finally, I am not sure if it affects the I/O speed. I guess it should be transparent, but I don't know. So, yes, actually it is a good solution :^) Basajaun -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused-New Stable Sarge Dist-Upgrade
Leonard Chatagnier wrote: Leonard Chatagnier said: tar: ./lib/modules/2.6.8-2-686/modules.symbols: Cannot write: No space left on device tar: Error exit delayed from previous errors I chacked partition space with df and seem to have ample room as shown ChatagnierL-Home:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda2 14114049 18722 86% / Phil said: Your / partition is where /lib lives, and you've only got ~18MB. I'd say your modules directory should take up more than that. 30MB+. Prolly not enough space. Hey Phil, thanks, that explains it. Now how to get more space on /? I could resize partitions with cfdisk and probably mess things up. You have a more newbie(noobie) frendly way of doing this? Any thought or suggestions will be much appreciated. BTW, did you see any problem with the df output for tmpfs as I wasn't sure if it was saying 0% usage or 0% free space. Also, for my clarification and understanding, the sarge modules were already installed from previous testing upgrades, so, why couldn't it just be written over with the new stable sarge or is the new upgrade that much larger..??? Appreciate any info on this. Thanks, leonard I find parted is not so hard -- after launching it, type 'help' and you get an overview of the available options; Then, for example, 'help resize' will give you some information on resizing The way is now simple: make a large partition smaller (maybe /var or /usr or /home) and make / bigger 'print' is helpfull to see the current state of the disc partitions I think you should not have partitions mounted which are to be resized -- anyone know how to do the resizing of / ? if resizing / really cannot be done, maybe create a new /lib partition instead HTH, Joris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused-New Stable Sarge Dist-Upgrade
Joris Huizer wrote: Leonard Chatagnier wrote: Leonard Chatagnier said: tar: ./lib/modules/2.6.8-2-686/modules.symbols: Cannot write: No space left on device tar: Error exit delayed from previous errors I chacked partition space with df and seem to have ample room as shown ChatagnierL-Home:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda2 14114049 18722 86% / Phil said: Your / partition is where /lib lives, and you've only got ~18MB. I'd say your modules directory should take up more than that. 30MB+. Prolly not enough space. Hey Phil, thanks, that explains it. Now how to get more space on /? I could resize partitions with cfdisk and probably mess things up. You have a more newbie(noobie) frendly way of doing this? Any thought or suggestions will be much appreciated. BTW, did you see any problem with the df output for tmpfs as I wasn't sure if it was saying 0% usage or 0% free space. Also, for my clarification and understanding, the sarge modules were already installed from previous testing upgrades, so, why couldn't it just be written over with the new stable sarge or is the new upgrade that much larger..??? Appreciate any info on this. Thanks, leonard I find parted is not so hard -- after launching it, type 'help' and you get an overview of the available options; Then, for example, 'help resize' will give you some information on resizing The way is now simple: make a large partition smaller (maybe /var or /usr or /home) and make / bigger 'print' is helpfull to see the current state of the disc partitions I think you should not have partitions mounted which are to be resized -- anyone know how to do the resizing of / ? if resizing / really cannot be done, maybe create a new /lib partition instead HTH, Joris The more classic solution to this would be to get another available partition by what ever means (adding another disk, parted...) and the create a mount point in your fstab table for /lib. The process would go something like this, assuming that the new partition is /dev/hda6 and / is /dev/hda2 mount /dev/hda6 /mnt cp -r /lib/* /mnt (or a dozen other methods will do, rsync -a for example) edit /etc/fstab to include a mount point for this /dev/hda6 /lib ext3defaults0 2 remount all your partitions. At this point you still have all the files in /lib of /dev/hda2 but you need to make sure you got it right before you remove them. if everything works correctly you can mount --bind the / partition to another mount point (/mnt) and the remove the directory /mnt/lib/ You should now have all your libs on /dev/hda6 and lots of space on your / partition. NOTE: not tested and I haven't had any coffee yet... So do your research before you let your fingers do the walking. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused-New Stable Sarge Dist-Upgrade
[snip] Phil said: Your / partition is where /lib lives, and you've only got ~18MB. I'd say your modules directory should take up more than that. 30MB+. Prolly not enough space. Hey Phil, thanks, that explains it. Now how to get more space on /? I could resize partitions with cfdisk and probably mess things up. You have a more newbie(noobie) frendly way of doing this? Any thought or suggestions will be much appreciated. [snip] Well, you could try the old link trick. First of all locate the biggest directory(ies) residing in /, e.g. du -sh /* then, move that directory and all of its contents to a bigger partition, where space is not a problem, e.g. cp -R /big_dir /scratch/ then create a link in / with the old dir name, and pointing to the new location, e.g. ln -s /scratch/big_dir /big_dir Yes, it is a dirty trick, but will save your day until you repartition properly (say, when reinstalling the whole system). HTH, Basajaun -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused-New Stable Sarge Dist-Upgrade
On Wed, Jun 08, 2005 at 05:36:21AM -0400, Tom Allison wrote: if resizing / really cannot be done, maybe create a new /lib partition instead Don't do this! /lib, /bin and /etc MUST be on your root filesystem or the system won't boot. Frank -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. - Brian W. Kernighan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused-New Stable Sarge Dist-Upgrade
Obviously, the following line: cp -R /big_dir /scratch/ should read: mv /big_dir /scratch/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Confused-New Stable Sarge Dist-Upgrade
Thanks to all you guys for your suggestions. I'll have to study a while before I decide how to proceed as I tend to get symlinks backwards even after reading man. I actually feel more comfortable resizind partitions. One thing I'd like to kow before closing this thread, how does one know, or read, just what's in the hda2 / partition or any partition for that matter. ls /, of course, gives the entire / subdirectory for the linux disc. I would also very much appreciate any guidance, recommendations on just how much more space to add to the root partition to be safe in the future. Currently I have woody and sarge installed on my HD with lost tty terminals on both and X(KDE) not working on woody(devfs problem) so I have alot of fixing to do. How much of my current problems are caused by lack of room on / part, I don't know, buy suspect there all related. Again, thanks for all your input. Leonard Chatagnier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused-New Stable Sarge Dist-Upgrade
Dear Basajaun and all, Basajaun wrote: [snip] Well, you could try the old link trick. First of all locate the biggest directory(ies) residing in /, e.g. du -sh /* then, move that directory and all of its contents to a bigger partition, where space is not a problem, e.g. cp -R /big_dir /scratch/ then create a link in / with the old dir name, and pointing to the new location, e.g. ln -s /scratch/big_dir /big_dir Yes, it is a dirty trick, but will save your day until you repartition properly (say, when reinstalling the whole system). HTH, Basajaun That was my first idea when reading the original post. In fact, I was thinking of doing that in a laptop of a friend. Is there any reason why this is a dirty trick. Is there any problem or disavantage in doing so? It seemed to me it would be safer (and easier) than changing partitions sizes... Thanks in advance, Luis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Confused-New Stable Sarge Dist-Upgrade
I was running Testing Sarge 2.6.8-2-686-13 Stock and just completed wajig distupgrading to Stable Sarge picking up a new version of the 2.6.8-2-686 KI-16(I think). Everything went smoothly until unpacking and installing modules. The following is an example of the error output except that virtually every subdirectory was included in messages: tar: ./lib/modules/2.6.8-2-686/kernel/sound/pci/au88x0/snd-au8820.ko: Cannot open: No such file or director tar: Skipping to next header Now here's the kicker, I checked the subdirectories down to the *.ko files and they do exist. Please explain. Do I have a problem or not? What do I do about it if it is a problem? Below are listed the closing error messages just before the prompt reappeared: tar: ./lib/modules/2.6.8-2-686/modules.symbols: Cannot write: No space left on device tar: Error exit delayed from previous errors dpkg-deb: subprocess tar returned error exit status 2 debsums: can't unpack /var/cache/apt/archives/kernel-image-2.6.8-2-686_2.6.8-13_i386.deb E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/debsums ]; then /usr/bin/debsums --generate=nocheck -sp /var/cache/apt/archives; fi' E: Sub-process returned an error code E: Sub-process /usr/bin/dpkg returned an error code (1) I chacked partition space with df and seem to have ample room as shown ChatagnierL-Home:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda2 14114049 18722 86% / tmpfs63472 0 63472 0% /dev/shm /dev/hda3 3368004 2339164857748 74% /usr /dev/hda6 2680180 1582836961196 63% /var /dev/hda793309 45274 43218 52% /home /dev/hda893309 66225 22267 75% /temp none 10240 820 9420 9% /dev ChatagnierL-Home:~# Be happy to supply any other needed info that's available. Thanks for any help or explanation on what's going on an if fixing is needed. I don't know the significance of the tmpfs results or what to do. Leonard Chatagnier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused-New Stable Sarge Dist-Upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Leonard Chatagnier said: tar: ./lib/modules/2.6.8-2-686/modules.symbols: Cannot write: No space left on device tar: Error exit delayed from previous errors I chacked partition space with df and seem to have ample room as shown ChatagnierL-Home:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda2 14114049 18722 86% / Your / partition is where /lib lives, and you've only got ~18MB. I'd say your modules directory should take up more than that. 30MB+. Prolly not enough space. - -- /phil -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCpjPMGbd/rBLcaFwRAgcaAJ9hXp+aR0WdwN90+uPS6AiEpz2deQCfbWoS cslOOt338kIVzZ2kezNH96g= =nTnj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused-New Stable Sarge Dist-Upgrade
Leonard Chatagnier said: tar: ./lib/modules/2.6.8-2-686/modules.symbols: Cannot write: No space left on device tar: Error exit delayed from previous errors I chacked partition space with df and seem to have ample room as shown ChatagnierL-Home:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda2 14114049 18722 86% / Phil said: Your / partition is where /lib lives, and you've only got ~18MB. I'd say your modules directory should take up more than that. 30MB+. Prolly not enough space. Hey Phil, thanks, that explains it. Now how to get more space on /? I could resize partitions with cfdisk and probably mess things up. You have a more newbie(noobie) frendly way of doing this? Any thought or suggestions will be much appreciated. BTW, did you see any problem with the df output for tmpfs as I wasn't sure if it was saying 0% usage or 0% free space. Also, for my clarification and understanding, the sarge modules were already installed from previous testing upgrades, so, why couldn't it just be written over with the new stable sarge or is the new upgrade that much larger..??? Appreciate any info on this. Thanks, leonard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
