summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2012-September/004683.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-sysadm/2012-September/004683.html')
-rw-r--r--zarb-ml/mageia-sysadm/2012-September/004683.html117
1 files changed, 117 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2012-September/004683.html b/zarb-ml/mageia-sysadm/2012-September/004683.html
new file mode 100644
index 000000000..0c9e36731
--- /dev/null
+++ b/zarb-ml/mageia-sysadm/2012-September/004683.html
@@ -0,0 +1,117 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-sysadm] [sysadmin-reports] Hobbit [727252] valstar.mageia.org:disk CRITICAL (RED)
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20%5Bsysadmin-reports%5D%20Hobbit%0A%09%5B727252%5D%09valstar.mageia.org%3Adisk%20CRITICAL%20%28RED%29&In-Reply-To=%3C20120915162144.GW21938%40mars-attacks.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="004682.html">
+ <LINK REL="Next" HREF="004684.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-sysadm] [sysadmin-reports] Hobbit [727252] valstar.mageia.org:disk CRITICAL (RED)</H1>
+ <B>nicolas vigier</B>
+ <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20%5Bsysadmin-reports%5D%20Hobbit%0A%09%5B727252%5D%09valstar.mageia.org%3Adisk%20CRITICAL%20%28RED%29&In-Reply-To=%3C20120915162144.GW21938%40mars-attacks.org%3E"
+ TITLE="[Mageia-sysadm] [sysadmin-reports] Hobbit [727252] valstar.mageia.org:disk CRITICAL (RED)">boklm at mars-attacks.org
+ </A><BR>
+ <I>Sat Sep 15 18:21:44 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="004682.html">[Mageia-sysadm] [sysadmin-reports] Hobbit [727252] valstar.mageia.org:disk CRITICAL (RED)
+</A></li>
+ <LI>Next message: <A HREF="004684.html">[Mageia-sysadm] [sysadmin-reports] Hobbit [727252] valstar.mageia.org:disk CRITICAL (RED)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4683">[ date ]</a>
+ <a href="thread.html#4683">[ thread ]</a>
+ <a href="subject.html#4683">[ subject ]</a>
+ <a href="author.html#4683">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Sat, 15 Sep 2012, Thomas Backlund wrote:
+
+&gt;<i> nicolas vigier skrev 15.9.2012 17:51:
+</I>&gt;&gt;<i> On Sat, 15 Sep 2012, <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">root at mageia.org</A> wrote:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> red Sat Sep 15 16:26:57 CEST 2012 - Filesystems NOT ok
+</I>&gt;&gt;&gt;<i> &amp;red /tmp (100% used) has reached the PANIC level (95%)
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Filesystem 1024-blocks Used Available Capacity Mounted on
+</I>&gt;&gt;&gt;<i> /dev/md0 20152044 10375432 8752928 55% /
+</I>&gt;&gt;&gt;<i> /dev/sda1 1004024 92956 860064 10% /boot
+</I>&gt;&gt;&gt;<i> /dev/sdb1 1004024 92792 860228 10% /boot2
+</I>&gt;&gt;&gt;<i> /dev/mapper/vg0-tmp 32640904 30979996 2868 100% /tmp
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> It seems /tmp was full because of rpmlint temporary files. Maybe because
+</I>&gt;&gt;<i> we had a few kernel packages finishing build at the same time ?
+</I>&gt;&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> Probably yes....
+</I>&gt;<i>
+</I>&gt;<i> As for pushing all kernels at the ~same time was intentional this time...
+</I>&gt;<i>
+</I>&gt;<i> I wanted to see how the BS would handle max load now that new
+</I>&gt;<i> ecosse is working too (as kernel builds do manage to max out
+</I>&gt;<i> buildnodes due to good support for parallel builds)
+</I>&gt;<i>
+</I>&gt;<i> But I didn't even think about valstar getting into trouble :/
+</I>&gt;<i>
+</I>&gt;<i> core kernel is the worst one for rpmlint as all rpms +
+</I>&gt;<i> their unpacked contents need ~20+ GB diskspace (every
+</I>&gt;<i> kernel-*-debug needs some 2+ GB) ....
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> But otoh I think it was nice side-effect to identify a SPOF
+</I>&gt;<i> now (instead of release time) so we can get it fixed...
+</I>
+Yes.
+
+&gt;<i>
+</I>&gt;<i> question is... do we somehow need to limit how many rpmlint
+</I>&gt;<i> processes is started (depending on cpu load or free disk space
+</I>&gt;<i> in /rmp), or should we just hope the extra disk space is enough ?
+</I>
+Maybe youri could check if there is enough space on /tmp before
+attempting to run rpmlint on the package.
+
+&gt;<i>
+</I>&gt;<i> Because load on the server was too high, I killed all rpmlint processes,
+</I>&gt;&gt;<i> and removed all rpmlint temporary files in /tmp.
+</I>&gt;&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> So whah happend to the packages being rpmlinted ? did they get uploaded
+</I>&gt;<i> anyway ?
+</I>
+Yes. Actually they were already listed as uploaded on pkgsubmit when I
+killed the rpmlint processes. I don't know why there still was rpmlint
+process running when the package was already uploaded.
+
+</PRE>
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="004682.html">[Mageia-sysadm] [sysadmin-reports] Hobbit [727252] valstar.mageia.org:disk CRITICAL (RED)
+</A></li>
+ <LI>Next message: <A HREF="004684.html">[Mageia-sysadm] [sysadmin-reports] Hobbit [727252] valstar.mageia.org:disk CRITICAL (RED)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4683">[ date ]</a>
+ <a href="thread.html#4683">[ thread ]</a>
+ <a href="subject.html#4683">[ subject ]</a>
+ <a href="author.html#4683">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
+mailing list</a><br>
+</body></html>