home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!charnel!rat!usc!zaphod.mps.ohio-state.edu!swrinde!news.dell.com!natinst.com!cs.utexas.edu!bcm!lib!dfenyes
- From: dfenyes@thesis1.med.uth.tmc.edu (David Fenyes,Neurobiol/Anatomy,5705,7901935)
- Newsgroups: comp.os.linux
- Subject: Re: ext fs question (.badblocks)
- Message-ID: <8120@lib.tmc.edu>
- Date: 14 Dec 92 19:38:45 GMT
- References: <1992Dec14.133843.2536@jussieu.fr> <1992Dec14.163449.15147@aston.ac.uk>
- Sender: usenet@lib.tmc.edu
- Organization: University of Texas Medical School at Houston
- Lines: 15
- Nntp-Posting-Host: thesis1.med.uth.tmc.edu
-
- In article <1992Dec14.163449.15147@aston.ac.uk> evansmp@uhura.aston.ac.uk (Mark Evans) writes:
- >Remy CARD (card@masi.ibp.fr) wrote:
- >: 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).
-
- Is there a way to easily read the bad blocks list to verify that all the
- bad blocks have been identified? (or even to modify it after the fs has
- been created?)
-
- David.
- --
- David Fenyes dfenyes@thesis1.med.uth.tmc.edu
- University of Texas Medical School Houston, Texas
-