fsck 的用法

磁盘failure,如何修复?            fsck

fsck -y	对所有文件进行检测，对所有提问都用yes回答 无须人工干预，自动修复文件系统
fsck -n	对所有文件进行检测，对所有提问都用no回答 只检测文件系统，不进行修复，只报告
fsck -D	通知fsck 额外检查系统的一致性

 

           

fsck命令不创建lost+found目录，用户必须先创建该目录


   无参数fsck和fsck -m一样，都是check but no repair (应该也是类似 –n)

#  fsck

** /dev/rdsk/c0d0s0
** Currently Mounted on /    针对当前/所在磁盘
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
164363 files, 7339667 used, 4713569 free (95961 frags, 577201 blocks, 0.8% fragmentation)

# fsck /dev/rdsk/c0d0s0 -m

** /dev/rdsk/c0d0s0
** Currently Mounted on /
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
164363 files, 7339667 used, 4713569 free (95961 frags, 577201 blocks, 0.8% fragmentation)
fsck: operation not applicable to FSType nfs

    fsck –m 和fsck –n 或fsck 的区别：fsck -m 必须跟dev 文件名，不能对当前硬盘

# fsck –m
** /dev/rdsk/c0d0s0
ufs fsck: sanity check:/dev/rdsk/c0d0s0 already mounted read/write

# fsck /dev/rdsk/c0d0s0 -m

** /dev/rdsk/c0d0s0
** Currently Mounted on /
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
164363 files, 7339667 used, 4713569 free (95961 frags, 577201 blocks, 0.8% fragmentation)
fsck: operation not applicable to FSType nfs

    fsck  -m后跟硬盘的/dev文件名作为参数时，时常出问题，最好就是fsck -y, 无文件名参数，直接对当前文件系统


   solaris 硬盘错误导致无法启动，最基本的步骤：光盘启动 + fsck

• 1    ok  boot cdrom -s
• 2    # fsck -y /dev/rdsk/c0t0d0s0

   异常down机时正在进行vi，linux也会产生缓存文件*.swp

[root@localhost vsftpd]# ls –a
.  ..  ftpusers  user_list  vsftpd.conf  vsftpd_conf_migrate.sh  .vsftpd.conf.swp

删掉即可
[root@localhost vsftpd]#rm  .vsftpd.conf.swp

转载自：http://blog.sina.com.cn/s/blog_6151984a0100fpa6.html