Chinaunix

标题: 求助，数据库DUMP恢复时报错 [打印本页]

作者: shinehom 时间: 2009-04-21 10:14
标题: 求助，数据库DUMP恢复时报错
$ isql -Usa -P
1> load database mpsdb1 from '/home/sybase/20090417.dmp'
2> go
Backup Server session id is:  5.  Use this value when executing the
'sp_volchanged' system stored procedure after fulfilling any volume change
request from the Backup Server.
Backup Server: 6.28.1.1: Dumpfile name 'mpsdb091070F7AA  ' section number 0001
mounted on disk file '/home/sybase/20090417.dmp'
Backup Server: 3.14.2.4: Logical page 79822847 is not in the given database
map.
Msg 8009, Level 16, State 1:
Line 1:
Error encountered by Backup Server.  Please refer to Backup Server messages for
details.
1> Apr 21 09:58:34 2009 Backup Server: 6.32.2.3: /home/sybase/20090417.dmp: volume not valid or not requested (server: , session id: 5.)
Apr 21 09:58:34 2009 Backup Server: 1.14.2.4: Unrecoverable I/O or volume error.  This DUMP or LOAD session must exit.

先创建了一个空的数据库，大小1000MB，LOAD此DUMP需要927MB空间。报错。

大侠们帮忙看看何解，搞了一晚上了。。。

作者: shinehom 时间: 2009-04-21 10:19
Apr 21 09:58:34 2009: Backup Server: 6.28.1.1: Dumpfile name 'mpsdb091070F7AA ' section number 0001 mounted on disk file '/home/syb
ase/20090417.dmp'
Apr 21 09:58:34 2009: Backup Server: 3.29.2.1: No virtual mapping for logical page 79822847.
Apr 21 09:58:34 2009: Backup Server: 3.14.2.4: Logical page 79822847 is not in the given database map.
Apr 21 09:58:34 2009: Backup Server: 6.32.2.3: /home/sybase/20090417.dmp: volume not valid or not requested (server: , session id: 5
.)
Apr 21 09:58:34 2009: Backup Server: 1.14.2.4: Unrecoverable I/O or volume error. This DUMP or LOAD session must exit.

SYB_BACKUP.log中日志

作者: hobbylu 时间: 2009-04-21 11:18
备份文件有问题，按正常办法已经无法恢复，请找到有效的备份进行恢复

作者: zq5143 时间: 2009-04-21 13:46
备份文件搞错了吧？

作者: WFCJZ 时间: 2009-04-21 17:23
备份之前,建议做DBCC检查!

作者: shinehom 时间: 2009-04-23 09:01
这个空数据库无法使用了。。。GOOGLE不到解决方法。。

作者: hobbylu 时间: 2009-04-23 09:21
你可以把这个dump文件发给我看看

作者: WFCJZ 时间: 2009-04-23 15:26

原帖由 hobbylu 于 2009-4-23 09:21 发表
你可以把这个dump文件发给我看看

楼主，相信hobbylu可以帮你！

作者: chuxu 时间: 2009-04-23 16:13
dbcc dbrepair (db_name,dropdb)

作者: shinehom 时间: 2009-04-24 09:47

原帖由 hobbylu 于 2009-4-23 09:21 发表
你可以把这个dump文件发给我看看

这个Dump文件是某银行的生产环境数据，不太好外泄，而且数据很大。

不过还是多谢。

问题已经通过其他途径解决，该Dump包可能在传输过程中出错。原本在银行生产机上的包是可以在他们的测试环境中恢复的。

只是在公司的模拟环境中出错。

作者: shinehom 时间: 2009-04-24 09:49
不知道如何散分，只能点2朵鲜花

作者: shinehom 时间: 2009-04-24 12:12
$ isql -Usa -P
1>
2> dbcc dbrepair (XX,dropdb)
3> go
Msg 2573, Level 16, State 1:
Line 2:
Database 'XX' is not marked suspect. You cannot drop it with DBCC.
DBCC execution completed. If DBCC printed error messages, contact a user with
System Administrator (SA) role.

恢复的时候还是报错，GOOGLE了一上午，没解决。。。
能帮忙看下吗？谢谢

作者: chuxu 时间: 2009-04-24 13:29
use master
go
update sysdatabases set status=256 where name='xx'
go
重启ASE
dbcc dbrepair (XX,dropdb)

作者: shinehom 时间: 2009-04-24 14:15
1> update sysdatabases set status=256 where name='XX'
2> go
Msg 10321, Level 14, State 1:
Line 1:
Ad-hoc updates to system catalogs not enabled. A user with System Security
Officer (SSO) role must reconfigure system to allow this.

继续报错，要更改什么设置？报错信息很模糊。。。

作者: zq5143 时间: 2009-04-24 14:18

原帖由 shinehom 于 2009-4-24 12:12 发表
$ isql -Usa -P
1>
2> dbcc dbrepair (XX,dropdb)
3> go
Msg 2573, Level 16, State 1:
Line 2:
Database 'XX' is not marked suspect. You cannot drop it with DBCC.
DBCC execution completed. If ...

dbcc dbrepair 操作应该是在数据库online之前做

作者: shinehom 时间: 2009-04-24 14:21
select into/bulkcopy/pllsort, trunc log on chkpt, don't recover, allow nulls by default, abort tran on

数据库现在的状态

作者: shinehom 时间: 2009-04-24 16:49
刚刚做了update master..sysdatabases set status=-32768的操作，重启数据库后，报错。

作者: shinehom 时间: 2009-04-24 16:53
$ isql -Usa -P
1> shutdown SYB_BACKUP
2> go
Backup Server: 3.48.1.1: The Backup Server will go down immediately.
Terminating sessions.
1> shutdown
2> go
00:00000:00001:2009/04/24 16:34:29.60 server  SQL Server shutdown by request.
00:00000:00001:2009/04/24 16:34:29.60 kernel  ueshutdown: exiting
Server SHUTDOWN by request.
The SQL Server is terminating this process.
CT-LIBRARY error:
      ct_results(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect
CT-LIBRARY error:
      ct_cancel(): network packet layer: internal net library error: Net-Lib protocol driver call to read data failed
$ startserver -f RUN_SYBASE
$ 00:00000:00000:2009/04/24 16:34:38.56 kernel  Using config area from primary master device.
00:00000:00000:2009/04/24 16:34:38.56 kernel  Warning: Using default file '/home/sybase/SYBASE.cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.
00:00000:00000:2009/04/24 16:34:38.56 kernel  Using 400 file descriptors.
00:00000:00000:2009/04/24 16:34:38.56 kernel  Adaptive Server Enterprise/11.9.2/P/DG AViiON/SCO UnixWare 2.1.3/FBO/Tue Jul  6 08:52:13 1999
00:00000:00000:2009/04/24 16:34:38.56 kernel  Confidential property of Sybase, Inc.
00:00000:00000:2009/04/24 16:34:38.56 kernel  Copyright 1987, 1999
00:00000:00000:2009/04/24 16:34:38.56 kernel  Sybase, Inc.  All rights reserved.
00:00000:00000:2009/04/24 16:34:38.56 kernel  Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2009/04/24 16:34:38.56 kernel
00:00000:00000:2009/04/24 16:34:38.56 kernel  This software contains confidential and trade secret information of Sybase,
00:00000:00000:2009/04/24 16:34:38.56 kernel  Inc. Use,  duplication or disclosure of the software and documentation by
00:00000:00000:2009/04/24 16:34:38.56 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in a license
00:00000:00000:2009/04/24 16:34:38.56 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  other  written
00:00000:00000:2009/04/24 16:34:38.56 kernel  agreement  specifying  the  Government's rights to use the software and any
00:00000:00000:2009/04/24 16:34:38.56 kernel  applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2009/04/24 16:34:38.56 kernel  Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608, USA
00:00000:00000:2009/04/24 16:34:38.56 kernel  Using '/home/sybase/SYBASE.cfg' for configuration information.
00:00000:00000:2009/04/24 16:34:38.56 kernel  Logging SQL Server messages in file '/home/sybase/install/SYBASE.log'.
00:00000:00000:2009/04/24 16:34:38.57 kernel  Directory Control Layer (DCL) using directory driver: InterfacesDriver
00:00000:00000:2009/04/24 16:34:38.57 kernel  Network and device connection limit is 390.
00:00000:00000:2009/04/24 16:34:38.58 server  Number of proc buffers allocated: 32290.
open of async device failed: Permission denied
00:00000:00000:2009/04/24 16:34:38.59 kernel  dioinit: Unable to lock memory for async I/O
00:00000:00000:2009/04/24 16:34:38.64 server  Proc header memory allocated 16145 pages for each per engine cache
00:00000:00000:2009/04/24 16:34:38.64 server  Number of blocks left for proc headers: 32352.
00:00000:00000:2009/04/24 16:34:38.64 server  Memory allocated for the default data cache cache: 141622 Kb
00:00000:00000:2009/04/24 16:34:38.65 server  Size of the 2K memory pool: 141622 Kb
00:00000:00000:2009/04/24 16:34:38.65 kernel  Initializing virtual device 0, '/home/sybase/data/master.dat'
00:00000:00000:2009/04/24 16:34:38.65 kernel  Virtual device 0 started using standard unix i/o.
00:00000:00000:2009/04/24 16:34:38.65 kernel  Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2009/04/24 16:34:38.65 kernel  Either the config parameter 'use security services' is set to 0, or ASE does not support use of external security mechanisms on this platform. The Security Control Layer will not be initialized. No external security mechanisms will be supported.
00:00000:00000:2009/04/24 16:34:38.65 kernel  engine 0, os pid 1387  online
00:00000:00000:2009/04/24 16:34:38.65 server  No active traceflags
00:00000:00001:2009/04/24 16:34:38.66 server  Opening Master Database ...
00:00000:00001:2009/04/24 16:34:38.66 server  Loading SQL Server's default sort order and character set
tli_ninit: sninteraface: machname /dev/tcp, netname tcp
00:00000:00002:2009/04/24 16:34:38.66 kernel  ninit:0: listener type: master
00:00000:00002:2009/04/24 16:34:38.66 kernel  ninit:0: listener endpoint: /dev/tcp
00:00000:00002:2009/04/24 16:34:38.66 kernel  ninit:0: listener raw address: \x00021f40c0a8081e0000000000000000
00:00000:00002:2009/04/24 16:34:38.66 kernel  ninit:0: transport provider: T_COTS_ORD
00:00000:00001:2009/04/24 16:34:38.66 server  Recovering database 'master'
00:00000:00001:2009/04/24 16:34:38.66 server  Redo pass of recovery has processed 1 committed and 0 aborted transactions.
00:00000:00001:2009/04/24 16:34:38.67 server  Database 'master' is now online.
00:00000:00001:2009/04/24 16:34:38.67 server  The transaction log in the database 'master' will use I/O size of 2 Kb.
00:00000:00001:2009/04/24 16:34:38.67 server  0 dump conditions detected at boot time
00:00000:00001:2009/04/24 16:34:38.67 server  server is unnamed
00:00000:00001:2009/04/24 16:34:38.67 server  Activating disk 'mpsdat'.
00:00000:00001:2009/04/24 16:34:38.67 kernel  Initializing virtual device 3, '/sybdata/mpsdb.dat'
00:00000:00001:2009/04/24 16:34:38.67 kernel  Virtual device 3 started using standard unix i/o.
00:00000:00001:2009/04/24 16:34:38.67 server  Activating disk 'mpsdbtest'.
00:00000:00001:2009/04/24 16:34:38.67 kernel  Initializing virtual device 9, '/home/sybase/data/mpsdbtest'
00:00000:00001:2009/04/24 16:34:38.67 kernel  Virtual device 9 started using standard unix i/o.
00:00000:00001:2009/04/24 16:34:38.67 server  Activating disk 'ssyscdt'.
00:00000:00001:2009/04/24 16:34:38.67 kernel  Initializing virtual device 5, '/home/sybase/data/ssyscdt'
00:00000:00001:2009/04/24 16:34:38.67 kernel  Virtual device 5 started using standard unix i/o.
00:00000:00001:2009/04/24 16:34:38.67 server  Activating disk 'sysprocsdev'.
00:00000:00001:2009/04/24 16:34:38.67 kernel  Initializing virtual device 1, '/home/sybase/data/systemprocs.dat'
00:00000:00001:2009/04/24 16:34:38.67 kernel  Virtual device 1 started using standard unix i/o.
00:00000:00001:2009/04/24 16:34:38.67 server  Activating disk 'systemdbdev'.
00:00000:00001:2009/04/24 16:34:38.67 kernel  Initializing virtual device 2, '/home/sybase/data/systempdb.dat'
00:00000:00001:2009/04/24 16:34:38.67 kernel  Virtual device 2 started using standard unix i/o.
00:00000:00001:2009/04/24 16:34:38.67 server  Activating disk 'tempdb'.
00:00000:00001:2009/04/24 16:34:38.67 kernel  Initializing virtual device 8, '/home/sybase/data/tempdb.dat'
00:00000:00001:2009/04/24 16:34:38.67 kernel  Virtual device 8 started using standard unix i/o.
00:00000:00001:2009/04/24 16:34:38.67 server  Activating disk 'tempdb1'.
00:00000:00001:2009/04/24 16:34:38.67 kernel  Initializing virtual device 4, '/home/sybase/data/tempdb1'
00:00000:00001:2009/04/24 16:34:38.67 kernel  Virtual device 4 started using standard unix i/o.
00:00000:00001:2009/04/24 16:34:38.67 server  Activating disk 'test3db'.
00:00000:00001:2009/04/24 16:34:38.67 kernel  Initializing virtual device 7, '/home/sybase/data.test3db.dat'
00:00000:00001:2009/04/24 16:34:38.67 kernel  Virtual device 7 started using standard unix i/o.
00:00000:00001:2009/04/24 16:34:38.68 server  Recovering database 'model'.
00:00000:00001:2009/04/24 16:34:38.68 server  The transaction log in the database 'model' will use I/O size of 2 Kb.
00:00000:00001:2009/04/24 16:34:38.69 server  Database 'model' is now online.
00:00000:00001:2009/04/24 16:34:38.69 server  Clearing temp db
00:00000:00001:2009/04/24 16:34:38.69 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2009/04/24 16:34:38.70 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2009/04/24 16:34:38.71 server  Database 'tempdb' is now online.
00:00000:00001:2009/04/24 16:34:38.71 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2009/04/24 16:34:38.71 server  Recovering database 'sybsystemdb'.
00:00000:00001:2009/04/24 16:34:38.72 server  The transaction log in the database 'sybsystemdb' will use I/O size of 2 Kb.
00:00000:00001:2009/04/24 16:34:38.72 server  Database 'sybsystemdb' is now online.
00:00000:00001:2009/04/24 16:34:38.72 server  Recovering database 'sybsystemprocs'.
00:00000:00001:2009/04/24 16:34:38.73 server  The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:00000:00001:2009/04/24 16:34:38.73 server  Database 'sybsystemprocs' is now online.
00:00000:00001:2009/04/24 16:34:38.73 server
*** Bypassing recovery of database id 6

00:00000:00001:2009/04/24 16:34:38.73 server  Starting diagnostics for read failure:
00:00000:00001:2009/04/24 16:34:38.73 server  Device Information:
                              Device number = 3
                              Phyname = /sybdata/mpsdb.dat
00:00000:00001:2009/04/24 16:34:38.73 server  Buffer Information:
                              Buf addr = 0xbfed90c8, Mass addr = 0xbfed90c8
                              Buf pageno = 1049, Mass pageno = 1049, dbid = 6
00:00000:00001:2009/04/24 16:34:38.73 server
                              Buf virtpg = 50332697, Mass virtpg = 50332697
                              Buf stat = 0x1, Mass stat = 0x1008
                              Mass keep = 1, Mass awaited = 0
00:00000:00001:2009/04/24 16:34:38.73 server  Page Information from first read attempt:
                              Page read from disk
                              ppageno = 125, pobjid = 0, pindid = 4
                              pnextpg = 70778882, pprevpg = 262145
                              plevel = 56, pstat = 0x0
                              pts_hi = 5, pts_lo = 0
00:00000:00001:2009/04/24 16:34:38.73 server  Page Information from second read attempt:
                              Page read from disk
                              ppageno = 125, pobjid = 0, pindid = 4
                              pnextpg = 70778882, pprevpg = 262145
                              plevel = 56, pstat = 0x0
                              pts_hi = 5, pts_lo = 0
00:00000:00001:2009/04/24 16:34:38.73 server  SDES Information:
                              dbid = 6, objid = 2, scur.pageid = 1049
                              sstat = 0x2000041, sstat2 = 0x20000
                              suid = 1, cacheid = 0
00:00000:00001:2009/04/24 16:34:38.73 server  PSS Information:
                              pstat = 0x1000, pcurdb = 2, pspid = 1
                              p2stat = 0x110, p3stat = 0x91e
                              plasterror = 0, preverror = 0, pattention = 0
00:00000:00001:2009/04/24 16:34:38.73 server  End diagnostics for read failure:
00:00000:00001:2009/04/24 16:34:38.73 server  Error: 695, Severity: 21, State: 1
00:00000:00001:2009/04/24 16:34:38.73 server  An attempt was made to read logical page '1049' for object '2' in database '6' from disk. Wrong logical page '125' was brought into cache 'default data cache'.
00:00000:00001:2009/04/24 16:34:38.73 kernel  ************************************
00:00000:00001:2009/04/24 16:34:38.73 kernel  curdb = 2 pstat = 0x1000 lasterror = 695
00:00000:00001:2009/04/24 16:34:38.73 kernel  preverror = 0 transtate = 1
00:00000:00001:2009/04/24 16:34:38.73 kernel  curcmd = 0 program =
00:00000:00001:2009/04/24 16:34:38.73 kernel  pc 0x83c3b88 ucbacktrace+0x58(0x0,0x1,0x0,0x0,0x15)
00:00000:00001:2009/04/24 16:34:38.73 kernel  pc 0x8104c5a terminate_process.low.usage+0x4ea(0x0,0xffffffff,0xb1b37e7c,0x81ee68c,0xb1b37e9c)
00:00000:00001:2009/04/24 16:34:38.73 kernel  pc 0x81ee6ac close_network+0xc(0xb1b37e9c,0x81897b7,0x6,0x5f,0x15)
00:00000:00001:2009/04/24 16:34:38.73 kernel  pc 0x81ee68c hdl_default+0x4c(0x6,0x5f,0x15,0x1,0xb1b37ec

00:00000:00001:2009/04/24 16:34:38.73 kernel pc 0x81897b7 sysind_handler+0x27(0x6,0x5f,0x15,0x1,0xb1b37ec

00:00000:00001:2009/04/24 16:34:38.73 kernel  pc 0x805a0ac ex_raise+0x16c(0x6,0x5f,0x15,0x1,0x419)
00:00000:00001:2009/04/24 16:34:38.73 kernel  pc 0x828bfcf wrongpage+0x32f(0xbfed90c8,0xb23946d4,0x1,0x1,0xffffffff)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x80ae0b8 getpage_with_validation.low.usage+0xbb8(0xb23946d4,0x4,0x0,0x0,0x0)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x804d3c4 apl_getnext+0x374(0xb23946d4,0xb23942e8,0xb1b19a20,0xb23946d4,0x4)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x804ce67 getnext+0x77(0xb23946d4,0xb23942e8,0xb1b19a20,0xb29c9dd4,0xb29c9dd4)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x80c9bb0 ind_ides_init.low.usage+0x440(0xb29c9dd4,0x2,0x0,0xb29c52e0,0xb23942e

00:00000:00001:2009/04/24 16:34:38.74 kernel  Handler sysind_handler (0x8189790)  installed by the following function:
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x8056f43 des__syssetup+0x213(0xb2393efc,0xb23942e8,0xb29c52e0,0x15,0x86bc2bc)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x807ebbf des_sysbuild+0x22f(0xb29c52e0,0xb29c52e0,0x626d0,0x5d00,0xffffffff)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x8085bc1 db_fill+0xd1(0xb29c52e0,0x1,0x0,0xb29c52e0,0x1)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x8086757 dbt__fill+0x87(0xb29c52e0,0x1,0x0,0xb2393a20,0x0)
00:00000:00001:2009/04/24 16:34:38.74 kernel  Handler dbt__errhdl (0x8159ab0)  installed by the following function:
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x80db0a1 dbt_get.low.usage+0x71(0x6,0x0,0x0,0xb2393a20,0x6)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x8065275 dbcontext_change+0x15(0x0,0x6,0x0,0x0,0x0)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x806c279 usedb+0x29(0x0,0x6,0x0,0x1,0x0)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x825784b make_log_consistent+0x2b(0x6,0x5,0x493f9,0x6,0x1)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x811fe54 rec_getnextdb_to_recover.low.usage+0x144(0xb1b385dc,0x0,0xb1b385f4,0x1,0x1)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x80a79fc dorecover+0x7c(0x1,0x2e90,0xb2393a20,0x0,0x0)
00:00000:00001:2009/04/24 16:34:38.74 kernel  Handler rec_handle (0x8258200)  installed by the following function:
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x80949b1 ds__recoverdbs+0x1b1(0x0,0x0,0x0,0x0,0x392e3131)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x8096326 dsinit+0x566(0x0,0xb1b387c4,0x6a006a,0x0,0x5374616b)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x83d0fb0 kpexit(0x0,0x5374616b,0x0,0x0,0x0)
00:00000:00001:2009/04/24 16:34:38.74 kernel  pc 0x6a006a (0x0,0x0,0x0,0x0,0x0)
00:00000:00001:2009/04/24 16:34:38.74 kernel  end of stack trace, spid 1, kpid 196611, suid 0

作者: WFCJZ 时间: 2009-04-25 17:43
感觉有些乱，能把你具体处理过程描述一下！

作者: chuxu 时间: 2009-04-28 08:04
库能起来吗？
dbcc dbrepair (XX,dropdb)

作者: shinehom 时间: 2009-05-07 09:33
$ isql -Usa -P
1> dbcc dbrepair(mpsdb,dropdb)
2> go
Msg 2573, Level 16, State 1:
Line 1:
Database 'mpsdb' is not marked suspect. You cannot drop it with DBCC.
DBCC execution completed. If DBCC printed error messages, contact a user with
System Administrator (SA) role.

作者: xiaobudian 时间: 2009-05-19 15:14
用dbcc来drop库，首先库的状态要是suspend，就是系统表sysdabases中status的值要包含256。

作者: zolowgc 时间: 2011-09-10 00:29
唉……，同病相怜，被hoobylu这么一说，恢复数据估计是没指望了。

作者: zolowgc 时间: 2011-09-10 00:30
唉……，同病相怜，被hoobylu这么一说，恢复数据估计是没指望了。

欢迎光临 Chinaunix (http://bbs.chinaunix.net/)