Hi Dean,
Thanks for the reply...
I indeed also thought of the mistake that I reversed the parameters...
Though I must say that all the other tables in the directory (luckily) still worked..
But reading your words it looks to me as if not a easy (unpossible) table to repair..
This really was bad luck, the machine the database is on makes a backup every night at
1:00 clock...
I started working on Monday morning.. Continued in the midday and evening.. When it
was about 12:15 in the
night I made the mistake.. If would have been 50 minutes later, I would probably have
had an very recent backup..
I even make some hourly rotating backups of some (important) tables, but these tables
weren't included in the script.. :-(
Well, O.K.. A hard way to learn that unix always does what you give it to do without
letting you play the o.k/cancel button game....
I indeed have the raw data... But it consists of about 1000 lines of tect of data for
a small accountancy program which is made with
PHP and uses
Mysql to store the data.. These 1000 records were just all booked correctly by
hand... :-)
Luckily the second time you do something everything goes quicker.. I restarted this
morning at 9:00 and at 14:00 I finished the
work..
Luckily the damage was not that high and I leaned again to respect the unix commands..
:-)
Thanks for the help..
Bye Bye
David
> Most likely you reversed the source and destination parameters in the tar
> command and stepped on your table(s). Usually, if this was indeed the cause
> of the problem, other tables in the directory would also be damaged, if any
> type of file globing was used. I don't suppose you have a backup of your
> original raw data?
>
>
> DG
>
> -----Original Message-----
> From: David Bouw [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 17, 2001 6:17 PM
> To: [EMAIL PROTECTED]
> Subject: Hoping for Crash recovery Miracle
>
>
> Hi there,
>
> I would really appreciate any help someone can give on the following awful
> problem..
>
> I have been working all day on filling a table with data. (Small records..)
> Because I have a table which I filled with some binary data someone asked me
> how big this will get..
> I looked at the directory and did a 'tar cfvz' command to (pack the data to
> a file) an look how big the file would get..
>
> I am not sure what I did wrong, but I got an error which I didn't look at
> very carefully
>
> After this it looked as if I damaged the table I worked on all day....
>
> The table consists of: 4440 records.. On this moment I can see this number
> listed when I do a:
> select count(*) from tablename... (So far so good)
>
> When I do a select * from ... this table I get the following error:
> Warning: MySQL: Unable to save result set in
> /www/websites/mubo/login/phpmyadmin/sql.php3 on line 65
> (This ss a error from the PHP script doing the query, but the error: 'MySQL:
> Unable to save result set' probably is from mysql..)
>
> The three table files look as follow:
> 2.8M -rw-r----- 1 root root 2.7M Sep 18 00:37
> mubo_boekhoud_boekhoud.ISD
> 140k -rw-r----- 1 root root 135k Sep 18 00:37
> mubo_boekhoud_boekhoud.ISM
> 12k -rw-r----- 1 root root 8.6k Sep 18 00:37
> mubo_boekhoud_boekhoud.frm
>
> When I do a isamchk mubo_boekhoud_boekhoud I get the following:
>
> [root@jaguar test]# isamchk mubo_boekhoud_boekhoud
> Checking ISAM file: mubo_boekhoud_boekhoud
> Data records: 4440 Deleted blocks: 0
> - check file-size
> isamchk: warning: Size of datafile is: 2878557 Should be: 403794
> - check delete-chain
> - check index reference
> - check data record references index: 1
> - check data record references index: 2
> - check data record references index: 3
> - check record links
> isamchk: error: Wrong bytesec: 31-139-8 at linkstart: 0
> ISAM-table 'mubo_boekhoud_boekhoud' is corrupted
> Fix it using switch "-r" or "-o"
>
> What are my options...??? If I could only get the data in a readable form, I
> could at least get back some data..
> The .ISD file should be O.K, is it possible to regenerate the .ISM files..
> ??
>
> What can I try.. If anyone think I still have some options I will very much
> appreciate to hear this..
>
> I did try a isamchk -o command, this was the result:
>
> [root@jaguar test]# isamchk -o mubo_boekhoud_boekhoud
> - recovering ISAM-table 'mubo_boekhoud_boekhoud.ISM'
> Data records: 4440
> Wrong bytesec: 31-139- 8 at 0; Skipped
> Data records: 0
> [root@jaguar test]#
>
> The .ISD file is truncated to 0 bytes and I then have a table with 0
> records...
>
> Thankyou very much for any help..
>
> With kind regards
> David ..
>
>
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
