• Home
  • Raw
  • Download

Lines Matching refs:superblock

102 Fix option syntax in dumpe2fs for explicit superblock and blocksize
118 Add support for setting new superblock fields to debugfs's
314 filesystem check is required before backing up the superblock due to
393 errors (i.e., if superblock mount time or last write time is in the
406 Fix e2fsck so that if the superblock is corrupt, but still looks
407 vaguely like an ext2/3/4 superblock, that it automatically tries to
408 fall back to the backup superblock, instead of failing with a hard
577 superblock, so that it won't accidentally find a superblock that was
579 backup superblock.
591 recovering a journal until the master superblock has been confirmed as
607 the backup journal information from the superblock was successfully
638 Fix MD superblock detection, and make sure the correct UUID is
639 reported from the MD superblock.
723 superblock to fix cross-architectural portability for htree
775 the superblock. Omit by default printing superblocks that are likely
902 Add test to make sure the ext2 superblock structure is 1024 bytes.
912 callers of ext2fs_open() should not be touching any superblock fields
942 table right up after the superblock (if present) in order to minimize
970 E2fsck will detect if the superblock's last mount field or last write
978 E2fsck now checks to see if the superblock hint for the location of
1051 checking the FAT superblock values.
1125 Clean up the blkid library by making the superblock and generic i/o
1235 If the superblock last mount time indicates that the system clock may
1239 superblock's last write time looked insane.)
1451 superblock was corrupt. E2fsck's standards for what is a ridiculous
1475 can set most superblock fields, including the date/time fields and
1476 some of the more newsly added superblock fields.
1522 Tune2fs will not mark rewrite the superblock if the feature bitmasks
1693 replayed when using an alternate superblock.
1705 block group descriptor or a superblock and a bad block indirect block.
1710 in the superblock and symlinks created by SE Linux to be cleared
1720 trying to print the location of the backup superblock.
1726 superblock. E2fsck will automatically save the journal information in
1727 the superblock if it is not there already, and will use it if the
1731 also have journal location written to the superblock as well.
1733 journal information in the superblock.
1799 Centralize code which calculates the location of the superblock
2016 Changed dumpe2fs to always display the superblock fields relating to
2037 bitmaps for sparse superblock filesystems and incorrectly marked
2140 superblock and block group descriptors when important changes are made
2170 superblock write time to determine whether or not it can safely use
2202 We have added a new superblock field, s_mkfs_time, which indicates
2214 Add support for storing default mount options in the superblock, so
2269 E2fsck now only updates the master superblock in all cases. This
2299 fields in the superblock.
2391 superblock used by other filesystems. (Addresses Debian bug #147256.)
2532 using a backup superblock, since the needs_recovery flag will never be
2533 set in the backup superblock copies.
2535 E2fsck now automatically finds the backup superblock/group descriptors
2536 even when the primary superblock is completely destroyed for 2k and 4k
2539 the backup superblock number.)
2555 E2fsck will check and fix botched ext3 V1 to V2 superblock updates by
2557 superblock is version 1 superblock.
2621 superblock fields which can be set using the command.
2623 Debugfs's rm and kill_file command now updates the superblock free block
2685 statistics in the bitmaps, block group descriptors, and superblock
2711 E2fsck will now not fall back to an alternate superblock if the user
2712 specifies the superblock location explicitly on the command-line.
2714 superblock and block groups are slightly corrupted, but the backup
2752 other filesystem/raid superblock magic values so that programs like
2807 of all of the superblock and block group descriptors.
2829 E2fsck will set the EXT2_ERROR_FS flag if the journal superblock
3005 inodes in the superblock, and clear those inodes before starting the
3082 information in hex, and also prints the location of the superblock and
3085 Mke2fs now clears the ext2 superblock before it starts creating a
3086 filesystem, so that the superblock magic number is only written if the
3093 by dumpe2fs) to print the superblock header information. This is more
3097 user to set arbitrary superblock fields.
3146 the filesystem close functions to only update the superblock, and to
3212 Dumpe2fs will display the superblock journaling information if the
3254 E2fsck now calculates the correct location of the backup superblock in
3259 but could cause a valid superblock to be rejected in extreme cases.
3260 Other checks for validating superblock values were made more
3296 blocksize and superblock location to be specified, and the -c option
3312 argument passed to ext2 library while initializing superblock".
3351 superblock.
3442 bit in the in-core superblock image. The new functionality is more
3489 Debugfs can now set and print filesystem features in the superblock
3491 set of features when listing the superblock.
3503 E2fsck now makes some additional sanity checks on the superblock to
3505 values in the superblock are unresonable (but the superblock otherwise
3566 sparse superblock feature enabled. The sparse superblock feature is
3616 to specify the superblock and blocksize when opening a filesystem.
3780 the superblock copies. This makes it easier to automatically
3799 Fixed a minor bug in mke2fs so that all groups with bad superblock
3820 the bad block was in a non-primary superblock or block group
3822 use and there is a bad block where a superblock or block group
3824 superblock.
3843 superblock is corrupt.
3926 superblock or block group descriptors and block bitmaps, inode
3942 superblock backups to avoid running over 80 columns when making a
3990 the sparse superblock option isn't supported by most kernels yet (1.2
4076 E2fsck will attempt to determine the correct superblock number and
4171 Added check to write_bitmaps() to make sure the superblock doesn't get
4174 Added checking of the new feature set fields in the superblock, to
4260 only write out the backup superblock and the back block descriptors if
4306 Add support for new fields in the ext2 superblock --- volume name,
4313 the creator_os field in the superblock to correctly handle different
4330 Make the message issued by e2fsck when the superblock is corrupt less
4332 "corrupt superblock" message might be that the partition might not be
4336 an illegal superblock where the blocksize is zero. (f_crashdisk is
4349 storage for the superblock, inodes, and directory blocks. This
4482 certain superblock consistency checks fail. Previously it continued