debian archive disk space requirements.
Hi, I've noticed the growth in the debian archive with some concern over the last few weeks/months. We're now hitting the limit of the partition that debian is on and it will be quite difficult technically for us to deal with this in the short term. We have some new storage which is being comissioned but it won't be in place for about a month and the debian archive has already filled up a 100G partition we've dedicated to it here (that doesn't include the debian-cd or debian-non-US or other debian related archives.. just the main debian one). I'm stuck between a rock and a hard place here as we have a large dependency tree before we can move equipment over and get access to the new disk.. Is there any way to reduce the size of the archive over the next 4-6 weeks ? regards, -jason
Re: debian archive disk space requirements.
On Sat, 30 Aug 2003, Josip Rodin wrote: > /dev/sda3 97G 97G 470M 100.0 [] /bla /dev/sdf1100798036 98652428 2145608 98% /raid/lun1p1 and that is by moving a chunk of debian archives into another disk and symlinking back in.. > > Is there any way to reduce the size of the archive over the next > > 4-6 weeks ? > > We are still waiting for Joey to officially announce the obsolescence of > potato on -announce so that it can be moved to archive.debian.org. That will > buy us six, seven gigabytes at most. Other than that, I've no idea. Pray to > god that testing and unstable stop diverging so much? :) hmm ok. 6-7G would probably help for 4 weeks. once we move to the new disk i don't mind too much about debian growing again :-) /dev/sdb11220623064 32828 1208380596 1% /data1 i just need to get the time to be able to migrate stuff across.. and i really don't want to break ftp.au.debian.org for people.. regards, -jason
Re: debian archive disk space requirements.
On Sun, 30 Aug 2003, Heikki Vatiainen wrote: > [I am not on debian-devel but reading the list through Usenet gateway] i didn't realise debian-devel is gatewayed to a newsgroup.. interesting. > You may also want to see mount(8) and look for bind from the manual > page. Since there is not very much about it, I will just quote it > below. From mount(8): [...] > ftp.fi.debian.org has the whole debian/ on the same partition but a > couple of directories, such as debian-cd/, that were previously on the > same partition with the mirror root are now mounted from a new > location with the --bind option. /etc/fstab also works with bind > option with something like: > > /newloc/debian-cd /oldloc/debian-cd none bind,noatime,noexec,nodev > > Using bind should keep all mirroring programs happy since they do not > have to get confused when they find a symlink instead of > directory. i'm not entirely sure how this helps unless you mean we can use the above to start moving parts of the debian tree to different partitions and then remounting them inside the tree.. this would be a nice temporary solution except that we have a more complicated architecture as we have a back end fileserver where everything is mirrored and front end servers that actually provide the ftp/http/rsync services which read only NFS mount from the back end.. once you start doing loops and binds on the back end it tends to fall over with NFS structures :-/ thanks for the tip though. regards, -jason
