File system locked on upgrade

[Derek Broughton]

David S Angulo wrote:

> On Thu, Jul 16, 2009 at 2:26 PM, Derek Broughton<derek at pointerstop.ca>
> wrote:
>>
>> fsck.
> 
> 
> Are you saying I should run fsck?

Are you reading impaired?  OK, it was terse, but what else _could_ it mean?  

>> How do you think it got mounted read-only?
> 
> 
> Is that a rhetorical question or did you want me to answer it?
> 
> If you wanted me to answer it, then I reall do not know how it got
> mounted read-only.
> 
> If it is rhetorical, then I don't know.  That's why I'm asking.  Could
> you tell me what you think happened?
> 
> 
>>As the fstab says
>> "errors=remount-ro".

What part of that is unobvious?  It SAYS: on error, remount read-only.  
Since both of us are probably sure you didn't explicitly remount it, Ockam's 
razor suggests this is what caused it.

>> Why are you still using ext2?  It really isn't smart, and it's so easy to
>> add a journal and turn it into ext3 (see tune2fs).  Then if you manage to
>> turn off the machine without properly shutting down, it'll be able to
>> recover properly.
> 
> OK, I'll look into this.  Is this why it's mounted read-only?  

Probably.  We can't really tell, but it's always the most likely reason, and 
the only acceptable reason to not use a journalling filesystem these days is 
if the filesystem is _supposed_ to be read-only.
-- 
derek