HDS AMS100盘柜故障

洛阳服务器盘柜分区报错

message错误日志

[root@HNTX-LY-PCMS log]# cat messages | grep EXT3-fs
Jan 17 08:10:08 HNTX-LY-PCMS kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jan 17 08:10:08 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 17 08:10:08 HNTX-LY-PCMS kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jan 17 08:10:08 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 18 08:10:07 HNTX-LY-PCMS kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jan 18 08:10:07 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 18 08:10:07 HNTX-LY-PCMS kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jan 18 08:10:07 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 08:10:08 HNTX-LY-PCMS kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jan 19 08:10:08 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 08:10:08 HNTX-LY-PCMS kernel: EXT3-fs error (device sdb1): ext3_check_descriptors: Block bitmap for group 384 not in group (block 3120627712)!
Jan 19 08:10:08 HNTX-LY-PCMS kernel: EXT3-fs: group descriptors corrupted !
Jan 19 08:54:11 HNTX-LY-PCMS kernel: EXT3-fs error (device sdb1): ext3_check_descriptors: Block bitmap for group 384 not in group (block 3120627712)!
Jan 19 08:54:11 HNTX-LY-PCMS kernel: EXT3-fs: group descriptors corrupted !
Jan 19 08:54:30 HNTX-LY-PCMS kernel: EXT3-fs error (device sdb1): ext3_check_descriptors: Block bitmap for group 384 not in group (block 3120627712)!
Jan 19 08:54:30 HNTX-LY-PCMS kernel: EXT3-fs: group descriptors corrupted !
Jan 19 08:59:16 HNTX-LY-PCMS kernel: EXT3-fs error (device sdb1): ext3_check_descriptors: Block bitmap for group 384 not in group (block 3120627712)!
Jan 19 08:59:16 HNTX-LY-PCMS kernel: EXT3-fs: group descriptors corrupted !
Jan 19 09:00:28 HNTX-LY-PCMS kernel: EXT3-fs error (device sdb1): ext3_check_descriptors: Block bitmap for group 384 not in group (block 3120627712)!
Jan 19 09:00:28 HNTX-LY-PCMS kernel: EXT3-fs: group descriptors corrupted !
Jan 19 09:04:35 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 09:04:35 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 09:04:35 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 09:04:35 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 09:05:30 HNTX-LY-PCMS kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jan 19 09:05:30 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 09:05:30 HNTX-LY-PCMS kernel: EXT3-fs error (device sdb1): ext3_check_descriptors: Block bitmap for group 384 not in group (block 3120627712)!
Jan 19 09:05:30 HNTX-LY-PCMS kernel: EXT3-fs: group descriptors corrupted !
Jan 19 09:31:44 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 09:31:44 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 09:31:44 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 09:31:44 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 09:32:38 HNTX-LY-PCMS kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jan 19 09:32:38 HNTX-LY-PCMS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 19 09:32:38 HNTX-LY-PCMS kernel: EXT3-fs error (device sdb1): ext3_check_descriptors: Block bitmap for group 384 not in group (block 3120627712)!
Jan 19 09:32:38 HNTX-LY-PCMS kernel: EXT3-fs: group descriptors corrupted !
[root@HNTX-LY-PCMS log]#

 

 

e2fsck与fsck
fsck是为检查各种不同的文件系统提供一个统一的用户界面。
   e2fsck是用于ext2/ext3类型的文件系统检查的一个工具。
仅仅如此区别，我在网上搜索了大半天都没有找到结果，最后却是用man比较的时候比较出来了。太笨了！！！
但是在网上找到了关于这两个命令的用法：


fsck



使用方式 : fsck [-sACVRP] [-t fstype] [--] [fsck-options] filesys [...]

说明 ： 检查与修复 Linux 档案系统，可以同时检查一个或多个 Linux 档案系统


参数 ：

filesys ： device 名称(eg./dev/sda1)，mount 点 (eg. / 或 /usr)
-t : 给定档案系统的型式，若在 /etc/fstab 中已有定义或 kernel 本身已支援的则不需加上此参数
-s : 依序一个一个地执行 fsck 的指令来检查
-A : 对/etc/fstab 中所有列出来的 partition 做检查
-C : 显示完整的检查进度
-d : 列印 e2fsck 的 debug 结果
-p : 同时有 -A 条件时，同时有多个 fsck 的检查一起执行
-R : 同时有 -A 条件时，省略 / 不检查
-V : 详细显示模式
-y : 预先设定所有检查时的问题均回答[是]
-a : 如果检查有错则自动修复
-r : 如果检查有错则由使用者回答是否修复

例子 :
检查 msdos 档案系统的 /dev/hda5 是否正常，如果有异常便自动修复 :
fsck -t msdos -a /dev/hda5

注意 :

此指令可与 /etc/fstab 相互参考操作来加以了解。




e2fsck


使用方式 : e2fsck [-pacnydfvFV] [-b superblock] [-B blocksize] [-l|-L bad_blocks_file] [-C fd] device

说明 ： 检查使用 Linux ext2 档案系统的 partition 是否正常工作


参数 ：

device ： 预备检查的硬盘 partition，例如：/dev/sda1
-a : 对 partition 做检查，若有问题便自动修复，等同 -p 的功能
-b : 设定存放 superblock 的位置
-B : 设定单位 block 的大小
-c : 检查该partition 是否有坏轨
-C file : 将检查的结果存到 file 中以便查看
-d : 列印 e2fsck 的 debug 结果
-f : 强制检查
-F : 在开始检查前，将device 的 buffer cache 清空，避免有错误发生
-l bad_blocks_file : 将有坏轨的block资料加到 bad_blocks_file 里面
-L bad_blocks_file : 设定坏轨的block资料存到 bad_blocks_file 里面，若无该档则自动产生
-n : 将档案系统以[唯读]方式开启
-p : 对 partition 做检查，若有问题便自动修复
-v : 详细显示模式
-V : 显示出目前 e2fsck 的版本
-y : 预先设定所有检查时的问题均回答[是]

例子 :
检查 /dev/hda5 是否正常，如果有异常便自动修复，并且设定若有问答，均回答[是] :
e2fsck -a -y /dev/hda5

注意 :

大部份使用 e2fsck 来检查硬盘 partition 的情况时，通常都是情形特殊，因此最好先将该 partition umount，然后再执行 e2fsck 来做检查，若是要非要检查 / 时，则请进入 singal user mode 再执行。

 

e2fsck检查ext3/2文件系统的分区
Note: 检查之前一定要先御下待检查的文件系统！

命令：e2fsck, fsck.ext3, fsck.ext2

1. e2fsck /dev/hda1
如果hda1是'clean'的，将跳过检查。

2. e2fsck -f -v -C0 /dev/hda1
-f: 即使是'clean'的，也要检查
-v: 显示详细结果
-C0: 检查的同时显示进度条和百分比到屏幕（是数字零，不是'O'）

还有些参数有时也会用到：
-r: 实际什么也不做，只演示性的检查，测试兼容性

如果检查到有问题，程序会停下来询问是否修复，如果不想被一个一个问，还有-n,-y,-p:
-n: 将以只读方式打开文件系统（在没有同时用-c,-l,-L的情况下），并对所有的问题回答no，这种情况下不会对文件系统做任何改变，即使查到错误。
-y: 对所有问题回答yes。
-p: 自动修复文件系统错误。
* 这三参数一次只能选一个，不能同时用

e2fsck还有标记坏扇区的功能，和其它参数，详见'man e2fsck'

 

 

 

濮阳服务器盘柜分区报错及其处理

EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
UDP: bad checksum. From 222.215.85.221:32016 to 61.158.214.196:8800 ulen 63
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds

[1]+  Stopped                 dmesg | less
[root@HNTX-PY-PCMS ~]# df -h
Filesystem            容量  已用 可用 已用% 挂载点
/dev/cciss/c0d0p2     9.9G  2.1G  7.4G  22% /
/dev/cciss/c0d0p1      99M   12M   83M  13% /boot
none                  505M     0  505M   0% /dev/shm
/dev/cciss/c0d0p6     122G  106G  9.9G  92% /home
/dev/cciss/c0d0p3     2.0G  1.7G  239M  88% /var
/dev/sda1             1.6T  1.5T   45G  98% /home/apache/media/media1
/dev/sdb1             1.6T  950G  617G  61% /home/apache/media/media2
[root@HNTX-PY-PCMS ~]# df -h
Filesystem            容量  已用 可用 已用% 挂载点
/dev/cciss/c0d0p2     9.9G  2.1G  7.4G  22% /
/dev/cciss/c0d0p1      99M   12M   83M  13% /boot
none                  505M     0  505M   0% /dev/shm
/dev/cciss/c0d0p6     122G  106G  9.9G  92% /home
/dev/cciss/c0d0p3     2.0G  1.7G  239M  88% /var
/dev/sda1             1.6T  1.5T   45G  98% /home/apache/media/media1
/dev/sdb1             1.6T  950G  617G  61% /home/apache/media/media2
[root@HNTX-PY-PCMS ~]# umount /dev/sda1
umount: /home/apache/media/media1: device is busy
umount: /home/apache/media/media1: device is busy
[root@HNTX-PY-PCMS ~]# umount -l /dev/sda1
[root@HNTX-PY-PCMS ~]# umount -l /dev/sdb1
[root@HNTX-PY-PCMS ~]# df -h
Filesystem            容量  已用 可用 已用% 挂载点
/dev/cciss/c0d0p2     9.9G  2.1G  7.4G  22% /
/dev/cciss/c0d0p1      99M   12M   83M  13% /boot
none                  505M     0  505M   0% /dev/shm
/dev/cciss/c0d0p6     122G  106G  9.9G  92% /home
/dev/cciss/c0d0p3     2.0G  1.7G  239M  88% /var
[root@HNTX-PY-PCMS ~]# df -h
Filesystem            容量  已用 可用 已用% 挂载点
/dev/cciss/c0d0p2     9.9G  2.1G  7.4G  22% /
/dev/cciss/c0d0p1      99M   12M   83M  13% /boot
none                  505M     0  505M   0% /dev/shm
/dev/cciss/c0d0p6     122G  106G  9.9G  92% /home
/dev/cciss/c0d0p3     2.0G  1.7G  239M  88% /var
[root@HNTX-PY-PCMS ~]# e2fsck -a -y /dev/sda1
e2fsck: Only one the options -p/-a, -n or -y may be specified.
[root@HNTX-PY-PCMS ~]# e2fsck -a -y /dev/sda1
e2fsck: Only one the options -p/-a, -n or -y may be specified.
[root@HNTX-PY-PCMS ~]# e2fsck -y /dev/sda1
e2fsck 1.35 (28-Feb-2004)
/dev/sda1: recovering journal
/dev/sda1: clean, 18615/210665472 files, 405397521/421330722 blocks
[root@HNTX-PY-PCMS ~]# e2fsck -y /dev/sdb1
e2fsck 1.35 (28-Feb-2004)
/dev/sdb1: recovering journal
Clearing orphaned inode 21258 (uid=0, gid=0, mode=0100666, size=1621264)
Already cleared block #0 (88599809) found in orphaned inode 21258.
/dev/sdb1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 20745 has zero dtime.  Fix? yes

Inodes that were part of a corrupted orphan linked list found.  Fix? yes

Inode 21256 was part of the orphaned inode list.  FIXED.
Inode 21258 was part of the orphaned inode list.  FIXED.
Pass 2: Checking directory structure
Entry 'M-4M-sM-?M-iM-MM-7M-RM-2M-SM-PM-4M-sM-CM-NM-OM-k.mpg.idx' in / (2) has deleted/unused inode 20745.  Clear? yes

Entry 'M-NM-dM-AM-VM-7M-g20100217.mpg.idx' in / (2) has deleted/unused inode 21256.  Clear? yes

Entry 'M-NM-dM-AM-VM-7M-g20100217.mpg.mpgi' in / (2) has deleted/unused inode 21258.  Clear? yes

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(93600961--93600967) -(95388162--95388167) -(95546817--95546818) -(130646530--130646535) -(132286785--132286791) -(132612610--132612615) -(132869569--132869575) -(132907522--132907527) -(132908738--132908743) -(132940290--132940295) -(132940481--132940487) -(133192641--133192647) -(133202434--133202439) -(133366274--133366279) -(136550229--136550524)
Fix? yes

Free blocks count wrong for group #2629 (0, counted=14300).
Fix? yes

Free blocks count wrong for group #2655 (0, counted=4471).
Fix? yes

Free blocks count wrong for group #2656 (0, counted=20127).
Fix? yes

Free blocks count wrong for group #2671 (0, counted=19819).
Fix? yes

Free blocks count wrong for group #2672 (0, counted=17299).
Fix? yes

Free blocks count wrong for group #2675 (0, counted=16174).
Fix? yes

Free blocks count wrong for group #2681 (0, counted=11853).
Fix? yes

Free blocks count wrong for group #2682 (0, counted=16259).
Fix? yes

Free blocks count wrong for group #2703 (0, counted=8631).
Fix? yes

Free blocks count wrong for group #2704 (0, counted=6689).
Fix? yes

Free blocks count wrong for group #2709 (0, counted=7666).
Fix? yes

Free blocks count wrong for group #2710 (0, counted=32254).
Fix? yes

Free blocks count wrong for group #2711 (0, counted=18814).
Fix? yes

Free blocks count wrong for group #2856 (0, counted=7).
Fix? yes

Free blocks count wrong for group #2911 (0, counted=6).
Fix? yes

Free blocks count wrong for group #2915 (0, counted=2).
Fix? yes

Free blocks count wrong for group #3987 (0, counted=6).
Fix? yes

Free blocks count wrong for group #4037 (0, counted=7).
Fix? yes

Free blocks count wrong for group #4047 (0, counted=6).
Fix? yes

Free blocks count wrong for group #4054 (0, counted=7).
Fix? yes

Free blocks count wrong for group #4056 (0, counted=12).
Fix? yes

Free blocks count wrong for group #4057 (0, counted=13).
Fix? yes

Free blocks count wrong for group #4064 (0, counted=7).
Fix? yes

Free blocks count wrong for group #4065 (0, counted=6).
Fix? yes

Free blocks count wrong for group #4070 (0, counted=6).
Fix? yes

Free blocks count wrong for group #4167 (0, counted=296).
Fix? yes

Free blocks count wrong (165914475, counted=166109212).
Fix? yes

Inode bitmap differences:  -20745 -21256 -21258
Fix? yes

Free inodes count wrong for group #1 (1300, counted=1306).
Fix? yes

Free inodes count wrong (210644370, counted=210644376).
Fix? yes

/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: 21096/210665472 files (29.7% non-contiguous), 255221510/421330722 blocks
[root@HNTX-PY-PCMS ~]#

服务器reboot后

 

[root@HNTX-PY-PCMS ~]# reboot

Broadcast message from root (pts/1) (Thu Mar 18 11:12:07 2010):

The system is going down for reboot NOW!
[root@HNTX-PY-PCMS ~]# Last login: Thu Mar 18 10:32:24 2010 from 61.168.222.130
[root.adminssh@HNTX-PY-PCMS ~]$ su -
Password:
[root@HNTX-PY-PCMS ~]# df -h
Filesystem            容量  已用 可用 已用% 挂载点
/dev/cciss/c0d0p2     9.9G  2.1G  7.4G  22% /
/dev/cciss/c0d0p1      99M   12M   83M  13% /boot
none                  505M     0  505M   0% /dev/shm
/dev/cciss/c0d0p6     122G  106G  9.9G  92% /home
/dev/cciss/c0d0p3     2.0G  1.7G  246M  88% /var
/dev/sda1             1.6T  1.5T   45G  98% /home/apache/media/media1
/dev/sdb1             1.6T  949G  618G  61% /home/apache/media/media2
[root@HNTX-PY-PCMS ~]# dmesg
Linux version 2.6.9-42.ELsmp () (gcc version 3.4.6 20060404 (Red Hat 3.4.6-2)) #1 SMP Wed Jul 12 23:27:17 EDT 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
 BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000003fe58000 (usable)
 BIOS-e820: 000000003fe58000 - 000000003fe60000 (ACPI data)
 BIOS-e820: 000000003fe60000 - 0000000040000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fed00000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
 BIOS-e820: 00000000ffc00000 - 0000000100000000 (reserved)
126MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f4f80
Using x86 segment limits to approximate NX protection
On node 0 totalpages: 261720
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 225280 pages, LIFO batch:16
  HighMem zone: 32344 pages, LIFO batch:7
DMI 2.3 present.
ServerWorks chipset detected. Disabling timer routing over 8254.
Using APIC driver default
ACPI: RSDP (v002 HP                                    ) @ 0x000f4f00
ACPI: XSDT (v001 HP     I15      0x00000002 ?0x0000162e) @ 0x3fe58300
ACPI: FADT (v003 HP     I15      0x00000002 ?0x0000162e) @ 0x3fe58380
ACPI: SPCR (v001 HP     SPCRRBSU 0x00000001 ?0x0000162e) @ 0x3fe58100
ACPI: MCFG (v001 HP     ProLiant 0x00000001  0x00000000) @ 0x3fe58180
ACPI: HPET (v001 HP     I15      0x00000002 ?0x0000162e) @ 0x3fe581c0
ACPI: SPMI (v005 HP     ProLiant 0x00000001 ?0x0000162e) @ 0x3fe58200
ACPI: MADT (v001 HP     00000083 0x00000002  0x00000000) @ 0x3fe58240
ACPI: DSDT (v001 HP         DSDT 0x00000001 INTL 0x20030228) @ 0x00000000
ACPI: PM-Timer IO Port: 0x908
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
Enabling APIC mode:  Flat.  Using 0 I/O APICs
ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
ACPI: HPET id: 0x8086a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Built 1 zonelists
Kernel command line: ro root=LABEL=/ elevator=deadline rhgb quiet
mapped APIC to ffffd000 (fee00000)
Initializing CPU#0
CPU 0 irqstacks, hard=c03ee000 soft=c03ce000
PID hash table entries: 4096 (order: 12, 65536 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1031840k/1046880k available (1876k kernel code, 14384k reserved, 759k data, 184k init, 129376k highmem)
Using HPET for base-timer
Using HPET for gettimeofday
Detected 1600.115 MHz processor.
Using hpet for high-res timesource
Calibrating delay using timer specific routine.. 3202.33 BogoMIPS (lpj=1601165)
Security Scaffold v1.0.0 initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
There is already a security framework initialized, register_security failed.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: bfebfbff 20000000 00000000 00000000
CPU: After vendor identify, caps:  bfebfbff 20000000 00000000 00000000
monitor/mwait feature present.
using mwait in idle threads.
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU0: Physical Processor ID: 0
CPU0: Processor Core ID: 0
CPU0: Initial APIC ID: 0
CPU: After all inits, caps:        bfebf3ff 20000000 00000000 00000040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
CPU0: Intel(R) Xeon(R) CPU            5110  @ 1.60GHz stepping 06
per-CPU timeslice cutoff: 4029.52 usecs.
task migration cache decay timeout: 5 msecs.
Booting processor 1/1 eip 3000
CPU 1 irqstacks, hard=c03ef000 soft=c03cf000
Initializing CPU#1
Calibrating delay using timer specific routine.. 3200.13 BogoMIPS (lpj=1600069)
CPU: After generic identify, caps: bfebfbff 20000000 00000000 00000000
CPU: After vendor identify, caps:  bfebfbff 20000000 00000000 00000000
monitor/mwait feature present.
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU1: Physical Processor ID: 0
CPU1: Processor Core ID: 1
CPU1: Initial APIC ID: 1
CPU: After all inits, caps:        bfebf3ff 20000000 00000000 00000040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel(R) Xeon(R) CPU            5110  @ 1.60GHz stepping 06
Total of 2 processors activated (6402.46 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 pin1=2 pin2=-1
checking TSC synchronization across 2 CPUs: passed.
Brought up 2 CPUs
zapping low mappings.
checking if image is initramfs... it is
Freeing initrd memory: 692k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 3.00 entry at 0xf0072, last bus=24
PCI: Using MMCONFIG
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040816
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IP2P._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IPTA.NPE1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT02._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT02.IPE4._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT02.IPE4.IPE1.NPE2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT03._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT04._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT05._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT06._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT07._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *5 7 10 11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *7 10 11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 5 7 *10 11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 *10 11)
ACPI: PCI Interrupt Link [LNKE] (IRQs 5 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs *5 7 10 11)
ACPI: PCI Interrupt Link [LNKG] (IRQs 5 7 *10 11)
ACPI: PCI Interrupt Link [LNKH] (IRQs 5 *7 10 11)
Linux Plug and Play Support v0.97 (c) Adam Belay
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
ACPI: PCI interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 177
ACPI: PCI interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 185
ACPI: PCI interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 193
ACPI: PCI interrupt 0000:00:1d.7[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI interrupt 0000:05:00.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI interrupt 0000:05:01.0[A] -> GSI 17 (level, low) -> IRQ 177
ACPI: PCI interrupt 0000:07:00.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI interrupt 0000:0b:08.0[A] -> GSI 18 (level, low) -> IRQ 185
ACPI: PCI interrupt 0000:10:00.0[A] -> GSI 18 (level, low) -> IRQ 185
ACPI: PCI interrupt 0000:10:00.1[B] -> GSI 19 (level, low) -> IRQ 193
ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI interrupt 0000:01:03.0[A] -> GSI 23 (level, low) -> IRQ 201
ACPI: PCI interrupt 0000:01:04.0[A] -> GSI 21 (level, low) -> IRQ 209
ACPI: PCI interrupt 0000:01:04.2[B] -> GSI 22 (level, low) -> IRQ 217
ACPI: PCI interrupt 0000:01:04.4[B] -> GSI 22 (level, low) -> IRQ 217
ACPI: PCI interrupt 0000:01:04.6[A] -> GSI 21 (level, low) -> IRQ 209
PCI: Device 00:00 not found by BIOS
apm: BIOS not found.
audit: initializing netlink socket (disabled)
audit(1268910828.396:1): initialized
highmem bounce pool size: 64 pages
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux:  Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 8301CD821788A86B
- User ID: Red Hat, Inc. (Kernel Module GPG key)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: Processor [CPU0] (supports C1)
ACPI: Processor [CPU1] (supports C1)
ACPI: Thermal Zone [THM0] (8 C)
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
divert: not allocating divert_blk for non-ethernet device lo
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Probing IDE interface ide0...
Probing IDE interface ide1...
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 131072 (order: 8, 1572864 bytes)
TCP: Hash tables configured (established 131072 bind 131072)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI: (supports S0 S4 S5)
ACPI wakeup devices:

Freeing unused kernel memory: 184k freed
SCSI subsystem initialized
HP CISS Driver (v 2.6.10.RH1)
cciss: Device 0x3238 has been found at bus 11 dev 8 func 0
ACPI: PCI interrupt 0000:0b:08.0[A] -> GSI 18 (level, low) -> IRQ 185
MSI INIT SUCCESS
cciss: using DAC cycles
      blocks= 286677120 block_size= 512
      heads= 255, sectors= 32, cylinders= 35132

Using deadline io scheduler
      blocks= 286677120 block_size= 512
      heads= 255, sectors= 32, cylinders= 35132

 cciss/c0d0: p1 p2 p3 p4 < p5 p6 >
QLogic Fibre Channel HBA Driver
ACPI: PCI interrupt 0000:10:00.0[A] -> GSI 18 (level, low) -> IRQ 185
qla2400 0000:10:00.0: Found an ISP2432, irq 185, iobase 0xf8826000
qla2400 0000:10:00.0: Configuring PCI space...
PCI: Setting latency timer of device 0000:10:00.0 to 64
qla2400 0000:10:00.0: Configure NVRAM parameters...
qla2400 0000:10:00.0: Verifying loaded RISC code...
qla2400 0000:10:00.0: Allocated (64 KB) for EFT...
qla2400 0000:10:00.0: Allocated (1413 KB) for firmware dump...
qla2400 0000:10:00.0: Waiting for LIP to complete...
qla2400 0000:10:00.0: LIP reset occured (f700).
qla2400 0000:10:00.0: LOOP UP detected (4 Gbps).
qla2400 0000:10:00.0: Topology - (F_Port), Host Loop address 0x0
scsi0 : qla2xxx
qla2400 0000:10:00.0:
 QLogic Fibre Channel HBA Driver: 8.01.06
  QLogic QMH2462 - SBUS to 2Gb FC, Dual Channel
  ISP2432: PCIe (2.5Gb/s x4) @ 0000:10:00.0 hdma+, host#=0, fw=4.00.23 [IP]
  Vendor: HITACHI   Model: DF600F            Rev: 0000
  Type:   Direct-Access                      ANSI SCSI revision: 03
qla2400 0000:10:00.0: scsi(0:0:0:0): Enabled tagged queuing, queue depth 32.
SCSI device sda: 3370647552 512-byte hdwr sectors (1725772 MB)
SCSI device sda: drive cache: write through
SCSI device sda: 3370647552 512-byte hdwr sectors (1725772 MB)
SCSI device sda: drive cache: write through
 sda: sda1
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
  Vendor: HITACHI   Model: DF600F            Rev: 0000
  Type:   Direct-Access                      ANSI SCSI revision: 03
qla2400 0000:10:00.0: scsi(0:0:0:1): Enabled tagged queuing, queue depth 32.
SCSI device sdb: 3370647552 512-byte hdwr sectors (1725772 MB)
SCSI device sdb: drive cache: write through
SCSI device sdb: 3370647552 512-byte hdwr sectors (1725772 MB)
SCSI device sdb: drive cache: write through
 sdb: sdb1
Attached scsi disk sdb at scsi0, channel 0, id 0, lun 1
ACPI: PCI interrupt 0000:10:00.1[B] -> GSI 19 (level, low) -> IRQ 193
qla2400 0000:10:00.1: Found an ISP2432, irq 193, iobase 0xf8828000
qla2400 0000:10:00.1: Configuring PCI space...
PCI: Setting latency timer of device 0000:10:00.1 to 64
qla2400 0000:10:00.1: Configure NVRAM parameters...
qla2400 0000:10:00.1: Verifying loaded RISC code...
qla2400 0000:10:00.1: Allocated (64 KB) for EFT...
qla2400 0000:10:00.1: Allocated (1413 KB) for firmware dump...
qla2400 0000:10:00.1: Waiting for LIP to complete...
qla2400 0000:10:00.1: Cable is unplugged...
scsi1 : qla2xxx
qla2400 0000:10:00.1:
 QLogic Fibre Channel HBA Driver: 8.01.06
  QLogic QMH2462 - SBUS to 2Gb FC, Dual Channel
  ISP2432: PCIe (2.5Gb/s x4) @ 0000:10:00.1 hdma+, host#=1, fw=4.00.23 [IP]
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
SELinux:  Disabled at runtime.
SELinux:  Unregistering netfilter hooks
inserting floppy driver for 2.6.9-42.ELsmp
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.4.38 (February 10, 2006)
ACPI: PCI interrupt 0000:07:00.0[A] -> GSI 16 (level, low) -> IRQ 169
divert: allocating divert_blk for eth0
eth0: Broadcom NetXtreme II BCM5708 1000Base-SX (B2) PCI-X 64-bit 133MHz found at mem fa000000, IRQ 169, node addr 001a4be0fcde
ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 169
divert: allocating divert_blk for eth1
eth1: Broadcom NetXtreme II BCM5708 1000Base-SX (B2) PCI-X 64-bit 133MHz found at mem f6000000, IRQ 169, node addr 001a4be0fccc
shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5
shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5
shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5
hw_random hardware driver 1.0.0 loaded
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 169
uhci_hcd 0000:00:1d.0: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: irq 169, io base 00001000
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 177
uhci_hcd 0000:00:1d.1: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: irq 177, io base 00001020
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 185
uhci_hcd 0000:00:1d.2: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: irq 185, io base 00001040
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 193
uhci_hcd 0000:00:1d.3: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: irq 193, io base 00001060
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:01:04.4[B] -> GSI 22 (level, low) -> IRQ 217
uhci_hcd 0000:01:04.4: UHCI Host Controller
uhci_hcd 0000:01:04.4: irq 217, io base 00003800
uhci_hcd 0000:01:04.4: new USB bus registered, assigned bus number 5
uhci_hcd 0000:01:04.4: port count misdetected? forcing to 2 ports
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:1d.7[A] -> GSI 16 (level, low) -> IRQ 169
ehci_hcd 0000:00:1d.7: EHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: irq 169, pci mem f88ae000
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 6
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 8 ports detected
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
usb 5-1: new full speed USB device using address 2
ACPI: Power Button (FF) [PWRF]
input: USB HID v1.01 Keyboard [HP Virtual Keyboard] on usb-0000:01:04.4-1
input: USB HID v1.01 Mouse [HP Virtual Keyboard] on usb-0000:01:04.4-1
usb 5-2: new full speed USB device using address 3
hub 5-2:1.0: USB hub found
hub 5-2:1.0: 7 ports detected
EXT3 FS on cciss/c0d0p2, internal journal
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: [e-mail]
kjournald starting.  Commit interval 5 seconds
EXT3 FS on cciss/c0d0p1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on cciss/c0d0p6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on cciss/c0d0p3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1052216k swap on /dev/cciss/c0d0p5.  Priority:-1 extents:1
IA-32 Microcode Update Driver: v1.14 <>
microcode: No new microdata for cpu 1
microcode: No new microdata for cpu 0
IA-32 Microcode Update Driver v1.14 unregistered
ip_tables: (C) 2000-2002 Netfilter core team
ip_tables: (C) 2000-2002 Netfilter core team
bnx2: eth0: using MSI
i2c /dev entries driver
lp: driver loaded but no devices found
NET: Registered protocol family 10
Disabled Privacy Extensions on device c0344160(lo)
IPv6 over IPv4 tunneling driver
divert: not allocating divert_blk for non-ethernet device sit0
bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex
eth0: no IPv6 routers present
ip_tables: (C) 2000-2002 Netfilter core team
bnx2: eth0: using MSI
bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex
eth0: no IPv6 routers present
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning (device sdb1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
EXT3-fs warning (device sdb1): ext3_clear_journal_err: Marking fs in need of filesystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
[root@HNTX-PY-PCMS ~]# umount /dev/sda1
[root@HNTX-PY-PCMS ~]# umount /dev/sdb1
[root@HNTX-PY-PCMS ~]# df -h
Filesystem            容量  已用 可用 已用% 挂载点
/dev/cciss/c0d0p2     9.9G  2.1G  7.4G  22% /
/dev/cciss/c0d0p1      99M   12M   83M  13% /boot
none                  505M     0  505M   0% /dev/shm
/dev/cciss/c0d0p6     122G  106G  9.9G  92% /home
/dev/cciss/c0d0p3     2.0G  1.7G  246M  88% /var
[root@HNTX-PY-PCMS ~]# e2fsck -a -y /dev/sdb1
e2fsck: Only one the options -p/-a, -n or -y may be specified.
[root@HNTX-PY-PCMS ~]# e2fsck -a  /dev/sdb1
/dev/sdb1 contains a file system with errors, check forced.
/dev/sdb1: Inodes that were part of a corrupted orphan linked list found. 

/dev/sdb1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)

[root@HNTX-PY-PCMS ~]# e2fsck -y  /dev/sdb1
e2fsck 1.35 (28-Feb-2004)
/dev/sdb1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? yes

Inode 21256 was part of the orphaned inode list.  FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: 21096/210665472 files (29.7% non-contiguous), 255221510/421330722 blocks
[root@HNTX-PY-PCMS ~]#