cancel
Showing results for 
Search instead for 
Did you mean: 
Trevor
Commander Commander
Commander
  • 22 Views

tune2fs

I've got a filesystem that is type btrfs.  When I execute the tune2fs command on it,
I get the following output:

sudo tune2fs -l /dev/sda5
tune2fs 1.47.0 (5-Feb-2023)
tune2fs: Bad magic number in super-block while trying to open /dev/sda5
/dev/sda5 contains a btrfs file system labelled 'fedora'

 

I have another filesystem that is type ext4.  When I execute the tune2fs coommand on
it, I get the following output:

sudo tune2fs -l /dev/sda2
tune2fs 1.47.0 (5-Feb-2023)
Filesystem volume name: <none>
Last mounted on: /boot
Filesystem UUID: f5191fc4-313b-4f75-b426-c817db0cf9ef
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index orphan_file filetype n
eeds_recovery extent 64bit flex_bg metadata_csum_seed sparse_super large_file huge_file dir_
nlink extra_isize metadata_csum orphan_present
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 65536
Block count: 262144
Reserved block count: 13107
Overhead clusters: 12949
Free blocks: 123272
Free inodes: 65133
First block: 0
Block size: 4096
Fragment size: 4096
Group descriptor size: 64
Reserved GDT blocks: 127
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Thu Jun 20 07:42:19 2024
Last mount time: Fri Nov 21 15:06:01 2025
Last write time: Fri Nov 21 15:06:01 2025
Mount count: 1
Maximum mount count: -1
Last checked: Fri Nov 21 15:06:00 2025
Check interval: 0 (<none>)
Lifetime writes: 1797 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 3ba92535-267f-4d0e-a968-2b0f705ec5e1
Journal backup: inode blocks
Checksum type: crc32c
Checksum: 0x7493e025
Checksum seed: 0xb0e75c98
Orphan file inode: 12

/dev/sda5 filesystem type:  btrfs

/dev/sda2 filesystem type:  ext4

 

Okay, now that you've been able to wade through all of the preliminary,
my question is, what could possibly be causing the very abbreviated 
output for the /dev/sda5 device?  Oh, by the way,  /devsda5 is my root
filesystem!!!

 

Trevor "Red Hat Evangelist" Chandler
Labels (3)
0 Kudos
0 Replies
Join the discussion
You must log in to join this conversation.