[Bug 264450] ufs "Cannot find file system superblock" on main 2573e6ced99616f2edccf97fb0f9283a84148246, perfectly usable on 12.3
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 264450] ufs "Cannot find file system superblock" on main 2573e6ced99616f2edccf97fb0f9283a84148246, perfectly usable on 12.3"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 264450] ufs: Partition recognized on 12.3 not recognized on CURRENT (2573e6ced996): Cannot find file system superblock .. Invalid fstype: Invalid argument"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 04 Jun 2022 16:14:16 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264450 Bug ID: 264450 Summary: ufs "Cannot find file system superblock" on main 2573e6ced99616f2edccf97fb0f9283a84148246, perfectly usable on 12.3 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: d8zNeCFG@aon.at Created attachment 234446 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234446&action=edit First megabyte of da0s4d Scenario: - A disk which, if attached to a 12.3 system, shows up as: [0]# ll /dev/da0* crw-r----- 1 root operator 0x75 Jun 4 17:39 /dev/da0 crw-r----- 1 root operator 0x79 Jun 4 17:39 /dev/da0s1 crw-r----- 1 root operator 0x7b Jun 4 17:39 /dev/da0s4 crw-r----- 1 root operator 0x83 Jun 4 17:39 /dev/da0s4a crw-r----- 1 root operator 0x84 Jun 4 17:39 /dev/da0s4b crw-r----- 1 root operator 0x85 Jun 4 17:39 /dev/da0s4d [0]# gpart show da0 => 63 976773105 da0 MBR (466G) 63 1985 - free - (993K) 2048 761726968 1 ntfs (363G) 761729016 215044152 4 freebsd [active] (103G) [0]# gpart show da0s4 => 0 215044152 da0s4 BSD (103G) 0 16 - free - (8.0K) 16 4194304 1 freebsd-ufs (2.0G) 4194320 10485760 2 freebsd-swap (5.0G) 14680080 200364072 4 freebsd-ufs (96G) [0]# - The two filesystems can be fsck'd o.k.: 0]# fsck /dev/da0s4a ** /dev/da0s4a ** Last Mounted on /d/26s4a ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 3627 files, 131623 used, 376160 free (3256 frags, 46613 blocks, 0.6% fragmentation) ***** FILE SYSTEM IS CLEAN ***** [0]# fsck /dev/da0s4d ** /dev/da0s4d ** Last Mounted on /d/26s4a/usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1269131 files, 10661916 used, 13593544 free (15728 frags, 1697227 blocks, 0.1% fragmentation) ***** FILE SYSTEM IS CLEAN ***** [0]# - And they can be mounted: [0]# mount /dev/da0s4a /mnt [0]# mount /dev/da0s4d /mnt/usr [0]# umount /mnt/usr [0]# umount /mnt [0]# - Now connecting this same disk to a system running main 2573e6ced99616f2edccf97fb0f9283a84148246 Result: - Now the da0s4d partition is not recognized as a UFS filesystem. - The partitions do show up: [0]# ll /dev/da* crw-r----- 1 root operator 0x7b Jun 4 17:08 /dev/da0 crw-r----- 1 root operator 0x5d Jun 4 18:11 /dev/da0s1 crw-r----- 1 root operator 0x5f Jun 4 18:11 /dev/da0s4 crw-r----- 1 root operator 0x7d Jun 4 18:11 /dev/da0s4a crw-r----- 1 root operator 0x7e Jun 4 18:11 /dev/da0s4b crw-r----- 1 root operator 0x7f Jun 4 18:11 /dev/da0s4d [0]# gpart show da0 => 63 976773105 da0 MBR (466G) 63 1985 - free - (993K) 2048 761726968 1 ntfs (363G) 761729016 215044152 4 freebsd [active] (103G) [0]# gpart show da0s4 => 0 215044152 da0s4 BSD (103G) 0 16 - free - (8.0K) 16 4194304 1 freebsd-ufs (2.0G) 4194320 10485760 2 freebsd-swap (5.0G) 14680080 200364072 4 freebsd-ufs (96G) [0]# - But fsck'ing yields: [0]# fsck /dev/da0s4a ** /dev/da0s4a ADD SUPERBLOCK CHECK-HASH PROTECTION? [yn] n ADD INODE CHECK-HASH PROTECTION? [yn] n ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 3627 files, 131623 used, 376160 free (3256 frags, 46613 blocks, 0.6% fragmentation) ***** FILE SYSTEM IS CLEAN ***** [0]# fsck /dev/da0s4d Cannot find file system superblock Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? no [8]# - And trying to mount yields: [8]# mount /dev/da0s4a /mnt [0]# mount /dev/da0s4d /mnt/usr mount: /dev/da0s4d: Invalid fstype: Invalid argument [1]# umount /mnt [0]# Expected result: - da0s4d should be usable under main as well. Note: - The first megabyte of da0s4d is attached. It hopefully suffices to find out why the superblock is not accepted on main. -- Martin -- You are receiving this mail because: You are the assignee for the bug.