[juneau-lug] Re: Recent power outage problems

  • From: bdk <bdk@xxxxxxxxxxxxxx>
  • To: juneau-lug@xxxxxxxxxxxxx
  • Date: Wed, 21 May 2003 22:36:02 -0800

The problem seemed to be w/ the file system and not the database. After 
rebooting everything worked, and the databases came back alive. Now I'm 
running into some more permission problems, not able to create new dirs 
in '/usr/local', because now that is a read-only file system. Rebooting 
to see if that'll clear it up again.

It did.

Anyone else experiencing their file systems being locked in read-only?

-sean

jeremyh@xxxxxxx wrote:

>Have you tried repairing the DB, I have had similar problems after a power 
>outage but have always recovered.
>
>Jer
>
>----- Original Message -----
>From: bdk <bdk@xxxxxxxxxxxxxx>
>Date: Wednesday, May 21, 2003 8:23 pm
>Subject: [juneau-lug] Recent power outage problems
>
>  
>
>>As a result of the recent power outage, I'm unable to load MySQL. 
>>I 
>>couldn't understand where it was erroring so I reinstalled it, and 
>>now I 
>>think I know how come it isn't loading.
>>
>>When I try to install the default databaes 
>>(scripts/mysql_install_db), 
>>mysql tells me:
>>
>>- scripts/mysql_install_db: cannot create temp file for here 
>>document: 
>>Read-only file system
>>- Installation of grant tables failed!
>>
>>I did some looking in the MySQL manual. For some reason I'm unable 
>>to 
>>write to my '/tmp'. I checked and '/tmp' is setup w/ the right 
>>modes 
>>(1777). When I reset the mode 'chmod 1777 /tmp', chmod sets them 
>>but 
>>tells me that '/tmp' is a ready-only file system. I can't create 
>>or even 
>>copy a file to '/tmp'. Vi won't let me save and cp tells me:
>>
>>- Osok:/home/bdk# cp test.123 /tmp
>>- cp: cannot create regular file `/tmp/test.123': Read-only file 
>>system
>>Is '/tmp' suppose to be a ready-only? How do I unread-only '/tmp'? 
>>Things were working just fine before the power outage.
>>
>>My Microsoft lobe suggested that I try rebooting the machine to 
>>see if 
>>that would clear the problem.
>>
>>2 minutes later.
>>
>>Problem cleared.
>>
>>Anyone know why '/tmp' would be write protected?
>>
>>-- 
>>----BEGIN GEEK CODE BLOCK----
>>Version 3.1
>>GIT d+>! s+:++ a->? C++++ ULU++++>$ P+>++++ L+++>++++>$ E--- W+++ 
>>N++ o? K- w--- !O M-- V PS PE++ Y++ PHP++(+++) t-- 5- X++ R++ tv++ 
>>b++>+++ DI++ D++ G e* h++ r+++ y+++*>++++
>>-----END GEEN CODE BLOCK-----
>>
>>
>>
>>------------------------------------
>>This is the Juneau-LUG mailing list.
>>To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx 
>>with the word unsubscribe in the subject header.
>>
>>    
>>
>
>
>------------------------------------
>This is the Juneau-LUG mailing list.
>To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx with the 
>word unsubscribe in the subject header.
>
>  
>

-- 
----BEGIN GEEK CODE BLOCK----
Version 3.1
GIT d+>! s+:++ a->? C++++ ULU++++>$ P+>++++ L+++>++++>$ E--- W+++ N++ o? K- 
w--- !O M-- V PS PE++ Y++ PHP++(+++) t-- 5- X++ R++ tv++ b++>+++ DI++ D++ G e* 
h++ r+++ y+++*>++++
-----END GEEN CODE BLOCK-----



------------------------------------
This is the Juneau-LUG mailing list.
To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx with the 
word unsubscribe in the subject header.

Other related posts: