Christian Kujau wrote:
On Tue, May 27, 2008 13:25, Jelle de Jong wrote:
http://www.powercraft.nl/temp/fsck-crash-info.txt.gz
So, you've ran fsck but did not try to repair yet, right? If so and you do
happen to have a spare 750 GB *now*, try to dd(1) your data to this spare
disk: then you can fsck your filesystems as many times as you want to.
I have not run fsck to repair with the previous disk this when wrong, so
I will buy a spare 750 GB disk today, and make a dd image from the
one disk to the other.
Are there any (USB-)device related errors in the syslogs? We don't wanna
run fsck when the underlying device is unstable. dd(1) would be a good way
to find out.
I have seen the usb bus reset errors before but I cant put my finger on
the broken part. I have now been copying data from one usb disk to an
other usb disk without any usb error messages and this is a 4 hour transfer.
Also, is LVM or RAID or sth. like this involved? Searching the net for
these errors brought up quite a few hits related to LVM b0rkage...
No RAID setup, but i am planning a software raid setup soon.
However, let's hope some ext3 hacker will comment on the logs...
yes lets hope so...
C.
_______________________________________________
Ext3-users mailing list
Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users
