Date: Sat, 6 Jan 2001 15:01:07 -0800 From: Jaye Mathisen <mrcpu@internetcds.com> To: hackers@freebsd.org Subject: fsck problem on large vinum volume Message-ID: <20010106150106.X32287@apocalypse.cdsnet.net>
next in thread | raw e-mail | index | archive | help
FreeBSD newsfeed-inn2.meganews.com 4.2-STABLE FreeBSD 4.2-STABLE #2: Fri Jan 5 09:42:37 PST 2001 root@newsfeed-inn2.meganews.com:/n/FreeBSD/RELENG_4-2000-12-18/src/sys/compile/NEWSFEED-INN3 i386 I have a 930GB vinum volume newfs -v -i 4194304 /dev/vinum/v-spool went fine. However, I can't fsck it, I have to always use the alternate block. newsfeed-inn2# fsck -b 32 /dev/vinum/v-spool Alternate super block location: 32 ** /dev/vinum/v-spool ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 9 files, 257 used, 975161122 free (18 frags, 121895138 blocks, 0.0% fragmentation) UPDATE STANDARD SUPERBLOCK? [yn] y ***** FILE SYSTEM WAS MODIFIED ***** newsfeed-inn2# fsck /dev/vinum/v-spool ** /dev/vinum/v-spool BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/vinum/v-spool: CANNOT FIGURE OUT FILE SYSTEM PARTITION If I mount it after the fsck -b 32, it seems just fine. smaller vinum volumes mount/umount fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010106150106.X32287>