Updating bad block inode browns phases of dating
Reiser filesystems are dynamic so you'll never have an issue with them. The inode-size value must be a power of 2 larger or equal to 128.The larger the inode-size the more space the inode table will consume, and this reduces the usable space in the filesystem and can also negatively impact performance.
The location of the backup superblock is dependent on the filesystem's blocksize.
in this case smartctl command gives us an LBA number, such as 0x01e44ccc (31739084 in base 10), which is the LBA number offset from the beginning of the disk using LBA 0 as the first block.
if sdd3 partition starts at LBA 31664128 (see fdisk output in step 1) then the LBA block number offset from beginning of partition is 31739084 - 31664128 = 74956.
To summarize, we figure-out the block address (2048) of file1with debugfs-stat command, then replaced file2block address 2049 with 2048.
By following unmounting and remounting - we ensure our above changes written to disk.umount /mnt mount -o sb=393216 /dev/xvdb /mnt -t ext3 Now go head print file1file2cat /mnt/file1/mnt/file2I hope you can spot the difference between our previous file1and file2output ans this one, right? Since we can't run file system checker (fsck) on mounted partitions umount /mnt e2fsck /dev/xvdb e2fsck 1.41.12 (17-May-2010) e2fsck: Superblock invalid, trying backup blocks... Pass 1: Checking inodes, blocks, and sizes Running additional passes to resolve blocks claimed by more than one inode... If you are wondering what values to put, just look above..no,not the sky :p just scroll above for original mode values You might have seen this error message sometimes, lets recreate it.
e2fsck is used to check the ext2/ext3/ext4 family of file systems.