Re: vivaldi?

[Ingo Jürgensmann <ij@2013.bluespice.org>]

Am 29.09.2013 um 19:12 schrieb "Christian T. Steigies" <cts@debian.org>:

>> The long run fix might be to hope for an upstream fix of the LVM
>> problem or to switch to btrfs snapshots. Or to cleanup the cruft in
>> pre/post scripts of sbuild.
> I think other arches have switched to btrfs or unpacking tarballs. I don't
> think I want to work with tarballs on m68k, snapshots are much faster.

Yes, I agree. :)

> I have no idea what these numbers mean. On kullervo I see:
> root@kullervo:~>lvs
>  LV                                                   VG       Attr LSize Pool Origin     Data%  Move Log Copy%  Convert
>  buildd-sid                                           kullervo owi-aos-- 4.00g                                      
>  sid-m68k-sbuild-9a14cde0-adc3-4598-9007-f6ada8958e37 kullervo swi-a-s-- 4.00g      buildd-sid  91.59               
>  sid-m68k-sbuild-9d323b40-9d1e-440d-a250-279dfad5d006 kullervo swi-a-s-- 4.00g      buildd-sid  84.73               
>  sid-m68k-sbuild-a9f9897a-a700-4449-b11c-36ac800b9b23 kullervo -wi-a---- 4.00g                                      
>  sid-m68k-sbuild-e0f47be2-9c2a-486d-93e8-8f1612be56f0 kullervo swi-aos-- 4.00g      buildd-sid   1.81               
>  user                                                 kullervo -wi-ao--- 4.00g                                     
> 
> So the first two snapshops seem to be pretty full... but the partitions are
> not mounted, only the e0f4.. one is in use. are these unused partitions the
> problem? As soon as there are too many of them, I run out of "extends"?

Yes. But basically there should only one "buildd-sid" origin at all. It might happen that two buildds are started after reboot: one by init script and one by cron. I've disabled the init script on my buildds. 

> Since the builds take a few hours on m68k, we do not run into this problem
> as fast as ia64 and others. Shouldn't it be possible to remove these
> outdated snapshots manually?

Yes, of course, but it gets awkward over time... find the mounted filesystems, umount them and then lvremove the unwanted LVs... 

But here's my script: 

arrakis:/home/ij# less /root/bin/cleanup-schroots.sh
#!/bin/bash

/etc/init.d/schroot stop
mount | grep var/lib/schroot | tac | awk '{print $3}' | xargs -n 1 umount
lvremove -f /dev/vg/sid-m68k-sbuild*
rm /var/lib/schroot/session/sid*
/etc/init.d/schroot start


> Since I booted the unified 3.10 kernel (37 days ago), I have seen only one
> segfault on one of the buildds, so this is the most stable kernel in a
> really long time! And I have not run out of "extends" yet. Is vivaldi
> running 3.10?


Yes: 
Linux vivaldi 3.10-2-m68k #1 Debian 3.10.5-1+m68k.2 (2013-08-09) m68k GNU/Linux

But Arrakis is running very unstable with the same 3.10 kernel... so I reverted to 3.2.0-4.

-- 
Ciao...            //      Fon: 0381-2744150
      Ingo       \X/       http://blog.windfluechter.net


gpg pubkey:  http://www.juergensmann.de/ij_public_key.asc