Re: Missing database file names

2010-06-05 Thread Jesse F. Hughes
"Jesse F. Hughes" writes: > "Jesse F. Hughes" writes: > >> r...@pw:/var/lib/mysql/mythconverg# myisamchk -o recorded.MYI >> Warning: option 'key_buffer_size': unsigned value 18446744073709551615 >> adjusted to 4294963200 >> Warning: option 'read_buffer_size': unsigned value 18446744073709551615

Re: Missing database file names

2010-06-04 Thread Jesse F. Hughes
"Jesse F. Hughes" writes: > r...@pw:/var/lib/mysql/mythconverg# myisamchk -o recorded.MYI > Warning: option 'key_buffer_size': unsigned value 18446744073709551615 > adjusted to 4294963200 > Warning: option 'read_buffer_size': unsigned value 18446744073709551615 > adjusted to 4294967295 > Warnin

Re: Missing database file names

2010-06-04 Thread Jesse F. Hughes
(I emailed this to Martin and Jaime rather than to the discussion group, so I'm re-sending it.) Martin Gainty writes: > Jesse ..please keep us apprised on your progress..we would like to > know how fubar the db can be before it becomes 'unrecoverable' Well, I'm not having much luck so far. I h

Re: Missing database file names

2010-06-04 Thread Jaime Crespo Rincón
2010/6/4 Jesse F. Hughes : > Is it possible to build a .MYI file "from scratch"? > > I have found a file that I believe is recorded.MYD.  I have the .frm > file as well, but I don't think that recorded.MYI survived the > file system event. Yes, the mysql utility "myisamchk" and the REPAIR command

Re: Missing database file names

2010-06-04 Thread Jesse F. Hughes
Is it possible to build a .MYI file "from scratch"? I have found a file that I believe is recorded.MYD. I have the .frm file as well, but I don't think that recorded.MYI survived the file system event. -- "No feeling sympathy for mathematicians who start marching with signs like 'Will work fo

Re: Missing database file names

2010-06-03 Thread Jesse F. Hughes
Dan Nelson writes: > In the last episode (Jun 02), Jesse F. Hughes said: >> After a recent hard drive kerfluffle and the results of fsck, I'm left >> with a slew of jumbled database files. The file command can tell me the >> file types, like so: >> >> #15901614: MySQL table definition file Vers

Re: Missing database file names

2010-06-03 Thread Jesse F. Hughes
Dan Nelson writes: > In the last episode (Jun 02), Jesse F. Hughes said: >> After a recent hard drive kerfluffle and the results of fsck, I'm left >> with a slew of jumbled database files. The file command can tell me the >> file types, like so: >> >> #15901614: MySQL table definition file Vers

Re: Missing database file names

2010-06-02 Thread Dan Nelson
In the last episode (Jun 02), Jesse F. Hughes said: > After a recent hard drive kerfluffle and the results of fsck, I'm left > with a slew of jumbled database files. The file command can tell me the > file types, like so: > > #15901614: MySQL table definition file Version 10 > #15901615: MySQL MI

Missing database file names

2010-06-02 Thread Jesse F. Hughes
After a recent hard drive kerfluffle and the results of fsck, I'm left with a slew of jumbled database files. The file command can tell me the file types, like so: #15901614: MySQL table definition file Version 10 #15901615: MySQL MISAM compressed data file Version 1 #15901617: MySQL table defin