You are not logged in.
I don't know if this was caused by an update but suddently my /raid is mounted read-only. It doesn't happen right after the mount but suddently after 1 day of uptime or a few hours and the /raid partition is locked again.
[dezza@dezza ~]$ cd /raid/
[dezza@dezza raid]$ touch me
touch: cannot touch `me': Read-only file system
[dezza@dezza raid]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 34G 13G 22G 38% /
none 1013M 0 1013M 0% /dev/shm
/dev/sda3 46M 12M 32M 27% /boot
/dev/md0 466G 364G 103G 79% /raid
[dezza@dezza raid]$ cat /etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options
> <dump> <pass>
none /dev/pts devpts defaults
0 0
none /dev/shm tmpfs defaults
0 0
# Optical drive, CD/DVD
/dev/sr0 /media iso9660,udf ro,user,
noauto,unhide 0 0
# Root, swap, boot
/dev/disk/by-label/root / reiserfs defaults
0 1
/dev/disk/by-label/swap swap swap defaults
0 0
/dev/disk/by-label/boot /boot ext2 defaults
0 1
# RAiD BACKUP (2x 500GB Western Digital 7200RPM)
/dev/md0 /raid reiserfs defaults
,sync,user 0 0
#
# External 1TB
/dev/disk/by-label/external /mnt/1tb ntfs-3g u
ser,sync,exec,uid=1000,gid=1000,locale=en_DK.utf8,force,noauto 0 0
# VirtualBox
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=0664,lo
cale=en_DK.utf8 0 0
[dezza@dezza raid]$
Last edited by dezza (2009-08-24 14:42:13)
Offline
I had the same problem with a hardware RAID array... I was installing Arch in an previously Redhat server.
The error I got just just before the read-only thing was related to the filesystem... (Arch was in reiserfs and /home in Redhat is ext3)
That read-only thing only happened when I was performing heavy load on the raid by rsyncing almost 300GB from RH to the new arch (No error while installing and configure a very complete system).
I though maybe it was that reiserfs wasn't good enough and I tried with no luck using jfs (the same I succesfully use in LVM in my laptop).
At the end I decided to get rid of the filesystem difference and It worked using ext3.
It worked perfectly for almost a month until last week that we had a crash copying 180GB from an USB external drive. We tried again and it worked with no problems. So in conclusion:
I used ext3 successfully but I have one crashed (after the read-only thing the system becomes useless) documented.
I know this is not an answer but I hope this help you or maybe help someone to give us a point.
P.S: The raid arrays are in the same computer (PERC6 I think) using the aacraid driver. One is raid 5 (RH) and the other one is RAID 0 (Arch),
Offline
Is this a problem caused by software RAID in Linux or ReiserFS can anyone confirm this?
I have a problem with backup since I'll have to re-order my disks, but I have 2TB not even unpackaged, 1TB in external (filled), 2x500GB RAID1 but I should lean towards a more decent filesystem. I did know reiserfs was not the best but alot happens with fs' now that it's hard to make a decision with something you doesn't know.
No one knows how to prevent/fix this?
Last edited by dezza (2009-08-24 22:47:56)
Offline
REISERFS error (device md0): vs-4080 _reiserfs_free_block: block 77178145: bit already cleared
REISERFS (device md0): Remounting filesystem read-only
REISERFS error (device md0): vs-4080 _reiserfs_free_block: block 77178139: bit already cleared
REISERFS error (device md0): vs-4080 _reiserfs_free_block: block 77178135: bit already cleared
REISERFS error (device md0): vs-4080 _reiserfs_free_block: block 77178125: bit already cleared
REISERFS error (device md0): vs-4080 _reiserfs_free_block: block 77178119: bit already cleared
REISERFS error (device md0): vs-4080 _reiserfs_free_block: block 77178115: bit already cleared
I found something on dmesg that might enlighten this issue.
Doing reiserfsck and reiserfsck --fix-fixable.
AKA. Never Reiserfs again ..
Last edited by dezza (2010-02-25 02:57:22)
Offline