Hi,
Did the reboot yesterday and after that all was fine.....I didn't need to
use the console..it just came back up....
Today it happened again..Read Only File System
Should I just reboot again?
I don't have access to the console panel....and I am not near the data
center.
Regards,
Mitch
The /proc/mdstat shows that your disks are still mirrored, and there are not
any messages in dmesg about hardware issues, so you likely have some minor
corruption on the filesystem.
I recomend you backup your data, then re-boot.
the re-boot will run the fsck program automatically that will clean the
filesystem and fix the error noted.
WARNING!!! THIS CAN CAUSE DATA TO BE LOST!!!!
but you don't have much of a choice in fixing it.
You will need console access, as the system will likely ask you to confirm
Yes or No as it is fixing items.
Make sure you have a backup before doing this.
If you re-mount the filesystem as noted above, it can likely cause more
issues, as the underlying filesystem is not happy.
-Adam
On 4/19/07, Mitchell Rothschild <mjr (at mark) misswebhost.com> wrote:
> Hello,
>
> I do not know much about mounting...but can I use this command to
> remount the file system so it is not in read only mode?
>
> mount -no remount,rw /
> or
> mount -o remount,rw /
>
> not sure what the exact command is..
>
> Is this the next smart step to proceed with?
>
>
> > Filesystem Size Used Avail Use% Mounted on
> > /dev/md1 6.0G 875M 4.8G 16% /
> > /dev/md6 99M 20M 75M 21% /boot
> > none 1013M 0 1013M 0% /dev/shm
> > /dev/md4 99G 12G 82G 13% /home
> > /dev/md2 1012M 34M 927M 4% /tmp
> > /dev/md3 4.0G 551M 3.2G 15% /var
>
> Hi,
>
> Thanks...
> This is some of what I get from dmesg..
>
> TCP: Treason uncloaked! Peer 207.105.34.2:39897/80 shrinks window
> 1990054351:1990057248. Repaired.
> TCP: Treason uncloaked! Peer 207.105.34.2:40168/80 shrinks window
> 2000741566:2000743084. Repaired.
> EXT3-fs error (device md4): ext3_readdir: directory #3817571 contains
> a hole at offset 4096 Aborting journal on device md4.
> EXT3-fs error (device md4): ext3_readdir: directory #3817571 contains
> a hole at offset 8192 EXT3-fs error (device md4): ext3_readdir:
> directory #3817571 contains a hole at offset 12288 EXT3-fs error (device
md4): ext3_readdir:
> directory #3817571 contains a hole at offset 16384 EXT3-fs error
> (device
> md4): ext3_readdir:
> directory #3817571 contains a hole at offset 20480 EXT3-fs error
> (device
> md4): ext3_readdir: directory #3817571
>
> #3817571 contains a hole at offset 319488 EXT3-fs error (device md4):
> ext3_readdir: directory #3817571 contains a hole at offset 323584
> EXT3-fs error (device md4): ext3_readdir: directory #3817571 contains
> a hole at offset 327680 EXT3-fs error (device md4) in
> start_transaction: Journal has aborted
> TCP: Treason uncloaked! Peer 63.147.152.184:61200/80 shrinks window
> 366474174:366481639. Repaired.
>
>
> This is what I get from cat /proc/mdstat
>
> cat /proc/mdstat
> Personalities : [raid1]
> md6 : active raid1 sdb1[1] sda1[0]
> 104320 blocks [2/2] [UU]
>
> md3 : active raid1 sdb3[1] sda3[0]
> 4192896 blocks [2/2] [UU]
>
> md5 : active raid1 sdb5[1] sda5[0]
> 1052160 blocks [2/2] [UU]
>
> md2 : active raid1 sdb6[1] sda6[0]
> 1052160 blocks [2/2] [UU]
>
> md4 : active raid1 sdb7[1] sda7[0]
> 104526784 blocks [2/2] [UU]
>
> md1 : active raid1 sdb2[1] sda2[0]
> 6289344 blocks [2/2] [UU]
>
> unused devices: <none>
>
>
> run the command 'dmesg' and see what it says.
>
> it is likely that there is some sort of error with your file system
> and the kernel has marked the file system read-only to protect it from
damage.
>
> The root cause of this sort of thing is usually hardware failure.
> since you are using md, also run a 'cat /proc/mdstat' to see what
> state the system thinks the disks are in.
>
> of course be paranoid, and take a good backup.
>
> -Adam
>
> On 4/19/07, Mitchell Rothschild <mjr (at mark) misswebhost.com> wrote:
> > Hi,
> >
> > Hope all is well with everyone...
> >
> > I have an error today...and some mysql sites are not working.
> > When I try to move or copy files I get an error...
> > Read-only file system
> >
> > How can I fix this?
> >
> > Thanks in advance.
> >
> >
> >
>
>
> --
> -----------------------------------------------------------------
> Shroom.net Donation Based Web Hosting
> http://www.shroom.net/
> -----------------------------------------------------------------
>
>
>
>
--
-----------------------------------------------------------------
Shroom.net Donation Based Web Hosting
http://www.shroom.net/
-----------------------------------------------------------------