Date: Thu, 13 Nov 2014 06:08:11 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194983] New: ZFS pool fails to import after r274337 (ZFS large block support) Message-ID: <bug-194983-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194983 Bug ID: 194983 Summary: ZFS pool fails to import after r274337 (ZFS large block support) Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: marcus@blazingdot.com Created attachment 149351 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=149351&action=edit Boot messages Hi, I have two pools: "zroot" (imports fine) and "archive", which will not import after -r274337. I have compiled both a r274337 kernel and r274334 (the commit before it) and the pool will import with the earlier kernel. During boot, I get: Solaris: WARNING: can't open objset for archive/oldmac Solaris: WARNING: can't open objset for archive/archive Solaris: WARNING: can't open objset for archive/pics Solaris: WARNING: can't open objset for archive/music Solaris: WARNING: can't open objset for archive/Win7 Solaris: WARNING: can't open objset for archive/win98 Solaris: WARNING: can't open objset for archive This repeats several times, with some usb initialization interspersed. See dmesg.boot (attached). These messages continue to accumulate in dmesg. [mreid@sol /usr/home/mreid]$ zpool status pool: archive state: FAULTED status: The pool metadata is corrupted and the pool cannot be opened. action: Destroy and re-create the pool from a backup source. see: http://illumos.org/msg/ZFS-8000-72 scan: scrub repaired 0 in 1h16m with 0 errors on Sat Oct 18 03:26:54 2014 config: NAME STATE READ WRITE CKSUM archive FAULTED 0 0 0 mirror-0 ONLINE 0 0 0 ada0s2 ONLINE 0 0 0 ada1s1 ONLINE 0 0 0 pool: zroot state: ONLINE scan: scrub repaired 0 in 0h0m with 0 errors on Wed Nov 12 21:25:39 2014 config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 ada2p2 ONLINE 0 0 0 errors: No known data errors Note that the pool is made up of two mbr partitions (ada0 also serves as a win7 boot disk). Here is some partition info: [mreid@sol /usr/home/mreid]$ fdisk ada0 ******* Working on device /dev/ada0 ******* parameters extracted from in-core disklabel are: cylinders=3876021 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=3876021 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 7 (0x07),(NTFS, OS/2 HPFS, QNX-2 (16 bit) or Advanced UNIX) start 2048, size 204800 (100 Meg), flag 80 (active) beg: cyl 0/ head 32/ sector 33; end: cyl 12/ head 223/ sector 19 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 206848, size 1858822144 (907628 Meg), flag 0 beg: cyl 205/ head 3/ sector 20; end: cyl 50/ head 12/ sector 44 The data for partition 3 is: sysid 7 (0x07),(NTFS, OS/2 HPFS, QNX-2 (16 bit) or Advanced UNIX) start 1859028992, size 2047997952 (999999 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: <UNUSED> [mreid@sol /usr/home/mreid]$ fdisk ada1 ******* Working on device /dev/ada1 ******* parameters extracted from in-core disklabel are: cylinders=3876021 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=3876021 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 1858823505 (907628 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 870/ head 15/ sector 63 The data for partition 2 is: sysid 7 (0x07),(NTFS, OS/2 HPFS, QNX-2 (16 bit) or Advanced UNIX) start 1858824192, size 2048200704 (1000098 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: <UNUSED> The data for partition 4 is: <UNUSED> [mreid@sol /usr/home/mreid]$ gpart list Geom name: ada0 modified: false state: OK fwheads: 16 fwsectors: 63 last: 3907029167 first: 63 entries: 4 scheme: MBR Providers: 1. Name: ada0s1 Mediasize: 104857600 (100M) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r0w0e0 attrib: active rawtype: 7 length: 104857600 offset: 1048576 type: ntfs index: 1 end: 206847 start: 2048 2. Name: ada0s2 Mediasize: 951716937728 (886G) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r0w0e0 rawtype: 165 length: 951716937728 offset: 105906176 type: freebsd index: 2 end: 1859028991 start: 206848 3. Name: ada0s3 Mediasize: 1048574951424 (977G) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r0w0e0 rawtype: 7 length: 1048574951424 offset: 951822843904 type: ntfs index: 3 end: 3907026943 start: 1859028992 Consumers: 1. Name: ada0 Mediasize: 2000398934016 (1.8T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r0w0e0 Geom name: ada1 modified: false state: OK fwheads: 16 fwsectors: 63 last: 3907029167 first: 63 entries: 4 scheme: MBR Providers: 1. Name: ada1s1 Mediasize: 951717634560 (886G) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 3584 Mode: r0w0e0 attrib: active rawtype: 165 length: 951717634560 offset: 32256 type: freebsd index: 1 end: 1858823567 start: 63 2. Name: ada1s2 Mediasize: 1048678760448 (977G) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r0w0e0 rawtype: 7 length: 1048678760448 offset: 951717986304 type: ntfs index: 2 end: 3907024895 start: 1858824192 Consumers: 1. Name: ada1 Mediasize: 2000398934016 (1.8T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r0w0e0 Please let me know if I can provide any more information. I can test patches, etc. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194983-8>