aboutsummaryrefslogtreecommitdiff
path: root/e2fsprogs/e2fsck.h
diff options
context:
space:
mode:
authorRob Landley <rob@landley.net>2006-05-05 17:29:09 +0000
committerRob Landley <rob@landley.net>2006-05-05 17:29:09 +0000
commitd8f6601502d8b0c124c3389a9c32b85d36f33869 (patch)
treebc84566f7142bb02dfc3a1178e5bce73ba7b62a0 /e2fsprogs/e2fsck.h
parent2c39eee805e4bc875eab737e529feb0c4c91f50e (diff)
downloadbusybox-d8f6601502d8b0c124c3389a9c32b85d36f33869.tar.gz
Another patch from Garrett: remove bad block bitmap checking code. Everything
produced in the list ten years has some variant of internal error correction (disks, cdrom, flash), so if it has user-visible bad blocks on it the hardware has exhausted its remapping reserve and is dying, and you need to get your data off pronto. (The one exception I can think of is floppies, and I don't care.)
Diffstat (limited to 'e2fsprogs/e2fsck.h')
-rw-r--r--e2fsprogs/e2fsck.h2
1 files changed, 0 insertions, 2 deletions
diff --git a/e2fsprogs/e2fsck.h b/e2fsprogs/e2fsck.h
index 0957f20a8..43080d24e 100644
--- a/e2fsprogs/e2fsck.h
+++ b/e2fsprogs/e2fsck.h
@@ -518,7 +518,6 @@ struct e2fsck_struct {
ext2fs_inode_bitmap inode_used_map; /* Inodes which are in use */
ext2fs_inode_bitmap inode_bad_map; /* Inodes which are bad somehow */
ext2fs_inode_bitmap inode_dir_map; /* Inodes which are directories */
- ext2fs_inode_bitmap inode_bb_map; /* Inodes which are in bad blocks */
ext2fs_inode_bitmap inode_imagic_map; /* AFS inodes */
ext2fs_inode_bitmap inode_reg_map; /* Inodes which are regular files*/
@@ -612,7 +611,6 @@ struct e2fsck_struct {
int fs_fast_symlinks_count;
int fs_fifo_count;
int fs_total_count;
- int fs_badblocks_count;
int fs_sockets_count;
int fs_ind_count;
int fs_dind_count;