![]() ![]() Primary superblock at 0, Group descriptors at 1-2048īlock bitmap at 2049 (+2049), Inode bitmap at 2065 (+2065)Ģ8637 free blocks, 2036 free inodes, 1 directories, 2034 unused inodes ![]() Journal features: journal_incompat_revoke journal_64bit Here's the (truncated) output: Filesystem volume name: įilesystem UUID: fef00ffc-5341-4158-9279-88cad6cc211fįilesystem features: has_journal ext_attr resize_inode dir_index filetype extent 64bit flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isizeįilesystem created: Wed Jan 16 11:07:07 2013ĭirectory Hash Seed: c7ec9ee0-002b-431d-a37c-33db922c6057 Moreover, dumpe2fs sees the correct block count ( Block count: 4294967296, a 16TB filesystem). ![]() I've run dumpe2fs to find the other copies of the superblock, but no matter which of them I add after fsck.ext4s -b option, I get the exact same output. Is corrupt, and you might try running e2fsck with an alternate superblock: If the device is valid and it really contains an ext2/ext3/ext4įilesystem (and not swap or ufs or something else), then the superblock The superblock could not be read or does not describe a valid ext2/ext3/ext4įilesystem. After a crash, I've got an Ext4 filesystem (on an LVM LV) that gives the following error when running fsck.ext4 -nf: e2fsck 1.42.12 (2)Ĭorruption found in superblock. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |