Maven 完全参考 学习笔记 (1) 简介

online book Maven: The Complete Reference

  1. Maven: A tool more than build;
  2. Maven is a project management tool which encompasses a project object model, a set of standards, a project lifecycle, a dependency management system, and logic for executing plugin goals at defined phases in a lifecycle. When you use Maven, you describe your project using a well-defined project object model, Maven can then apply cross-cutting logic from a set of shared (or custom) plugins.
  3. COC 最佳实践 共同知识 easonable defaults. Not only folders, plugin..., And can .. customized.
  4. The core of Maven is pretty dumb, it doesn’t know how to do much beyond parsing a few XML documents and keeping track of a lifecycle and a few plugins. Maven has been designed to delegate most responsibility to a set of Maven Plugins which can affect the Maven Lifecycle and offer access to goals.

ext3 文件系统报错 bad entry in directory

买一超级便宜U盘: usb 2.0, 512G 40RMB. 直接插电脑, 写入速度1.3 ~ 3.6 M/s.
格式化为 ext3, 快速硬盘检查, 无问题. 接到路由器的USB hub, 开始aria2 文件下载.
arias 配置文件, 及 downloads 目录创建正常.
几分钟后, downloads 目录无法写入, 所有bt下载全部被删除.
telnet 登上去, touch 文件显示: : Input/output error
查看读写权限, 全有, 并且使用root来写入, 排除权限问题.

查看系统日志, 显示:
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #5556142: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0

根据google 结果, 修复:
http://www.novell.com/support/kb/doc.php?id=3554036

Situation

At reboot, or mount of an EXT3 file-system, an error similar to the one below is seen:
EXT3-fs error (device dm-0): ext3_readdir: bad entry in directory #5556142: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0

Resolution

This error is caused by a file that has been marked as a directory. This is a non-fatal error and can be fixed by removing the file in question.
1) Mount the file-system in question
2) Locate the file that has been corrupted. The file's inode is the number after "bad entry in directory" Using the example error code the file would be found by typing

find /MOUNT_POINT-inum 5556142

3) Delete the file identified in step two
4) Umount the file-system
5) Check the disk, and check for errors.

fsck/dev/PHYSICAL_DEVICE

6) Repeat step 5. If no errors, the file-system is clean.

Could not get any response