From: evansmp@uhura.aston.ac.uk (Mark Evans) Subject: Re: ext fs question (.badblocks) Date: 14 Dec 1992 16:34:49 GMT
Remy CARD (card@masi.ibp.fr) wrote:
: In article <orman.724229253@vislab.me.iastate.edu> orman@iastate.edu (David L Orman) writes:
: >does mkefs still make a /.badblocks with the -c option? I was
: >reinstalling and tried it and I didnt get a .badblocks I got made
: >errors as the scan was done however, so I know there is some bad spots.
: >the command I used was:
: >mkefs -c /dev/hdb1 xxxxxx
: >
: >I forget the number of blocks, anyway its an RLL drive with known bad
: >areas so whats the deal.... is it ok or not?
: >
:
: mkefs now uses a reserved inode (inode #2) to store the bad blocks.
: This inode does not appear in the filesystem tree any more because it was
: leading to problems (root could delete the .badblocks file or save it during
: a backup).
This is a common way of implimenting a bad block list, fsck will not
complain about this inode being unreferenced.
:
: So, even if you don't see a .badblocks file with ls, don't worry. The
: bad blocks are recorded and won't be use in the fs.
It also means that back-up utilities (e.g. tar) will not pick up the
bad blocks file