- 论坛徽章:
- 0
|
本帖最后由 cduedu 于 2011-02-11 09:58 编辑
操作系统是SUSE 10SP3,在节前对服务器正电的时候采用的是维护界面的power off功能。昨天启动的时候能正常启动,但启动后发现所有的文件系统都为只读不可写。
查看启动日志,未发现任何错误。并且在启动过程中是有日志的更新的,也就是说在启动过程中文件系统是可写的,但启动好后就变成了只读。用mount看,所有的挂载点都是RW,不知道问题出在那里,不知道各位 有没有遇到过这种情况- cdn-35:~ # df -h
- Filesystem Size Used Avail Use% Mounted on
- /dev/sda2 74G 4.3G 66G 7% /
- udev 2.0G 148K 2.0G 1% /dev
- /dev/sda3 992G 27G 915G 3% /opt
- cdn-35:~ # mount
- /dev/sda2 on / type ext3 (rw,acl,user_xattr)
- proc on /proc type proc (rw)
- sysfs on /sys type sysfs (rw)
- debugfs on /sys/kernel/debug type debugfs (rw)
- udev on /dev type tmpfs (rw)
- devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
- /dev/sda3 on /opt type ext3 (rw,acl,user_xattr)
- securityfs on /sys/kernel/security type securityfs (rw)
- cdn-35:~ # cd /tmp/
- cdn-35:/tmp # touch test
- touch: cannot touch `test': Read-only file system
复制代码 刚才查了一下,原来真的是文件系统的一些块坏了:- EXT3-fs error (device sda2): ext3_free_blocks_sb: bit already cleared for block 3711234
- Aborting journal on device sda2.
- ext3_abort called.
- EXT3-fs error (device sda2): ext3_journal_start_sb: Detected aborted journal
- Remounting filesystem read-only
- EXT3-fs error (device sda2) in ext3_reserve_inode_write: Journal has aborted
- EXT3-fs error (device sda2) in ext3_reserve_inode_write: Journal has aborted
- EXT3-fs error (device sda2) in ext3_orphan_del: Journal has aborted
- __journal_remove_journal_head: freeing b_committed_data
复制代码 现在要怎么修复啊?
根据日志信息,使用fsck /dev/sda2 进行修复后。重启系统,文件系统恢复正常 |
|