On Apr 13, Rogier Wolff wrote:
> Anyway, if a disk finds a block to be unreadable for some reason, it
> cannot do anything else but report error. Possibly if you issue a
the disk can relocate a block when it gets soft (correctable) read errors
_before_ real data gets lost.
> write request for that block, it could reallocate the block, however,
> I've tried "fixing" disks with badblocks by doing a
>
> dd if=/dev/zero of=/dev/<disk>
>
> but the bad blocks remained in place.
>
> So how DO I trigger a reallocation of a grown bad block?
from SCSI-2 specs (s2-r10l.txt) :
9.2.10 REASSIGN BLOCKS command (Operation code 07h)
The REASSIGN BLOCKS command (see table 129) requests the target to
reassign the defective logical blocks to another area on the medium set
aside for this purpose. The target should also record the location of the
defective logical blocks to the grown defect list if such a list is
supported. More than one physical or logical block may be relocated by
each defect descriptor sent by the initiator. This command does not alter
the contents or location of the Plist (see 9.2.1, FORMAT UNIT command).
Harald
--
All SCSI disks will from now on ___ _____
be required to send an email notice 0--,| /OOOOOOO\
24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig, \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik // / \\ \
koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:20 EST