From mboxrd@z Thu Jan 1 00:00:00 1970 From: Whit Blauvelt Subject: Marking bad blocks Date: Sat, 19 Jul 2003 23:30:04 -0400 Message-ID: <20030720033004.GA6519@free.transpect.com> Mime-Version: 1.0 Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com Content-Disposition: inline List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: reiserfs-list@namesys.com Hi, I'm trying to use the add-bad-blocks.c script provided on the site, but with both gcc 2.95.3 and 3.2.2 I get: "undefinded reference to `concat'" when I try to do "gcc add-bad-blocks.c". Is there something else I need to do to compile it successfully? Or is it just bad code? Why isn't whatever the necessary step is spelled out on the site? And, the instruction page only mentions patches to old versions of the kernel. Is the patch to support this now standard in the Reiserfs of kernel 2.4.21? I like Reiserfs a lot, and use it extensively, but for the second time I'm having serious trouble because of its lack of bad block handling. The Website is full of posturing about "If you have a problem, it's probably your hardware, not a real bug." Fine, this is hardware. The first time around a drive problem totally trashed a system. Now it looks like the Reiser code is better (in 2.4.21 it doesn't crash the system as it does on the same drive with 2.4.19 - looks like something was improved either in Reiser or general file system support in the kernel). But an out of date page on handling bad blocks with a utility that doesn't compile doesn't evidence thorough care. Thanks for any advice on how to actually take care of this problem short of throwing out a drive (or going to another file system) just because a couple of blocks are bad. Whit