home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!mcsun!julienas!jussieu!card
- From: card@masi.ibp.fr (Remy CARD)
- Subject: Re: ext fs question (.badblocks)
- Message-ID: <1992Dec15.084358.17478@jussieu.fr>
- Sender: news@jussieu.fr (Le Facteur)
- Nntp-Posting-Host: ares.ibp.fr
- Organization: Laboratoire MASI - Universite Pierre et Marie Curie - Paris - France
- References: <1992Dec14.133843.2536@jussieu.fr> <1992Dec14.163449.15147@aston.ac.uk> <8120@lib.tmc.edu>
- Date: Tue, 15 Dec 1992 08:43:58 GMT
- Lines: 31
-
- In article <8120@lib.tmc.edu> dfenyes@thesis1.med.uth.tmc.edu (David Fenyes,Neurobiol/Anatomy,5705,7901935) writes:
- >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?)
-
- You can add bad blocks to the list with efsck. 'efsck -t' tests for
- bad blocks in a fs and adds new bad blocks to the list. 'efsck -b file' reads
- a bad blocks list from the file and adds them to the list.
-
- Unfortunately, there is no way to print the bad blocks list. Seems
- like I must add an option to efsck for the next release.
-
- >
- >David.
- >--
- >David Fenyes dfenyes@thesis1.med.uth.tmc.edu
- >University of Texas Medical School Houston, Texas
-
-
- Remy
- --
-
- Remy Card
- card@masi.ibp.fr
-