[Systems] disk space fluctiation on freedom Fwd: freedom.sugarlabs.org-Munin_alert
Sam P.
sam.parkinson3 at gmail.com
Tue May 5 17:41:36 EDT 2015
Yes, no reboot is needed.
Thanks,
Sam
On Wed, May 6, 2015 at 2:26 AM Stefan Unterhauser <dogi at sugarlabs.org>
wrote:
> Hi,
>
> On Tue, May 5, 2015 at 2:57 AM, Sam P. <sam.parkinson3 at gmail.com> wrote:
>
>> Hi,
>>
>> I don't think we need a restart.
>>
>> I was able to use "/proc/*/mounts" as James suggested to kill all the old
>> docker processes. "sudo service docker kill" did not do a very good job of
>> shutting down cleanly! I have now reformatted the docker partition and
>> updated docker so hopefully it will all get back up and running very soon!
>>
>> awesome :) sounds like you got it ...
> let me just reconfirm there is no reboot of freedom necessary. Right?
>
>
>
>> Adding more drives to justice sounds like a very good idea :)
>>
>> Thanks,
>> Sam
>>
>> On Tue, May 5, 2015 at 2:47 PM Stefan Unterhauser <dogi at sugarlabs.org>
>> wrote:
>>
>>> On Mon, May 4, 2015 at 11:41 PM, Bernie Innocenti <bernie at codewiz.org>
>>> wrote:
>>>
>>>> +dogi
>>>>
>>>> On 04/05/15 17:21, James Cameron wrote:
>>>>
>>>>> On Mon, May 04, 2015 at 02:14:26PM -0700, Sam Parkinson wrote:
>>>>>
>>>>>> However, it is creating many issues because when running
>>>>>> "mkfs.btrfs" on the lvm mapper file it says it is busy. When it is
>>>>>> mounted, lsof and fuser don& apos;t report any users though :(
>>>>>>
>>>>>
>>>>> There's still a reference to the mapper.
>>>>>
>>>>> Filesystem mounts, not being tracked by file descriptors, are a common
>>>>> cause of this symptom. There's probably a tool for finding them, but
>>>>> my method is to look for processes that might own the mount, or
>>>>> perhaps check /proc/*/mounts.
>>>>>
>>>>> When time is short, there's nothing like an "i'm defeated" reboot.
>>>>>
>>>>
>>>> Ok to reboot, but please wait until an week day afternoon (EDT), so in
>>>> case something goes badly wrong I can run to the media lab to fix things.
>>>>
>>>> Don't worry will go to reboot freedom in person tomorrow
>>> Hope that is OK with you guys
>>>
>>> reason:
>>> freedom got rebooted in the last 4 year exactly 2 times :)
>>> once before docker and and the other time with bernie as we upgraded to
>>> docker ;)
>>> -> a really stable system :D
>>>
>>> so compared to justice which gets rebooted every 3 months where we know
>>> it will just go fine, with rebooting freedom I am a little bit ... you know
>>> ... uneasy/protective ;)
>>>
>>>
>>>
>>>> Last friday I made more room in /backup by moving historic backups to
>>>> justice and deleting the oldest backups snapshots of sunjammer, but at this
>>>> rate it will fill by the end of this week.
>>>>
>>>> Dogi was in the process of migrating some large VMs related to OLE in
>>>> order to free up some space on freedom. Dogi, how long will it take?
>>>>
>>>> I just freed some 400G on or for backupLV 3 weeks ago,
>>> right now ~50% of all the space is used for backups
>>> so please give me some air here ... ;)
>>>
>>> my advise for fast relieve of the backup problem:
>>> is to fill the 2 empty slots on justice with two big drives ...
>>>
>>> xo
>>> dogi
>>>
>>>
>>>> --
>>>> _ // Bernie Innocenti
>>>> \X/ http://codewiz.org
>>>>
>>>
>> _______________________________________________
>> Systems mailing list
>> Systems at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/systems
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/private/systems/attachments/20150505/eaec87cb/attachment.html>
More information about the Systems
mailing list