有时候，在Linux删除一个大文件的时候，你会发现磁盘空间并没有释放出来。
比方说下面这样的情况：
磁盘空间满：
|
1 2 3 4 5 6 7 |
[root@mha1 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_mha1-lv_root 42G 42G 0 100% / tmpfs 7.9G 88K 7.9G 1% /dev/shm /dev/sda1 485M 37M 423M 8% /boot [root@mha1 ~]# |
最后，找到占用磁盘空间的是一个日志文件：nohup.out，如下：
[crayon-5adc7c[……]
在刚才更改网站策略的时候遇到了一个cPanel的错误（如题所示），它具体的表现如下图：
其实，该错误是由于网站的存储空间耗尽引发的：
解决方法 – 腾出足够的空间即可：
————————————————————————
Done。
今天，在启动数据库的时候，遇到了如下所示的这个问题：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
[oracle11g@em12cdb ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Fri Aug 7 01:16:33 2015 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to an idle instance. SQL> startup mount; ORACLE instance started. Total System Global Area 2204696576 bytes Fixed Size 2255112 bytes Variable Size 671090424 bytes Database Buffers 1526726656 bytes Redo Buffers 4624384 bytes Database mounted. SQL> alter database open; alter database open * ERROR at line 1: ORA-03113: end-of-file on communication channel Process ID: 3226 Session ID: 1 Serial number: 5 SQL> |
该错误发生时的alert日志状态如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 |
Fri Aug 07 01:19:05 2015 alter database open Fri Aug 07 01:19:05 2015 LGWR: STARTING ARCH PROCESSES Fri Aug 07 01:19:05 2015 ARC0 started with pid=20, OS id=3409 ARC0: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE ARC0: STARTING ARCH PROCESSES Fri Aug 07 01:19:06 2015 ARC1 started with pid=21, OS id=3413 Fri Aug 07 01:19:06 2015 ARC2 started with pid=22, OS id=3417 Errors in file /u01/app/oracle/diag/rdbms/em12c/em12c/trace/em12c_ora_3401.trc: ORA-19815: WARNING: db_recovery_file_dest_size of 4385144832 bytes is 100.00% used, and has 0 remaining bytes available. ************************************************************************ You have following choices to free up space from recovery area: 1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard, then consider changing RMAN ARCHIVELOG DELETION POLICY. 2. Back up files to tertiary device such as tape using RMAN BACKUP RECOVERY AREA command. 3. Add disk space and increase db_recovery_file_dest_size parameter to reflect the new space. 4. Delete unnecessary files using RMAN DELETE command. If an operating system command was used to delete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands. ************************************************************************ ARCH: Error 19809 Creating archive log file to '/u01/app/oracle/fast_recovery_area/EM12C/archivelog/2015_08_07/o1_mf_1_27_%u_.arc' Errors in file /u01/app/oracle/diag/rdbms/em12c/em12c/trace/em12c_ora_3401.trc: ORA-16038: log 5 sequence# 27 cannot be archived ORA-19809: limit exceeded for recovery files ORA-00312: online log 5 thread 1: '/u01/app/oracle/oradata/em12c/redo05' Fri Aug 07 01:19:06 2015 ARC3 started with pid=23, OS id=3421 USER (ospid: 3401): terminating the instance due to error 16038 Fri Aug 07 01:19:07 2015 System state dump requested by (instance=1, osid=3401), summary=[abnormal instance termination]. System State dumped to trace file /u01/app/oracle/diag/rdbms/em12c/em12c/trace/em12c_diag_3339_20150807011907.trc Dumping diagnostic data in directory=[cdmp_20150807011907], requested by (instance=1, osid=3401), summary=[abnormal instance termination]. Instance terminated by USER, pid = 3401 |
通过alert日志可以定位到问题：
“
ARCH: E[……]