[Gllug] JFS and bad blocks

[Jack Bertram]

* Martin A. Brooks <martin at hinterlands.org> [051005 11:10]:
> Jack Bertram wrote:
> >I can't seem to work out how to test a JFS filesystem for bad blocks and
> >mark them bad. Anyone using it and can give advice?
> 
> I may be misunderstanding but what do bad blocks have to do with a 
> filesystem?
> 
> All modern hard disks remap bad sectors on the fly.  This is (allegedly) 
> one reason why manufacturers quote hard disk capacity as 10^n rather 
> than 2^n.  The overhead gives them unused sectors to remap to.
> 
> If a disk had a bad block that's exposed to the host then the filesystem 
> is irrelevant - all filesystems using the partition containing the bad 
> block will be affected.
> 
> Perhaps you mean that you want to have the filesystem exclude writing to 
> blocks that are known to be bad?  If so then you either have an old disk 
> that doesn't do on-the-fly remapping or your disk has run out of sectors 
> to remap to.  In either case you should seriously consider simply 
> replacing the hard disk - they are stupidly cheap these days.

Well, I may be being stupid: but I have a disk giving read errors.  I
wanted to check whether this was filesystem corruption or disk problems,
and running badblocks gave a list of bad blocks - but fsck for jfs
doesn't have a -c option.  So I was asking for a way of telling the
filesystem not to use these.  How should I tell whether it's a disk
problem or a filesystem problem?

The disk is a modern SATA Maxtor, I believe.

jack
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20051005/febf68e2/attachment.pgp>
-------------- next part --------------
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug