[Voyage-linux] when remountro fails

[tictacbum]

Hello,
this also fits my case, as I always do an apt-get clean after
upgrading, to free space
I tried to install some small packages again, then apt-get clean, but
remountro problem didn't appeared
will do a "lsof | grep apt" next time I can't remountro to see if
there's some apt cache files still open.

about fsck, a value of 1 will check the filesystem on every boot, is
this necessary given that it is always mounted ro?

regards,
Lluís

On Thu, Feb 2, 2012 at 6:32 AM,  <jfh at greenhousepc.com> wrote:
> Greets,
>
> In my experience, a common reason you can't remount read-only is because a
> file has been deleted and is still open.
>
> As regards the "other" problems -- you need to set the maximum mount-count
> between fsck's to 1 and the error handling to "remount-ro" with tune2fs.
> --
> Julie Haugh
> Senior Design Engineer
> greenHouse Computers, LLC // jfh at greenhousepc.com // greenHousePC on
> Skype
>
>
> -------- Original Message --------
> Subject: Re: [Voyage-linux] when remountro fails
> From: tictacbum <tictacbum at gmail.com>
> Date: Wed, February 01, 2012 3:58 pm
> To: voyage-linux at voyage.hk
>
> Hi,
> I've taken the compact flash and did a fsck -f (filesystem was clean)
> left filesystem mounted rw about an hour and remounted ro without
> trouble, seems fsck helped :)
> thank you!
>
> On Wed, Feb 1, 2012 at 9:24 PM, Frank Hoeflich <frankhoeflich at yahoo.com>
> wrote:
>> Lluís:
>>
>>    This happened to my Voyage 0.6.5 and 0.7.5 virtual machines when they
>> were taken down unceremoniously.  I was ultimately obliged to boot the
>> Voyage SDK iso, run a filesystem check to repair the Voyage installation on
>> my hard drive, and then boot from hard disk again.  At the end everything
>> was reasonably OK - I did lose a few inodes - but I could
>> remountrw/remountro once again without the annoying / is busy message.
>>
>>    Give it a shot
>>
>> --Frank
>>
>> --- On Wed, 2/1/12, tictacbum <tictacbum at gmail.com> wrote:
>>
>>> From: tictacbum <tictacbum at gmail.com>
>>> Subject: [Voyage-linux] when remountro fails
>>> To: voyage-linux at voyage.hk
>>> Date: Wednesday, February 1, 2012, 11:58 AM
>>> Hello,
>>> I have a voyage 0.8 installation, sometimes when I try to
>>> remountro it
>>> fails showing "/ is busy", specially if I had it mounted rw
>>> for a
>>> while (for example to apt-get upgrade)
>>> when I get this I try to stop all services running, until I
>>> don't know
>>> what more to stop, ps aux is almost empty, and I can't
>>> recognize any
>>> process to stop with lsof
>>> I tryed to stop sshd and login from terminal too, finally
>>> what I do is
>>> a reboot...
>>> how can I find which process keeps / busy?
>>>
>>> regards,
>>> Lluís
>>>
>>> _______________________________________________
>>> Voyage-linux mailing list
>>> Voyage-linux at list.voyage.hk
>>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>>
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux