<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Luis,<br></div><div><br></div><div>The deleted files which are still open don't have to be apt cache files. They can be data or executable files from the application that was updated. In my experience, if you can't "remountro" after an upgrade, it would be best to reboot.<br></div><div><br></div><div>And yes, a value of "1" means a filesystem is =always= checked when the box is rebooted.<br></div><div>--<br>Julie Haugh<br>Senior Design Engineer<br>greenHouse Computers, LLC // jfh at <a href="http://greenhousepc.com">greenhousepc.com</a> // greenHousePC on Skype</div><div><br><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [Voyage-linux] when remountro fails<br>
From: tictacbum <<a href="mailto:tictacbum@gmail.com">tictacbum@gmail.com</a>><br>
Date: Thu, February 02, 2012 1:27 am<br>
To: <a href="mailto:jfh@greenhousepc.com">jfh@greenhousepc.com</a><br>
Cc: <a href="mailto:voyage-linux@voyage.hk">voyage-linux@voyage.hk</a><br>
<br>
Hello,<br>
this also fits my case, as I always do an apt-get clean after<br>
upgrading, to free space<br>
I tried to install some small packages again, then apt-get clean, but<br>
remountro problem didn't appeared<br>
will do a "lsof | grep apt" next time I can't remountro to see if<br>
there's some apt cache files still open.<br>
<br>
about fsck, a value of 1 will check the filesystem on every boot, is<br>
this necessary given that it is always mounted ro?<br>
<br>
regards,<br>
Lluís<br>
<br>
On Thu, Feb 2, 2012 at 6:32 AM, <<a href="mailto:jfh@greenhousepc.com">jfh@greenhousepc.com</a>> wrote:<br>
> Greets,<br>
><br>
> In my experience, a common reason you can't remount read-only is because a<br>
> file has been deleted and is still open.<br>
><br>
> As regards the "other" problems -- you need to set the maximum mount-count<br>
> between fsck's to 1 and the error handling to "remount-ro" with tune2fs.<br>
> --<br>
> Julie Haugh<br>
> Senior Design Engineer<br>
> greenHouse Computers, LLC // jfh at <a href="http://greenhousepc.com">greenhousepc.com</a> // greenHousePC on<br>
> Skype<br>
><br>
><br>
> -------- Original Message --------<br>
> Subject: Re: [Voyage-linux] when remountro fails<br>
> From: tictacbum <<a href="mailto:tictacbum@gmail.com">tictacbum@gmail.com</a>><br>
> Date: Wed, February 01, 2012 3:58 pm<br>
> To: <a href="mailto:voyage-linux@voyage.hk">voyage-linux@voyage.hk</a><br>
><br>
> Hi,<br>
> I've taken the compact flash and did a fsck -f (filesystem was clean)<br>
> left filesystem mounted rw about an hour and remounted ro without<br>
> trouble, seems fsck helped :)<br>
> thank you!<br>
><br>
> On Wed, Feb 1, 2012 at 9:24 PM, Frank Hoeflich <<a href="mailto:frankhoeflich@yahoo.com">frankhoeflich@yahoo.com</a>><br>
> wrote:<br>
>> Lluís:<br>
>><br>
>> This happened to my Voyage 0.6.5 and 0.7.5 virtual machines when they<br>
>> were taken down unceremoniously. I was ultimately obliged to boot the<br>
>> Voyage SDK iso, run a filesystem check to repair the Voyage installation on<br>
>> my hard drive, and then boot from hard disk again. At the end everything<br>
>> was reasonably OK - I did lose a few inodes - but I could<br>
>> remountrw/remountro once again without the annoying / is busy message.<br>
>><br>
>> Give it a shot<br>
>><br>
>> --Frank<br>
>><br>
>> --- On Wed, 2/1/12, tictacbum <<a href="mailto:tictacbum@gmail.com">tictacbum@gmail.com</a>> wrote:<br>
>><br>
>>> From: tictacbum <<a href="mailto:tictacbum@gmail.com">tictacbum@gmail.com</a>><br>
>>> Subject: [Voyage-linux] when remountro fails<br>
>>> To: <a href="mailto:voyage-linux@voyage.hk">voyage-linux@voyage.hk</a><br>
>>> Date: Wednesday, February 1, 2012, 11:58 AM<br>
>>> Hello,<br>
>>> I have a voyage 0.8 installation, sometimes when I try to<br>
>>> remountro it<br>
>>> fails showing "/ is busy", specially if I had it mounted rw<br>
>>> for a<br>
>>> while (for example to apt-get upgrade)<br>
>>> when I get this I try to stop all services running, until I<br>
>>> don't know<br>
>>> what more to stop, ps aux is almost empty, and I can't<br>
>>> recognize any<br>
>>> process to stop with lsof<br>
>>> I tryed to stop sshd and login from terminal too, finally<br>
>>> what I do is<br>
>>> a reboot...<br>
>>> how can I find which process keeps / busy?<br>
>>><br>
>>> regards,<br>
>>> Lluís<br>
>>><br>
>>> _______________________________________________<br>
>>> Voyage-linux mailing list<br>
>>> <a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>
>>> <a href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
>>><br>
><br>
> _______________________________________________<br>
> Voyage-linux mailing list<br>
> <a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>
> <a href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
</div>
</blockquote></span></body></html>