1 Oct 2011 19:39
mondo_tmp
madunix <at> gmail.com <madunix <at> gmail.com>
2011-10-01 17:39:09 GMT
2011-10-01 17:39:09 GMT
I keep seeing this on my server mondo.tmp, Can I remove it safely?
[root <at> server ~]# df -kh
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
518G 147G 345G 30% /
/dev/sda1 99M 27M 68M 29% /boot
tmpfs 3.9G 0 3.9G 0% /dev/shm
/dev/shm 350M 0 350M 0% /mondo.tmp.OzlYPx/tmpfs
-pons
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
Well, yes, I succeded to mondoarchive my Ubuntu 11.04, on a USB hard disk.
I used Mondo Archive v2.2.9.6-r2760, Mindi v2.0.7.7-r2760 and Mindi-BusyBox v1.18.3.
The only problems were:
* syslinux --s (solved by syslinus --stupid),
and
* EXTRA_SPACE and BOOT_SIZE parameters (solved by EXTRA_SPACE=80152 and BOOT_SIZE=32768).
I have to try with the latest versions, to see if I get the same problem than your.
Your df results are not easy to read, could you post it in a file, in attachment ?
Rgds,
Victor
-----Original Message-----
From: Steffen Hulegaard [mailto:shulegaa <at> yahoo.com]
Sent: lundi 3 octobre 2011 17:36
To: Gattegno, Victor (GCC - Software); Mondo mailing list
Subject: Re: [Mondo-devel] Ubuntu 11.04 mondoarchive FAIL - leaves /dev/loop0 mounted? Runs out of space?
Victor Gattegno rocks! Thanks again for your amazingly quick response.
In a determined effort to get mondoarchive working on Ubuntu 11.04, I'm now
working with a relatively new, scratch install of Ubuntu 11.04. I do have those
'proper' EXTRA_SPACE and BOOT_SIZE values in my /usr/sbin/mindi script.
I'll attach my /usr/bin/mindi - and I'll reattach the mondo/mini log files again ...
just for ease of reference.
I really appreciate all the time and attention paid to my trials and tribulations.
Should I try bumping up my EXTRA_SPACE and BOOT_SIZE parameters
(in /usr/bin/mindi) even more? If so, how much?
I saw FAQ Q#17 as well. Great point! Not surprisingly, my df output *does*
show tons of *both* inodes and free space:
#df -iah
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda1 58M 360K 58M 1% /
proc 0 0
0 - /proc none
0 0 0 - /sys
fusectl 0 0
0 - /sys/fs/fuse/connections
none 0 0
0 - /sys/kernel/debug none
0 0 0 - /sys/kernel/security
none 999K 1003 998K 1% /dev
none 0 0
0 - /dev/pts none 1001K
28 1001K 1% /dev/shm none
1001K 70 1001K 1% /var/run
none 1001K 2 1001K 1%
/var/lock binfmt_misc 0 0
0 - /proc/sys/fs/binfmt_misc gvfs-fuse-daemon
0 0 0 - /root/.gvfs
gvfs-fuse-daemon 0 0 0 - /home/schulegaard/.gvfs
/dev/sdc1 117M 43 117M 1% /mnt/usb1_1
/dev/sdc2 59M 1.5M 57M 3% /mnt/usb1_2
/dev/sdb1 59M 11 59M 1% /mnt/work
# df -ah
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 910G 11G 853G 2% /
proc 0 0 0
- /proc none 0 0
0 - /sys fusectl 0 0
0 - /sys/fs/fuse/connections
none 0 0 0 -
/sys/kernel/debug none 0 0
0 - /sys/kernel/security none
4.0G 740K 3.9G 1% /dev none 0
0 0 - /dev/pts none 4.0G
1.3M 4.0G 1% /dev/shm none 4.0G 248K
4.0G 1% /var/run none 4.0G 0
4.0G 0% /var/lock binfmt_misc 0 0 0
- /proc/sys/fs/binfmt_misc gvfs-fuse-daemon 0 0
0 - /root/.gvfs gvfs-fuse-daemon 0.0K 0.0K 0.0K - /home/schulegaard/.gvfs
/dev/sdc1 1.8T 8.8G 1.8T 1% /mnt/usb1_1
/dev/sdc2 917G 295G 623G 33% /mnt/usb1_2
/dev/sdb1 917G 200M 917G 1% /mnt/work
While I no zilch (or less) about the inner-workings of mondoarchive, if I had to hazard a very
ignorant guess (... contrary to my better judgement), I'd wonder about the /dev/loop0 device that
mondoarchive left mounted (on /tmp/≤something>). From the email thread below:
/dev/loop0 118995 1538 116188
2% /tmp/mondo.tmp.15Er7D/mnt1
That is a pretty small filesystem! By process of elimination, I've been guessing that this
might be the device triggering the "write error: No space left on device" error.
Either that, or perhaps there are time outs afflicting by 'sync' mounted, external USB drive
partitions (e.g. /dev/sdc1 and /dev/sdc2). Of course, I'm just wildly grasping at straws. I already
tried to -E exclude these anyway - just in case.
From my clueless perspective, it is just as likely that this particular error message is somehow
misleading (... about the true nature/cause of the error). Are you able to run mondoarchive on an Ubuntu
11.04 box?
I'm really at a loss. The help on mond-devel <at> lists.sourceforge.net is *awesome* - but I feel
more and more like a noob.
Worried, Steffen
________________________________
From: "Gattegno, Victor (GCC - Software)" <victor_gattegno <at> hp.com>
To: Steffen Hulegaard <shulegaa <at> yahoo.com>; Mondo mailing list <mondo-devel <at> lists.sourceforge.net>
Sent: Monday, October 3, 2011 7:18 AM
Subject: RE: [Mondo-devel] Ubuntu 11.04 mondoarchive FAIL - leaves /dev/loop0 mounted? Runs out of space?
Hi Steffen,
In your log I see a lot of "write error: No space left on device".
EXTRA_SPACE value was already increased in /usr/sbin/mindi (and tested) in order to avoid that problem
with Ubuntu.
Normally you see, in your /usr/sbin/mindi:
EXTRA_SPACE=80152
BOOT_SIZE=32768
So, if you already have these values in your /usr/sbin/mindi, it could be an inode problem, check Mondo
Rescue FAQ #Q17.
Regards,
Victor
-----Original Message-----
From: Steffen Hulegaard [mailto:shulegaa <at> yahoo.com]
Sent: vendredi 30 septembre 2011 22:01
To: mondo-devel <at> lists.sourceforge.net
Subject: [Mondo-devel] Ubuntu 11.04 mondoarchive FAIL - leaves /dev/loop0 mounted? Runs out of space?
Despite Victor Gattegno's prompt, detailed and *most* helpful reply, Somehow, I still do not
have the knack for running mondoarchive on Ubuntu 11.04. I did follow the Mondo Rescue FAQ Q#11 (see
RSS Feed