On 11 Aug., 14:12, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> On 2011-08-11 12:41, John Cremona wrote:
> > After building Sage the amount of filespace used is (as we all know)
> > rather large. I was just checking a 4.7 install, which is not used
> > for any development pusposes, and is on a machine which I use but do
> > not own, and where I was just told that the filespace was getting
> > short, and found that the SAGE_ROOT was taking up 15GB of which 5.5GB
> > is in devel and 8.4GB in local. Moreover, in devel I find:
>
> > masgaj@hpclogin1%cd devel/
> > masgaj@hpclogin1%du -sh *
> > 256K old
> > 256K sage
> > 3.1G sage-main
> > 256K sagenb
> > 2.4G sagenb-main
> > masgaj@hpclogin1%ls sagenb-main/
> > build go MANIFEST.in README.txt sagenb sass
> > setup.cfg spkg-dist
> > dist Makefile PKG-INFO release_notes.txt sagenb.egg-info
> > sdist setup.py SPKG.txt
> > masgaj@hpclogin1%ls sage-main/
> > build c_lib export MANIFEST.in module_list.pyc pull
> > sage setup.py spkg-dist
> > bundle doc install module_list.py PKG-INFO README.txt
> > sage-push spkg-delauto spkg-install
>
> > Can anyone say just why sagenb-main is almost as large as sage-main
> > itself? And is there a simple way (I looked for a command line option
> > but could not see one) of stripping down a Sage build so it is still
> > fully functional, including all the include files and shared libraries
> > under local/ (which I use for building other stuff) but which takes up
> > rather less than 15GB?
>
> I agree with leif, this is probably an issue with the filesystem you are
> using. This is on an reiserfs file system:
> $ cd $SAGE_ROOT
> $ du -sh # On-disk size
> 3.0G .
> $ du -bsh # Sum of byte sizes of files
> 2.7G .
In case it is, that's easy to solve without changing the [main]
filesystem's characteristics, assuming you're using Linux:
[To the owner or administrator of the affected box:]
# Create a sufficiently large file to create a filesystem in (here 4
GB):
dd if=/dev/zero of=/wherever/sage-filesystem bs=1024 count=4M
# Create a filesystem (here ext4) within that file:
# (You might get prompted whether to continue because it's not a block
device.)
mkfs -t ext4 /wherever/sage-filesystem
# Create a directory to later mount that filesystem on (usually in /
mnt or /media):
mkdir /mnt/sage-filesystem
# Mount the new filesystem:
mount -t ext4 -o loop /wherever/sage-filesystem /mnt/sage-filesystem
# Move (or copy) the Sage installation into that filesystem:
mv $SAGE_ROOT /mnt/sage-filesystem # or use "cp -pr ..."
# Sage now lives in e.g. /mnt/sage-filesystem/sage-4.7
You'll need administrator privileges ("sudo ...") for some of the
commands above, and depending on your setup, also for (re)mounting the
Sage filesystem later. (You can change the latter by editing /etc/
fstab and setting the appropriate options for that filesystem, i.e.,
add "user", and/or perhaps also "auto".)
-leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
