From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Oglesby Subject: Re: Reiserfs 1300G partition on lvm problem ... Date: Tue, 31 May 2005 08:51:36 -0500 Message-ID: <429C6BE8.4090906@teleformix.com> References: <1117392967.29669.ezmlm@namesys.com> <429A1742.8030504@mh.be> <200505292137.j4TLbarw017197@turing-police.cc.vt.edu> <429AAFDC.4050208@mh.be> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <429AAFDC.4050208@mh.be> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Matthias Barremaecker Cc: Valdis.Kletnieks@vt.edu, reiserfs-list@namesys.com Matthias Barremaecker wrote: > Hi, > > Thanx for your reply. > > The data is not THAT importend, all our importend data is backuped 4 > times, inc. original (well, 3 times now, since the 1300gig machine is > broke). > > I did a bit furtur reasearch and maybe this is something to think about > if you use reiserfs : > > I did a bad block check and I have 10 bad blocks of 4096bytes on 1300Gig > and ... that is the reason reiserfs will not work anymore. > > I guess this sux. I rather have that the data on the bad blocks is just > corupted but the rest is accesseble. > > I'm doing a --rebuild-tree with the bad block list. Hopes this works. > > > Aren't there any tools to substract data from a broken reiserfs partition ? > > > kind regardes, > > Matthias. > > > I'm currently in a similar situation: 1TB (RAID-5) ReiserFS filesystem running on RedHat 7.2 with a Promise SX6000 controller. Everything was running stock version/firmware/BIOS, and it suddently developed 39 bad blocks after a power outage. reiserfsck --rebuild-tree (version 3.6.4, the latest for RH 7.2) failed to complete after the controller kept hard locking/crashing. So, I've compiled a plain 2.4.30 kernel (from kernel.org, not RedHat), updated the BIOS/Firmware on the SX6000, and compiled and installed the latest reiserfsprogs (3.6.19, I believe?), and have been running badblocks (non-destructive) for the last four days. Nothing has turned up so far. I'm hoping the next time I run a --rebuild-tree, it will be able to complete. I really do need to get the data off of this filesystem. Good luck with your recovery. --Dan > Valdis.Kletnieks@vt.edu wrote: > >> On Sun, 29 May 2005 21:25:54 +0200, Matthias Barremaecker said: >> >> >>> but that sais it is a fysical drive error >> >> >> >> Physical drive errors. Your hardware is broken. Isn't much that >> Reiserfs >> can do about it. >> >> >>> What can I do. >> >> >> >> 1) Call whoever you get hardware support from. >> >> 2) Be ready to restore from backups. >> >> 3) If you didn't have RAID-5 (or similar) set up, or a good backup, >> consider >> it a learning experience. >> >> If your data is important enough that you'll care if you lose it, you >> should take >> steps to make sure you won't lose it... It's that simple. >> >> (Just for the record, if we have important info, it gets at least >> RAID5, a >> backup to tape or other device, *and* a *second* backup off-site. And >> my shop >> is far from the most paranoid about such things.) >> >