Date: Sun, 4 Jan 2004 11:18:50 +0100 From: Jens Schweikhardt <schweikh@schweikhardt.net> To: "Greg 'groggy' Lehey" <grog@FreeBSD.org> Cc: fs@freebsd.org Subject: Re: fsck(8), /etc/fstab and vinum Message-ID: <20040104101850.GA1169@schweikhardt.net> In-Reply-To: <20040104031138.GE7617@wantadilla.lemis.com> References: <20040103160313.GA54680@schweikhardt.net> <20040104031138.GE7617@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Grog, On Sun, Jan 04, 2004 at 01:41:38PM +1030, Greg 'groggy' Lehey wrote: # On Saturday, 3 January 2004 at 17:03:13 +0100, Jens Schweikhardt wrote: # > hello, world\n # > # > it appears fsck can't determine the file system type for ufs on vinum # > partitions if there is no entry in /etc/fstab, # # Yes, there are difficulties, depending on the name of the volume. /dev/vinum/Ports in this case. # > even when I use fsck -T ufs:ro /dev/vinum/foo. # # Hmm. I haven't tried this. It works fine with -t ufs, at least on # -CURRENT. Do you have trouble with that? Yes. On -CURRENT -T ufs: only works when /etc/fstab already has an entry for /dev/vinum/Ports. Starting without an entry in /etc/fstab: root@hal9000: # uname -a FreeBSD hal9000.schweikhardt.net 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon Dec 22 15:03:45 CET 2003 toor@hal9000.schweikhardt.net:/usr/obj/usr/src/sys/HAL9000 i386 root@hal9000: # fsck -T ufs /dev/vinum/Ports fsck: Invalid option string root@hal9000: 1 # fsck -T ufs: /dev/vinum/Ports fsck: Could not determine filesystem type root@hal9000: 1 # fsck -T ufs:ro /dev/vinum/Ports fsck: Could not determine filesystem type root@hal9000: 1 # mount /dev/vinum/Ports /mnt root@hal9000: # df /dev/vinum/Ports Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/vinum/Ports 8131083 1 7480596 0% /mnt root@hal9000: # echo '/dev/vinum/Ports /mnt ufs rw,noatime,noauto 0 2' >> /etc/fstab root@hal9000: # umount /dev/vinum/Ports root@hal9000: # fsck /dev/vinum/Ports ** /dev/vinum/Ports ** 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 1 files, 1 used, 8131082 free (18 frags, 1016383 blocks, 0.0% fragmentation) root@hal9000: # fsck -T ufs /dev/vinum/Ports fsck: Invalid option string root@hal9000: 1 # fsck -T ufs: /dev/vinum/Ports ** /dev/vinum/Ports ** 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 1 files, 1 used, 8131082 free (18 frags, 1016383 blocks, 0.0% fragmentation) root@hal9000: # fsck -T ufs:ro /dev/vinum/Ports fsck_ufs: illegal option -- o usage: fsck_ufs [-BFpfny] [-b block] [-c level] [-m mode] file system ... Hmm. The last usage message looks suspicious. Is something wrong with fsck's option parsing or passing to fsck_ufs? Thanks for any input, and, before it's over, happy new year! Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040104101850.GA1169>